Re: [LAD] [RFC] LADSPA 1.2

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Krzysztof Foltman <wdev@...>
Cc: <linux-audio-dev@...>
Date: Friday, June 19, 2009 - 3:18 pm

--0016e6db29434dc82b046cb507e1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

2009/6/19 Krzysztof Foltman

> Stefano D'Angelo wrote:

Ok.

> > to ladspa_parse_value() and ladspa_format_value(), just

Ok #2.

Stefano

--0016e6db29434dc82b046cb507e1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/6/19 Krzysztof Foltman <wdev@foltman.com>
Stefano D'Angelo wrote:

> A little note, though: wouldn't it be better to pass this function=
s

br>

I'm already thinking of reusing the same thing for DSSI, and DSSI=

indexes may be overlap with LADSPA indexes while referring to different
plugins - while the same isn't the problem when using descriptors
(they're either different or point to the same plugin).

Example: dssi_descriptor may return "Synth A" as index 0 and &quo=
t;Effect A"
as index 1, while ladspa_descriptor will only return "Effect A" a=
s index
0. So, the index 0 may refer to the synth or the effect depending on
context (LADSPA or DSSI). On the other hand, even if DSSI and LADSPA
reuse the same LADSPA_Descriptor (like it was the case in older versions
of Calf), both uses of this descriptor refer to the same plugin.Ok.=A0

t

I'm against doing it in this iteration - because state-dependent<=
br>
conversion is actually a more complex problem, which may be solved some
time in the next 40 years. It makes sense, but benefit/risk ratio is
worse than for other things already being proposed (circular flag,
enums, or even my silly text-float conversion).

Why is it more complex? It's because it makes it necessary to have
things like inter-parameter dependencies (to be able to specify that,
for example, port "filter type" affects the enum labels of "=
filter
rolloff", or that change in a port called "delay unit" from =
seconds to
samples should trigger a redraw of labels of ports called "delay lengt=
h
(L)" and "delay length (R)"). It's a whole new can of wo=
rms, one that I
don't *need* opened now. And if we do it without worrying about
dependencies, we end up with UI glitches (labels out of sync with
current state), or inefficiency like requerying all the enum-capable
ports for all the enum values after any port value change, just in case
any of them changed due to state change.
Ok #2.Stefano<=
br>

--0016e6db29434dc82b046cb507e1--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] [RFC] LADSPA 1.2, Jörn Nettingsmeier, (Thu Jun 18, 4:28 pm)
Re: [LAD] [RFC] LADSPA 1.2, Pau , (Sat Jun 20, 12:07 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 5:48 pm)
Re: [LAD] [RFC] LADSPA 1.2, Tim Goetze, (Thu Jun 18, 6:53 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 8:22 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 8:57 pm)
Re: [LAD] [RFC] LADSPA 1.2, Tim Goetze, (Thu Jun 18, 9:17 pm)
Re: [LAD] [RFC] LADSPA 1.2, Arnold Krille, (Thu Jun 18, 9:24 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 9:43 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 9:23 pm)
Re: [LAD] [RFC] LADSPA 1.2, Damon Chaplin, (Thu Jun 18, 9:47 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 9:59 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Fri Jun 19, 8:20 am)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Fri Jun 19, 12:07 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Fri Jun 19, 12:35 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Fri Jun 19, 12:49 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Fri Jun 19, 1:33 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fraser, (Fri Jun 19, 4:53 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Fri Jun 19, 6:01 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fraser, (Sat Jun 20, 2:18 am)
Re: [LAD] [RFC] LADSPA 1.2, David Robillard, (Sat Jun 20, 12:14 am)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Fri Jun 19, 1:45 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Fri Jun 19, 2:15 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Fri Jun 19, 3:18 pm)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Thu Jun 18, 10:36 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 5:55 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 6:34 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 6:54 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 7:31 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 8:50 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 9:33 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 10:13 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 10:58 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 11:44 pm)
Re: [LAD] [RFC] LADSPA 1.2, Luis Garrido, (Thu Jun 18, 6:31 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 6:46 pm)
Re: [LAD] [RFC] LADSPA 1.2, Fons Adriaensen, (Thu Jun 18, 6:57 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 6:58 pm)
Re: [LAD] [RFC] LADSPA 1.2, Damon Chaplin, (Thu Jun 18, 8:39 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 8:52 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefano D'Angelo, (Thu Jun 18, 6:48 pm)
Re: [LAD] [RFC] LADSPA 1.2, Stefan Kost, (Tue Jun 23, 7:52 am)
Re: [LAD] [RFC] LADSPA 1.2, Krzysztof Foltman, (Tue Jun 23, 8:34 am)
Re: [LAD] [RFC] LADSPA 1.2, Jörn Nettingsmeier, (Thu Jun 18, 5:53 pm)