22 Feb
2009
22 Feb
'09
10:14 p.m.
Yes you are missing that, either we would have an intelligent host
commanding an unruly herd of time time-tracks, or we would just have a
single master pretty much in terms with its own inconsistencies.
In a fight between a single 24 track Studer and an array of synchronized
Nagra's, I know what combination of poison I would pick :-D
/j
On Sun, 2009-02-22 at 19:01 -0800, Justin Smith wrote:
So there is our answer: one extra input on every
"timeline" dependent
plugin, telling it the logical transport time/state. That plus a gui
with pretty pictures of waveforms or midi notes or automation lines
gives us what we have been talking about, right? Or am I missing
something?
On Sun, Feb 22, 2009 at 6:55 PM, Jens M Andreasen
<jens.andreasen(a)comhem.se> wrote:
On Sun, 2009-02-22 at 18:51 -0800, Justin Smith wrote:
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev Actually almost everything an audio plugin does
is time dependent.
But not to the wall clock!
/j
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev