On Saturday 27 January 2007 06:47, Loki Davison wrote:
On 1/27/07, Fraser [EMAIL PROTECTED] wrote:
Hi All,
I've been converting my old VST plugins over to LADSPA and have come
across something in the api which I really miss - the inability separate
the algorithmic to the displayed value
On Sat, 2007-01-27 at 16:05 +1100, Fraser wrote:
Hi All,
I've been converting my old VST plugins over to LADSPA and have come
across something in the api which I really miss - the inability separate
the algorithmic to the displayed value of a parameter.
I'm finding this inability is leading
Robert Jonsson [EMAIL PROTECTED] writes:
On Saturday 27 January 2007 06:47, Loki Davison wrote:
On 1/27/07, Fraser [EMAIL PROTECTED] wrote:
Hi All,
I've been converting my old VST plugins over to LADSPA and have come
across something in the api which I really miss - the inability
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 code for a plugin standard that nothing
supports?
Suggesting that LADSPA is deprecated is a bit of a stretch. It may not
be
perfect, but it's well supported.
What would be really nice for LA scene is to clean up the available Ladspa
plugins so that they all just work while there is still a momentum to
maintain these. Unless this has changed
Hi Paul,
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 about it yet out there
(unless you
