LV2 Create
Moderators: MattKingUSA, khz
LV2 Create
Going to start on the UI stuff.
Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.
- lucianodato
- Established Member
- Posts: 156
- Joined: Sat May 15, 2010 9:00 pm
- Has thanked: 3 times
- Been thanked: 16 times
Re: LV2 Create
Re: LV2 Create
Well it needs to use some installed XWindow font and I assumed helv was a safe choice. When debian testing switches to Wayland, this will be rewritten as a cairo-using wayland app anyway.lucianodato wrote:Hi Jeff, this is very useful for experimenting with quick dsp code. Thank's! However when I run it I get "Need to install helvetica 8 font", could this be avoided? I don't mind installing helvetica fonts though. Again thank's!
P.S. Before you do serious coding, download the latest version (with the "Add source" button on the Compile page). You add your code to the file named after your project -- not dsp.c. The readme tutorial is updated.
Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.
Re: LV2 Create
I was using lv2 create last night (first time earnestly trying to make a plugin using it). One thing I can suggest, Cypress's PSOC system autogenerates lots of code for their systems. In the autogenerated code there is always a lot of comments, just like what you've done, but also there is always a block like:
Code: Select all
/*Insert User Code in this section*/
/*End of User Code*/
Also I had to check the plugin.h file to figure out how to access the control ports. I didn't see in the docs or any of the source comments a guide for this. Pretty easy to figure out for me but I would recommend putting in the comment above the run function a quick example of accessing the users first control port, same as you do with the audio input and output port.
Overall excellent work. Makes it almost too easy to do plugin development Thanks.
music: https://soundcloud.com/ssj71
My plugins are Infamous! http://ssj71.github.io/infamousPlugins
I just want to get back to making music!
Re: LV2 Create
Well, that's the thing. All user code goes into the .c and .h files LvC makes for you for that purpose (for example My_Little_Amp.c and My_Little_Amp.h). And those 2 files are never overwritten, even if you add/delete controls/channels/state variables, add/remove support such as MIDI, or change any of the settings. (The only exception is if you change language from C to C++ after already adding your code, which would be silly). The skeleton code manages all the lv2/ladspa details.ssj71 wrote:there is always a block like:
/*Insert User Code in this section*/
And anything NOT in those blocks will get automatically removed next time it is built.
LvC doesn't just spit out a blank template, then leave you on your own. Each and every update to your plugin can be done via the gui, right to compiling.
Hmm, right from the first example My_Little_Amp the tutorial shows accessing its Volume port. But maybe you read the initial version. Each update has gotten expanded docs (and they're still not even close to done. There's more docs to come).Also I had to check the plugin.h file to figure out how to access the control ports. I didn't see in the docs or any of the source comments a guide for this.
But note in the comment header for pluginRun, all your control ports are listed by name and then code you can copy/paste, such as:
Volume = *Head.In[LV2_VOLUME]
I should make it
*plugin->Head.In[LV2_VOLUME]
Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.
Re: LV2 Create
However, when I do x386 compile and install the makefile tries to cp so.686 to the lv2 directory, where the gcc output is so.386.
music: https://soundcloud.com/ssj71
My plugins are Infamous! http://ssj71.github.io/infamousPlugins
I just want to get back to making music!
Re: LV2 Create
Uh oh. I assumed that all 32-bit intel/amd systems would output "uname -m" as i386. Guess there's an i686 too.ssj71 wrote:the makefile tries to cp so.686 to the lv2 directory, where the gcc output is so.386.
Will work on a fix.
Author of BackupBand at https://sourceforge.net/projects/backupband/files/
My fans show their support by mentioning my name in their signature.