4 - Toutes les autres applications, les émulateurs...

client event poll on 26 for qjackctl starts at 6639941695
back from client event poll after 8 usecs
DIS-connect Hydrogen-1:out_R and system:playback_2
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now firewire_pcm active ? 1
client firewire_pcm: internal client, execution_order=0.
+++ client is now Hydrogen-1 active ? 1
client Hydrogen-1: start_fd=7, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: in subgraph after Hydrogen-1, execution_order=1.
client event poll on 26 for qjackctl starts at 6639941886
back from client event poll after 10 usecs
client Hydrogen-1: wait_fd=27, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
client event poll on 26 for qjackctl starts at 6639941967
back from client event poll after 8 usecs
DIS-connect Hydrogen-1:out_L and system:playback_1
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now firewire_pcm active ? 1
client firewire_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 26 for qjackctl starts at 6639942550
back from client event poll after 13 usecs
+++ client is now Hydrogen-1 active ? 1
client Hydrogen-1: in subgraph after qjackctl, execution_order=1.
client qjackctl: wait_fd=27, execution_order=2 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
client event poll on 26 for qjackctl starts at 6639942696
back from client event poll after 12 usecs
+++ deactivate Hydrogen-1
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now firewire_pcm active ? 1
client firewire_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 26 for qjackctl starts at 6639943741
back from client event poll after 17 usecs
client qjackctl: wait_fd=19, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 2
trying to lock graph to remove 2 problems
we have problem clients (problems = 2
++ Removing failed clients ...
client firewire_pcm error status 0
client qjackctl error status 0
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
21:00:01.011 Récupération désynchronisation (XRUN) (1).
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
firewire MSG: xrun detected
client event poll on 26 for qjackctl starts at 6640627331
back from client event poll after 80 usecs
load = 2.6377 max usecs: 385.000, spare = 20948.000
load = 2.2540 max usecs: 399.000, spare = 20934.000