Re: [Jack-Devel] The Situation(s) With JACK

PrevNext  Index
DateSat, 10 Dec 2011 15:36:47 +0100
From Robin Gareus <[hidden] at gareus dot org>
ToFons Adriaensen <[hidden] at linuxaudio dot org>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToFons Adriaensen Re: [Jack-Devel] The Situation(s) With JACK
On 12/10/2011 12:33 PM, Fons Adriaensen wrote:
> On Fri, Dec 09, 2011 at 06:58:00PM -0500, Paul Davis wrote:
>  
>> STOPPED and RUNNING can't accomodate slow-sync clients.
> 
> 1. Stopped, Rolling and Starting are incomplete as well.
> 
> It's impossible to find out if everybody is ready to
> start on cue without actually trying it and risk failure.
> There should be a 4th state, 'Locating' or so, to allow a
> client to indicate that it is not yet ready (and then
> 'Stopped' implies readyness of course, just as 'Rolling'
> does.).
> 
> 2. It should be possible to have more than one transport

+1
> state. 
Oh :)

> For at least 3 concerts this year I had two or more
> players (Ardour) which needed their transport synced with
> e.g. effects sequencers, and which were used at the same
> time but independent of each other. Had to hack something
> using audio ports to transfer data.

A few years back I was proposing to have additional transport/time
information per audio port.

Basically each track could have its own transport or be linked with an
offset to the main transport.

robin
PrevNext  Index

1323527827.17642_0.ltw:2,a <4EE36E7F.1020904 at gareus dot org>