5 Feb
2008
5 Feb
'08
3:24 a.m.
Le 5 févr. 08 à 00:10, Krzysztof Foltman a écrit :
Paul Davis wrote:
jackdmp used a 2 threads model on client side: one RT thread for
audio (call the "process" callback) and one non RT thread for
"notification" callback (like graph reorder, port register, connect/
disconnect...)
Stéphane
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