Paul Davis wrote:
> there are many parts of the JACK API that are not RT-bound. in fact,
> basically *all* of it except for a clients process() callback, which a
> client is not required to register.
>
I guess the "synchronous" response to port appearance/connection events
(like application connecting ports before next event is generated by
JACK) pretty much requires RT in those applications. Is that right?
Or are those callbacks called in non-audio thread context and don't
block audio? (I suppose they block audio, because I see several watchdog
timeouts which seem to be related to patchbay applications doing screen
updates etc.)
Krzysztof
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Tue Feb 5 04:15:01 2008
This archive was generated by hypermail 2.1.8 : Tue Feb 05 2008 - 04:15:01 EET