[linux-audio-dev] Plugin APIs (again)

Tim Hockin thockin at hockin.org
Wed Dec 4 14:11:00 UTC 2002


> The central part can be very open, eg in URIs you're allowed to assign
> URIs from any domain you have control over, so I could label somthing
> "http://plugin.org.uk/foo#23". This means that anyone with a website can
> assign URIs.
> 
> I dont really like using strings for UIDs though. Its too easy to read
> semantics into them.

I agree about semantics, but self-maintenance makes this much more
appealing.  Of course, domain registration expires.

> > I disagree with that - this is a waste of DSP cycles processing to be sent
> > nowhere.
> 
> No, its a waste of DSP cycles to check whether something's there or not.

can we meet in the middle and say that for some cases it is easier to assume
silence, and in others it is easier to check for presence?

> Dont bundle up channels! People dont do that in studios for a good reason.
> a single channel on a single connections is simple, unambiguous, obvious.
> But say you have 2 channels is that L+R, M+S, C+M? how about 8, is it 7.1,
> 8.1 pre filter, 5.1 in ADAT? What do you do when you have a 5.1 bundle
> and you want to send it as 5.1 in ADAT? Does that require a 5.1 rebundler?

ok, ok, I'm coming around again :)

> I'm not sure about the other arguments, but polyphony control is complex
> and probably only the instrument can do it usefully. If you want this you
> might have to do it by telling the instrument what its max poly should be.

Perhaps this, with some way of the instrument telling the host about numbers
of voices.

> voice_on is proably more instrument neutral. Not everything is a note (eg.
> my LADSPA gong).

sorry, note_on is MIDI, voice_on is what I put in the API :)

> I dont think you can do anything useful with a generic file string, what
> could be host use it for?

The host could provide a standard file-open dialog for filenames.  The host
could provide a text-box for speech-synthesis.




More information about the Linux-audio-dev mailing list