> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Davis
> Sent: 22 November 2001 14:10
> To: James Courtier-Dutton
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Alsa-devel] Restarting when in async mode
>
>
> nope. it does it the same way that JACK does it (and Rewire, and every
> plugin system including VST/MAS/TDM/RTAS/LADSPA and others): you use
> a callback approach. every participant in the processing network
> provides a callback which is called with a number of frames to
> process. this ensures that its audio input and/or output is locked to
> every other participant.
>
> >One could probably add this feature to alsa quite easily, by adding a
> >"presentation time stamp" to the snd_pcm_write function call. The if two
> >applications were trying to output sound at the same time, alsa-lib could
> >compare presentation time stamps, and keep everything in sync.
>
> sorry, but thats not running in sample sync. thats "chasing sync". if
> one of them "drifts", the others follow. running in sample sync means
> that they never drift. its like the difference between word clock and
> a time sync signal like MTC or SMPTE. the former avoids any drift by
> having everyone use the same sample clock; the latter allows the
> different parties to catch up or slow down or jump around as required.
>
> --p
>
So the assumption here is that there is only one drain/output device, and
all sources are kept in sync with the single drain device.
Your solution would fail if there was more than one drain/output device.
I.E. Two audio cards.

Cheers
James


_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Reply via email to