Re: [LAD] [RFC] LADSPA 1.2

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Fraser <fraser@...>
Cc: <linux-audio-dev@...>
Date: Friday, June 19, 2009 - 6:01 pm

Fraser wrote:

Such a change could also give you problems if you expose
implementation-defined values (as opposed to real-life-compatible units)
to users. Think of backward compatibility, for example.
Be careful: I can't speak for everyone, but after years of stagnation it
would be nice to get a useful 1.2 out of the door without trying to cram
every possible good idea into it.

On the other hand, I'm definitely going to push for more improvements.
Just let's finalize 1.2 first, before everyone involved exceeds their
quota of give-a-damn ;)

Some ideas about discovery (which I *wouldn't* like to put into v1.2):

1. Define a plugin exported function (or a set of those) that need to be
called to notify the plugin about functionality it implements; which
will affect the set of descriptors that ladspa_descriptor will return
(i.e. host calls a plugin function called ladspa_host_version(1, 5); so
that plugin knows to return the plugins that require LADSPA v1.5 to be
implemented by the host)

This is actually dangerous in context of multiple hosts within same
process, and contrary to intuition, this situation may happen (say,
LADSPA plugins loaded into Ingen either directly or as LV2 via NASPRO
wrapper; )

2. Provide a new discovery function (say, ladspa15_descriptor), with
additional parameters that pass at least the version number implemented
by the host, and maybe some callback mechanism that can be used to
obtain information about the host.

Or alternatively, we can use some sort of RDF-based discovery mechanism,
preferably using some human-friendly notation. I've heard Turtle is
rather nice from that point of view ;)

These may be control ports with special hints, or special name, or some
transport related callback. It should be done reasonably soon, but it
shouldn't be done in v1.2 IMHO.

(I want it for Vintage Delay and other things, too!)

The language can be read via getenv() - you may want to keep it simple :)

The host name - I wouldn't push for or against that.

Factory presets are important, too, but it proved to be a contentious
issue more than one time already, and you probably don't want to wait
until everyone agrees or stops giving a damn ;). If I had my way, I'd
probably avoid RDF or even XML, but that's, again, a flamewar waiting to
happen.

Krzysztof

_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

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)