Hi,
just one note: a LADSPA plugin will not be more stable just because it
is a LADSPA plugin. It's regular C/C++ code and if you mess things up,
it will crash, no matter inside which kind of plugin the code is
running. A crashing LADSPA plugin will also crash LMMS itself as it's
not running in a
On 02/09/2014 11:39 AM, Johannes Lorenz wrote:
> Am Sonntag, 9. Februar 2014, 11:33:19 schrieb Vesa:
>> there's things that LADSPA plugins can't do, eg.
>> instruments.
> Sorry for the OT talk. But: I am not sure why this should not be possible. An
> instrument is nothing but an effect with no inp
Am Sonntag, 9. Februar 2014, 11:33:19 schrieb Vesa:
> there's things that LADSPA plugins can't do, eg.
> instruments.
Sorry for the OT talk. But: I am not sure why this should not be possible. An
instrument is nothing but an effect with no input and one (stereo) output. I
know this is missing in
On 02/09/2014 11:13 AM, Johannes Lorenz wrote:
>> And for another, I don't really see what the reasoning or purpose behind
>> this LADSPA++ idea is - see my response in the github thread. Let me
>> turn your question around for you: what benefit would LADSPA++ allow
>> over a native LMMS plugin?
>
> And for another, I don't really see what the reasoning or purpose behind
> this LADSPA++ idea is - see my response in the github thread. Let me
> turn your question around for you: what benefit would LADSPA++ allow
> over a native LMMS plugin?
* smaller code (about 5-10 times less)
* safer cod
On 02/09/2014 10:46 AM, Johannes Lorenz wrote:
>> Thanks, this is helpful. The BUILD_PLUGIN is in the main cmake file
>> right? I don't really have experience with cmake, I just barely know how
>> to write regular makefiles, but I guess it's just something I'll figure
>> out as I go, again... (the
> Thanks, this is helpful. The BUILD_PLUGIN is in the main cmake file
> right? I don't really have experience with cmake, I just barely know how
> to write regular makefiles, but I guess it's just something I'll figure
> out as I go, again... (the best way to figure things out!)
Actually not. This
On 02/09/2014 10:24 AM, Johannes Lorenz wrote:
> Hey,
>
> seems to be a good idea to me. If you need some sample code about
> waveshaping,
> look into ZynAddSubFX, though I think you know how it's done.
>
> You probably need 6 files:
>
> $ find . -iname "*analy*" | grep -E '\.cpp$|\.h$'
> ./plugi
Hey,
seems to be a good idea to me. If you need some sample code about waveshaping,
look into ZynAddSubFX, though I think you know how it's done.
You probably need 6 files:
$ find . -iname "*analy*" | grep -E '\.cpp$|\.h$'
./plugins/spectrum_analyzer/spectrumanalyzer_control_dialog.cpp
./plugin
I've been thinking about this, and I'd like to take a shot at
implementing this. I'll probably be trying to look at other effect
plugins and see how they're implemented for guidance.
I'd like to know though, how exactly does the plugin discovery work in
LMMS? Are there steps I need to do to get LM
I'm a bit overwhelmed and under-qualified to speak on behalf of this
enhancement, but what you describe sounds very logical.
I had to look up the youtube video (here:
http://www.youtube.com/watch?v=vf0xXW3Z4ho) and I still am a bit perplexed
as to the use case of this.
-Tres
- tres.finocchi...@g
I've been thinking about this... basically, it's something I believe FL
studio already has, and something like this has been implemented in
various other softwares as well...
A waveshaper with a graph-based GUI. Basically, you have input on one
axis and output on another, and by default it's a dia
12 matches
Mail list logo
