Subject: Re: Plugin chains and EDLs, was Re: [linux-audio-dev] ardour, LADSPA, a marriage
From: Paul Barton-Davis (pbd_AT_Op.Net)
Date: Tue Nov 14 2000 - 01:06:12 EET
>> 1) Could Ardour be a smart enough host to handle the patching? At this
>> point I tend to think that pbd can do anything, so I'm going to assume
>> yes. :) It's more a question of what pbd wants.
>
>At the moment, as I understand it, ardour can only use 1 input, 1 output
>plugins, so no.
Thats correct. It does handle plugin chains, but it doesn't do
anything intelligent with input > 1 and/or output > 1 (other than just
duplicate all the channels in place, so to speak.
Again, thats because the current use is as an insert, not an aux send
or other concept.
>something more appropriate), but my understanding of what an EDL does
>doesn't include things like plugins. I think it's just a description of
>which lump of audio to play next in a stream.
yep. think of an EDL as a replacement for a disk file. thats really
all it is. it just so happens that instead of getting data
sequentially from the disk, the act of reading data from an EDL may
use a data stream from all over the place, but thats just an
implementation detail that the EDL user doesn't need to worry about.
>You can uniquly describe a LADSPA net by stating what each plugin is
>connected to and what all its parameters are. Infact it's probably
>possible to create a LADSPA plugin which reads a nets description and then
>offers all the unconnected inputs and outputs as its input and outputs.
heh. shades of LISP.
>Would requite a plugin that was a host too, but I think that's possible.
yep, no reason why a plugin can't be a host or vice versa, as long as
it can adapt to certain situations.
--p
This archive was generated by hypermail 2b28 : Tue Nov 14 2000 - 01:55:21 EET