Senbee ha scritto:(vedo dagli screenshot che hai due istanze di QSynth, vuol dire che comunque un po' ci hai smanettato ^_^)
...un poooo?!?! o.o!
;);) (davvero, è qualche settimana che ci provo, ma son piantato, se no non ti avrei disturbato qui
)
Intanto devo dirti che il tutto lo sto facendo su una slackware con kde 4.5.5 (ho anche ubuntu in un altra partizione, al limite se da qua non riesco provo anche da ubuntu!)
Prima di tutto prova a resettarlo con quella riga di comando che c'è scritta nell'ultimo paragrafo dedicato a QSynth. Se non parte, postaci di nuovo l'errore per favore.
purtroppo l'errore che ho riportato è già quello dopo aver resettato: in sostanza ho chiuso qsynth, eliminato quel file .conf, ho riaperto qsynth e ho copiato e incollato il messaggio!
Inoltre, prova a togliere "Realtime" dalle impostazioni di Jack, e prova a portare Fotogrammi/Periodo a 1024 (goiusto per portare Jack a una situazione lenta e inefficiente ma che ha più probabilità di partire senza problemi).
l'ho fatto e ho riavviato jack e qsynth, ma la situazione è sempre la stessa... ti riporto i messaggi di qsynth e di jack:
qsynth:
Codice: Seleziona tutto
12:13:28.824 Qsynth1: Creating synthesizer engine...
12:13:28.855 Qsynth1: Loading soundfont: "/usr/share/sounds/sf2/PC51f.sf2" (bank offset 0)...
12:13:29.037 Qsynth1: Creating audio driver (jack)...
12:13:29.059 Qsynth1: Creating MIDI router (alsa_seq)...
12:13:29.061 Qsynth1: Creating MIDI driver (alsa_seq)...
12:13:29.064 Qsynth1: Creating MIDI player...
12:13:29.067 Qsynth1: Synthesizer engine started.
12:13:29.068 Qsynth2: Creating synthesizer engine...
12:13:29.109 Qsynth2: Loading soundfont: "/usr/share/sounds/sf2/Unison.sf2" (bank offset 0)...
12:13:29.389 Qsynth2: Creating audio driver (jack)...
12:13:29.412 Qsynth2: Creating MIDI router (alsa_seq)...
12:13:29.413 Qsynth2: Creating MIDI driver (alsa_seq)...
12:13:29.414 Qsynth2: Creating MIDI player...
12:13:29.415 Qsynth2: fluid_synth_set_reverb_on(1)
12:13:29.415 Qsynth2: fluid_synth_set_chorus_on(1)
12:13:29.416 Qsynth2: fluid_synth_set_gain(1)
12:13:29.416 Qsynth2: fluid_synth_set_reverb(0.2,0,1,0.9)
12:13:29.417 Qsynth2: fluid_synth_set_chorus(3,1,0.3,8,0)
12:13:29.417 Qsynth2: Synthesizer engine started.
12:13:29.418 Qsynth1: fluid_synth_set_gain(1.03)
12:13:29.418 Qsynth1: fluid_synth_set_reverb(0.61,0.47,52,0.82)
12:13:29.419 Qsynth1: fluid_synth_set_chorus(46,0.78,2.34,8,0)
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
cannot use real-time scheduling (FIFO at priority 5) [for thread -1338647696, from thread -1338647696] (1: Operation not permitted)
fluidsynth: warning: Failed to set thread to high priority
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: warning: Ignoring sample *KPianoB5: can't use ROM samples
cannot use real-time scheduling (FIFO at priority 5) [for thread -1386652816, from thread -1386652816] (1: Operation not permitted)
fluidsynth: warning: Instrument not found on channel 9 [bank=0 prog=9], substituted [bank=0 prog=0]
fluidsynth: warning: Instrument not found on channel 9 [bank=0 prog=9], substituted [bank=0 prog=0]
fluidsynth: warning: Failed to set thread to high priority
zombified - calling shutdown handler
fluidsynth: error: Help! Lost the connection to the JACK server
jack (dal momento in cui ho aperto qsynth) :
Codice: Seleziona tutto
new client: qsynth, id = 3 type 2 @ 0xb42e3000 fd = 18
start poll on 5 fd's
server thread back from poll
new client qsynth using 19 for events
start poll on 5 fd's
server thread back from poll
registered port qsynth:l_00, offset = 12288
start poll on 5 fd's
server thread back from poll
registered port qsynth:r_00, offset = 16384
start poll on 5 fd's
12:13:29.061 JACK connection graph change.
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now qsynth active ? 1
client qsynth: start_fd=7, execution_order=0.
client event poll on 19 for qsynth starts at 3559196267
back from client event poll after 68 usecs
client qsynth: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559196385
back from client event poll after 6 usecs
client event poll on 19 for qsynth starts at 3559196399
back from client event poll after 43 usecs
client event poll on 19 for qsynth starts at 3559196452
back from client event poll after 27 usecs
client event poll on 16 for qjackctl starts at 3559196509
back from client event poll after 6 usecs
-- jack_sort_graph
client event poll on 19 for qsynth starts at 3559196525
back from client event poll after 45 usecs
client event poll on 19 for qsynth starts at 3559196579
back from client event poll after 27 usecs
client event poll on 19 for qsynth starts at 3559196615
back from client event poll after 26 usecs
client event poll on 16 for qjackctl starts at 3559196676
back from client event poll after 5 usecs
client event poll on 16 for qjackctl starts at 3559196711
back from client event poll after 5 usecs
start poll on 5 fd's
server thread back from poll
connect qsynth:l_00 and system:playback_1 (output)
client event poll on 19 for qsynth starts at 3559197187
back from client event poll after 42 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now qsynth active ? 1
client qsynth: start_fd=7, execution_order=0.
client event poll on 19 for qsynth starts at 3559197283
back from client event poll after 51 usecs
client qsynth: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 19 for qsynth starts at 3559197361
back from client event poll after 24 usecs
client event poll on 16 for qjackctl starts at 3559197421
back from client event poll after 9 usecs
client event poll on 16 for qjackctl starts at 3559197459
12:13:29.114 ALSA connection graph change.
12:13:29.116 JACK connection change.
12:13:29.118 ALSA connection change.
12:13:29.123 XRUN callback (1).
12:13:29.125 JACK connection graph change.
back from client event poll after 8 usecs
client event poll on 19 for qsynth starts at 3559197474
back from client event poll after 25 usecs
-- jack_sort_graph
start poll on 5 fd's
server thread back from poll
connect qsynth:r_00 and system:playback_2 (output)
client event poll on 19 for qsynth starts at 3559197567
back from client event poll after 27 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now qsynth active ? 1
client qsynth: start_fd=7, execution_order=0.
client event poll on 19 for qsynth starts at 3559197634
back from client event poll after 41 usecs
client qsynth: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559197721
back from client event poll after 8 usecs
client event poll on 19 for qsynth starts at 3559197738
back from client event poll after 24 usecs
client event poll on 19 for qsynth starts at 3559197774
back from client event poll after 34 usecs
client event poll on 16 for qjackctl starts at 3559197848
12:13:29.162 ALSA connection graph change.
back from client event poll after 8 usecs
-- jack_sort_graph
start poll on 5 fd's
subgraph starting at qsynth timed out (subgraph_wait_fd=14, status = 0, state = Triggered, pollret = 0 revents = 0x0)
at 3559237122 waiting on 14 for 24046 usecs, status = 1 sig = 3559213067 awa = 3559213158 fin = 0 dur=0
checking client alsa_pcm: awake at 0 finished at 0
checking client qjackctl: awake at 0 finished at 0
checking client qsynth: awake at 3559213158 finished at 0
bad status (-1) for client qsynth handling event (type = 8)
client qsynth has timed out
waking server thread
waking server thread
**** alsa_pcm: xrun of at least 1.073 msecs
client event poll on 16 for qjackctl starts at 3559237335
back from client event poll after 29 usecs
waking server thread
server thread back from poll
trying to lock graph to remove 3 problems
we have problem clients (problems = 3
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 0
client qsynth error status 10000001
removing failed client qsynth state = Triggered errors = 10000001
removing client "qsynth"
removing client "qsynth" from the processing chain
DIS-connect qsynth:r_00 and system:playback_2
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now qsynth active ? 1
client qsynth: start_fd=7, execution_order=0.
client qsynth: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559237494
back from client event poll after 21 usecs
client event poll on 16 for qjackctl starts at 3559237551
back from client event poll after 5 usecs
-- jack_sort_graph
client event poll on 16 for qjackctl starts at 3559237591
back from client event poll after 10 usecs
DIS-connect qsynth:l_00 and system:playback_1
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now qsynth active ? 1
client qsynth: start_fd=7, execution_order=0.
client qsynth: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559237677
back from client event poll after 8 usecs
client event poll on 16 for qjackctl starts at 3559237713
back from client event poll after 8 usecs
-- jack_sort_graph
client event poll on 16 for qjackctl starts at 3559237756
back from client event poll after 8 usecs
+++ deactivate qsynth
++ jack_sort_graph
++ jack_rechain_graph():
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559237879
back from client event poll after 8 usecs
client event poll on 16 for qjackctl starts at 3559237915
back from client event poll after 8 usecs
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 4 fd's
client event poll on 16 for qjackctl starts at 3559237957
back from client event poll after 22 usecs
registered port alsa_pcm:FLUID-Synth-(4687)/midi_playback_1, offset = 0
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
new client: Qsynth2, id = 4 type 2 @ 0xb42e3000 fd = 18
start poll on 5 fd's
server thread back from poll
new client Qsynth2 using 19 for events
start poll on 5 fd's
server thread back from poll
registered port Qsynth2:l_00, offset = 12288
start poll on 5 fd's
server thread back from poll
registered port Qsynth2:r_00, offset = 16384
start poll on 5 fd's
12:13:29.413 JACK connection graph change.
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 1
client Qsynth2: start_fd=7, execution_order=0.
client event poll on 19 for Qsynth2 starts at 3559547653
back from client event poll after 50 usecs
client Qsynth2: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559547728
back from client event poll after 26 usecs
client event poll on 19 for Qsynth2 starts at 3559547768
back from client event poll after 33 usecs
client event poll on 19 for Qsynth2 starts at 3559547814
back from client event poll after 32 usecs
client event poll on 16 for qjackctl starts at 3559547859
back from client event poll after 16 usecs
-- jack_sort_graph
client event poll on 19 for Qsynth2 starts at 3559547894
back from client event poll after 40 usecs
client event poll on 19 for Qsynth2 starts at 3559547946
back from client event poll after 38 usecs
client event poll on 19 for Qsynth2 starts at 3559547996
back from client event poll after 58 usecs
client event poll on 16 for qjackctl starts at 3559548068
back from client event poll after 23 usecs
client event poll on 16 for qjackctl starts at 3559548131
back from client event poll after 17 usecs
start poll on 5 fd's
server thread back from poll
connect Qsynth2:l_00 and system:playback_1 (output)
client event poll on 19 for Qsynth2 starts at 3559548576
back from client event poll after 28 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 1
client Qsynth2: start_fd=7, execution_order=0.
client event poll on 19 for Qsynth2 starts at 3559548644
back from client event poll after 62 usecs
client Qsynth2: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 19 for Qsynth2 starts at 3559548727
back from client event poll after 37 usecs
client event poll on 16 for qjackctl starts at 3559548779
back from client event poll after 20 usecs
client event poll on 16 for qjackctl starts at 3559548836
12:13:29.439 ALSA connection graph change.
back from client event poll after 8 usecs
client event poll on 19 for Qsynth2 starts at 3559548854
back from client event poll after 27 usecs
-- jack_sort_graph
start poll on 5 fd's
server thread back from poll
connect Qsynth2:r_00 and system:playback_2 (output)
client event poll on 19 for Qsynth2 starts at 3559548955
back from client event poll after 37 usecs
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 1
client Qsynth2: start_fd=7, execution_order=0.
client event poll on 19 for Qsynth2 starts at 3559549074
back from client event poll after 1607 usecs
client Qsynth2: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559550719
back from client event poll after 26 usecs
client event poll on 19 for Qsynth2 starts at 3559550762
back from client event poll after 28 usecs
client event poll on 19 for Qsynth2 starts at 3559550804
back from client event poll after 32 usecs
client event poll on 16 for qjackctl starts at 3559550850
back from client event poll after 17 usecs
-- jack_sort_graph
start poll on 5 fd's
subgraph starting at Qsynth2 timed out (subgraph_wait_fd=14, status = 0, state = Triggered, pollret = 0 revents = 0x0)
at 3559587107 waiting on 14 for 24036 usecs, status = 1 sig = 3559563062 awa = 3559563114 fin = 0 dur=0
checking client alsa_pcm: awake at 0 finished at 0
checking client qjackctl: awake at 0 finished at 0
checking client Qsynth2: awake at 3559563114 finished at 0
client Qsynth2 has timed out
waking server thread
server thread back from poll
trying to lock graph to remove 1 problems
waking server thread
**** alsa_pcm: xrun of at least 1.157 msecs
client event poll on 16 for qjackctl starts at 3559587262
back from client event poll after 21 usecs
registered port alsa_pcm:FLUID-Synth-(Qsynth2)/midi_playback_1, offset = 0
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 0
client Qsynth2 error status 1
client failure: client Qsynth2 state = Triggered errors = 1
removing client "Qsynth2" from the processing chain
DIS-connect Qsynth2:r_00 and system:playback_2
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 1
client Qsynth2: start_fd=7, execution_order=0.
client Qsynth2: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559587495
back from client event poll after 8 usecs
client event poll on 16 for qjackctl starts at 3559587544
back from client event poll after 7 usecs
-- jack_sort_graph
client event poll on 16 for qjackctl starts at 3559587597
back from client event poll after 8 usecs
DIS-connect Qsynth2:l_00 and system:playback_1
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 1
client Qsynth2: start_fd=7, execution_order=0.
client Qsynth2: wait_fd=14, execution_order=1 (last client).
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559587690
back from client event poll after 7 usecs
client event poll on 16 for qjackctl starts at 3559587736
back from client event poll after 7 usecs
-- jack_sort_graph
client event poll on 16 for qjackctl starts at 3559587787
back from client event poll after 8 usecs
+++ deactivate Qsynth2
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now Qsynth2 active ? 0
-- jack_rechain_graph()
client event poll on 16 for qjackctl starts at 3559587857
back from client event poll after 7 usecs
client event poll on 16 for qjackctl starts at 3559587903
back from client event poll after 7 usecs
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 1
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client Qsynth2 error status 0
client qjackctl error status 0
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 5 fd's
server thread back from poll
client event poll on 16 for qjackctl starts at 3559587940
back from client event poll after 15 usecs
start poll on 5 fd's
12:13:29.525 JACK connection change.
12:13:29.526 ALSA connection change.
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
12:13:29.728 XRUN callback (1 skipped).
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
load = 0.1561 max usecs: 35.000, spare = 23184.000
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
server thread back from poll
start poll on 5 fd's
load = 0.1556 max usecs: 36.000, spare = 23183.000
load = 0.1510 max usecs: 34.000, spare = 23185.000
load = 0.1509 max usecs: 35.000, spare = 23184.000
load = 0.1508 max usecs: 35.000, spare = 23184.000
load = 0.1572 max usecs: 38.000, spare = 23181.000
load = 0.1583 max usecs: 37.000, spare = 23182.000
load = 0.1545 max usecs: 35.000, spare = 23184.000
load = 0.1440 max usecs: 31.000, spare = 23188.000
load = 0.1431 max usecs: 33.000, spare = 23186.000
load = 0.1448 max usecs: 34.000, spare = 23185.000
load = 0.1391 max usecs: 31.000, spare = 23188.000
load = 0.1449 max usecs: 35.000, spare = 23184.000
e moo me la spasso un pochino !!
