Subject: Re: [linux-audio-dev] App intercomunication issues, some views.
From: Paul Davis (pbd_AT_op.net)
Date: Wed Jul 24 2002 - 16:33:12 EEST
>> JACK provides both current time and information on the latency
>
>Oh right - so jack_port_get_total_latency() is working now? Excellent.
>Last time I asked it was still in the planning stage.
no, it exists and works, but it can't handle all possible connection
graphs. it may never be able to.
>What apps have an example implementation of the JACK transport controls?
>Neither ecasound or ardour appear to but I'm probably a bit out of date
>with them. And again, why should I care about the JACK transport?
i think ecasound can act as the time master + slave now. i still need
to add it to ardour (it will act as both a slave and a master).
why care? because the transport time is the only important global time
- it indicates what you should be playing/doing right now. if your
client is running but is not the master, and the master has stopped,
then you may have the kind of client that needs to stop
too. rosegarden would be, i think, such a client. conversely, you may
want your client to function as the master, thus being able to stop and
start, loop and position other time-sensitive clients.
--p
This archive was generated by hypermail 2b28 : Wed Jul 24 2002 - 16:42:50 EEST