On 1/28/07, Chris Cannam [EMAIL PROTECTED] wrote:
On Saturday 27 Jan 2007 18:57, Nedko Arnaudov wrote:
Robert Jonsson [EMAIL PROTECTED] writes:
On Saturday 27 January 2007 06:47, Loki Davison wrote:
why are you coding new stuff for a depreciated system? Why not
LV2?
And why should you
On 28 Jan 2007, at 05:07, Fraser wrote:
however, it and i think all the other issues you raise are all
solved by
LV2 (LADSPA Version 2), which has come about in part from other
people's
difficulties with the same range of problems as you.
ahh, so there is a V2 coming, not too much info
Hi,
maybe it's just another of my dumb questions, however I would like to
know whether it is happened to you that a sound processing plugin
(LADSPA, LV2, VST, etc.) crashed (segm. faults, etc.).
In such case, can you estimate how often does it happen that such
plugins are misprogrammed?
Thanks in
Hi Steve,
ahh, so there is a V2 coming, not too much info about it yet out there
(unless you know where to look)
Which is deliberate, as it's not quite finished yet. There was quite
a lot of discussion here though.
I took me a while to find this list.
The http://www.ladspa.org site
Fraser [EMAIL PROTECTED] writes:
The plugin doesn't know when a parameter has changed, so it must calculate
it's internal values from the displayed parameter 'as often as possible' -
once per run() call (doing it in the for loop itself is just too extreme).
dynparam LV2 extension handles
