On 30 Jan 2007, at 01:25, Fraser wrote:
Hi Steve,
Ah, well the host is not supposed to change port values during run()
anyway, the idea in LADSPA (and LV2) is that the host should chop the
run() block where port values change. In practice not all hosts do
that, some just pick a suitably smal
Hi Steve,
> Ah, well the host is not supposed to change port values during run()
> anyway, the idea in LADSPA (and LV2) is that the host should chop the
> run() block where port values change. In practice not all hosts do
> that, some just pick a suitably small block size, eg. 32 frames and
> qua
Chris Cannam <[EMAIL PROTECTED]> writes:
> Is Zynjacku specific to Zyn in any way, or is it just named that way because
> you wanted an LV2 host when you happened to be working on Zyn-based plugins?
It is not specific. I loaded and produced sound with some of LV2 plugins
From ll-plugins and with
On Mon, 2007-01-29 at 10:23 -0500, Paul Winkler wrote:
> On Mon, Jan 29, 2007 at 08:08:37AM +, Steve Harris wrote:
> > Ah, well the host is not supposed to change port values during run()
> > anyway, the idea in LADSPA (and LV2) is that the host should chop the
> > run() block where port v
On 29 Jan 2007, at 15:23, Paul Winkler wrote:
On Mon, Jan 29, 2007 at 08:08:37AM +, Steve Harris wrote:
Ah, well the host is not supposed to change port values during run()
anyway, the idea in LADSPA (and LV2) is that the host should chop the
run() block where port values change.
/delurk
On Mon, Jan 29, 2007 at 08:08:37AM +, Steve Harris wrote:
> Ah, well the host is not supposed to change port values during run()
> anyway, the idea in LADSPA (and LV2) is that the host should chop the
> run() block where port values change.
/delurk
What does "chop the run block" mean?
/
On 29 Jan 2007, at 14:41, Lars Luthman wrote:
On Mon, 2007-01-29 at 13:49 +, Chris Cannam wrote:
On Monday 29 Jan 2007 07:39, Nedko Arnaudov wrote:
Chris Cannam <[EMAIL PROTECTED]> writes:
What are they? Do they do anything else, besides host LV2 plugins?
I'm aware of these LV2 hosts:
On Mon, 2007-01-29 at 13:49 +, Chris Cannam wrote:
> On Monday 29 Jan 2007 07:39, Nedko Arnaudov wrote:
> > Chris Cannam <[EMAIL PROTECTED]> writes:
> > > What are they? Do they do anything else, besides host LV2 plugins?
> >
> > I'm aware of these LV2 hosts:
> > * jack_host from libslv2 proj
On Monday 29 Jan 2007 07:39, Nedko Arnaudov wrote:
> Chris Cannam <[EMAIL PROTECTED]> writes:
> > What are they? Do they do anything else, besides host LV2 plugins?
>
> I'm aware of these LV2 hosts:
> * jack_host from libslv2 project, by Dave Robillard
> * elven from ll-plugins project, by Lars
On 29 Jan 2007, at 02:18, Fraser wrote:
Hi Steve,
Hi Fraser,
Sure. This was an issue in LADSPA, though not a significant enough
one that anyone wanted it changed. I would suspect you're
overestimating the burden compared to the function call overhead and
cache thrashing. I'd be interested t
Chris Cannam <[EMAIL PROTECTED]> writes:
> What are they? Do they do anything else, besides host LV2 plugins?
I'm aware of these LV2 hosts:
* jack_host from libslv2 project, by Dave Robillard
* elven from ll-plugins project, by Lars Luthman
* zynjacku, by me
* maybe ingen (om), by Dave Robil
"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 handle
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
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 ab
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?
> >
> > An
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
> > 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 c
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 nothi
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 - th
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 le
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 dis
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 le
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 of a parameter.
I'm finding this inability is leading to non-
23 matches
Mail list logo
