Most synths are either VST only or support both VST and LV2. But there are a lot of excellent effects, which are LV2 only. But does that really matter? We have Carla, so you can use LV2 in a VST-only host and vice-versa. And, as I said above, developers can easily choose to support both formats. Can...

This is very unlikely to happen in the "official" JUCE from ROLI. They have been asked to do that for a long time and never did anything about it. There's talk of bringing falkTX's JUCE fork, which already has LV2 support, up to date again. But that won't help with existing plugins, which ...

You probably mean the original poster, but I for one wholeheartedly recommend using DPF, if - for some reason - one isn't restricted to pure C. It spares the developer from having to mess around with .ttl file generation and you get LV2 and VST2 plugin format output for free. When we did a small plu...

Understanding the concepts of LV2 and writing your first "Hello Sine" LV2 plugin isn't really that hard, and the official tutorial at lvplug.in does a good job of showing that. But I agree that a guide explaining how LV2 relates to other plugin formats from a technical standpoint and from ...

if the plugin has no factory preset, Carla, for example, won't enable the GUI controls to load LV2 presets. Correction: Carla doesn't enable the "Load State" button, unless there's at least one factory or user preset. So apparently no need to include a factory preset, if not needed. Sorry...

You probably know that, but you can look at this DPF example: https://github.com/DISTRHO/DPF/blob/master/examples/States/ExamplePluginStates.cpp I also just implemented state in one of my plugins (no UI): https://github.com/SpotlightKid/midiomatic/blob/master/plugins/MIDICCRecorder/PluginMIDICCRecor...

[...] what you want is this: Plugin(paramCount, 0, 1) // 0 programs, 1 state Otherwise I don't think it will save and load your state. I think if you have state it is a good idea to have at least one factory program. The state can be be saved in LV2 preset files, but if the plugin has no factory pr...

What I'm saying is that MIDI/OSC to parameter routing should be left to the plugin host, unless you have special needs. If you only have normal int/float/list parameters, no need to do that in the plugin yourself.

Here's the receipt: 1. [...] How's that different from a writing a plugin? Especially, if you're using a framework, that warps the differences of the various plugin standards. Ok, you don't have to allocate the input and output buffers yourself. Big deal. you don't have to worry about implementing ...

maybe even an established DSP wrapper like LADSPA or LV2. Why? Unless you're targetting a non-Linux embedded environment (but then you wouldn't be able to use ALSA as well), make that a definitely . For one thing, you don't have to worry about implementing dynamic parameter control via MIDI or othe...

I was hoping to rename the ports before the python script launches. I'm not sure you can rename ALSA ports, which your program hasn't opened itself. Maybe you could write a short Python script using the ALSA Python bindings and try? See the examples in the "test" directory of the alsa-pyt...