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

Problème Jack-Rosengarden

Envoyé par Sappy le Sat 17 Apr 2010 20:36 Articles: 6

Salut,

Je suis débutant ( 1 mois que j'ai quitté Windows) mais je n'arrive pas à faire fonctionner Jack, ni rosengarden et le noyau RT ne fonctionne jamais pourtant je l'active au démarrage.
Je n'ai aucun son qui sort.

J'ai suivi le tuto pour optimé ubuntu 9.10.

20:06:02.111 Baie de brassage désactivée.
20:06:02.137 Réinitialisation des statistiques.
20:06:02.196 Changement du graphique des connexions ALSA.
20:06:02.477 Changement des connexions ALSA.
20:06:07.227 Changement du graphique des connexions ALSA.
20:06:07.284 Changement des connexions ALSA.
20:06:20.920 Changement du graphique des connexions ALSA.
20:06:21.111 Changement des connexions ALSA.
20:06:26.719 Script de démarrage...
20:06:26.720 artsshell -q terminate
sh: artsshell: not found
20:06:27.124 Script de démarrage terminé avec statut de sortie=32512.
20:06:27.124 JACK démarre...
20:06:27.125 /usr/bin/jackd -P89 -p128 -t5000 -dalsa -dhw:0,0 -r48000 -p128 -n2 -i2 -o2
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|128|2|48000|2|2|nomon|swmeter|-|32bit
control device hw:0
20:06:27.173 JACK a été démarrer avec le PID=3863.
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
20:06:28.208 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
20:06:28.210 Réinitialisation des statistiques.
20:06:28.211 Client activé.
20:06:28.213 Changement des connexions JACK.
20:06:28.220 Changement du graphique des connexions JACK.
20:06:28.294 Récupération désynchronisation (XRUN) (1).
20:06:30.217 Récupération de désynchronisation (XRUN) (164 sauté).
20:06:32.220 Récupération de désynchronisation (XRUN) (163 sauté).
20:06:34.222 Récupération de désynchronisation (XRUN) (165 sauté).
20:06:36.225 Récupération de désynchronisation (XRUN) (165 sauté).
20:06:38.228 Récupération de désynchronisation (XRUN) (164 sauté).
20:06:40.231 Récupération de désynchronisation (XRUN) (164 sauté).
20:06:42.234 Récupération de désynchronisation (XRUN) (165 sauté).
20:06:44.237 Récupération de désynchronisation (XRUN) (164 sauté).
20:06:44.388 Client désactivé.
20:06:44.389 JACK s'arrête...
jack main caught signal 15
20:06:44.413 JACK a été arrêté avec succès.
20:06:44.414 Script post-extinction...
20:06:44.414 killall jackd
jackd: no process found
20:06:44.833 Script post-extinction terminé avec statut de sortie=256.
20:06:53.458 Script de démarrage...
20:06:53.459 artsshell -q terminate
sh: artsshell: not found
20:06:53.861 Script de démarrage terminé avec statut de sortie=32512.
20:06:53.862 JACK démarre...
20:06:53.863 /usr/bin/jackd -P89 -p128 -t5000 -dalsa -dhw:0,0 -r48000 -p128 -n2 -i2 -o2 -Xseq
20:06:53.880 JACK a été démarrer avec le PID=3887.
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|128|2|48000|2|2|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 128 frames (2.7 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
20:06:53.937 Changement du graphique des connexions ALSA.
20:06:54.999 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
20:06:55.001 Réinitialisation des statistiques.
20:06:55.004 Client activé.
20:06:55.008 Changement des connexions JACK.
20:06:55.021 Changement du graphique des connexions JACK.
20:06:55.022 Récupération désynchronisation (XRUN) (1).
20:06:57.016 Récupération de désynchronisation (XRUN) (165 sauté).
20:06:59.019 Récupération de désynchronisation (XRUN) (164 sauté).
20:07:01.022 Récupération de désynchronisation (XRUN) (165 sauté).
20:07:03.027 Récupération de désynchronisation (XRUN) (165 sauté).
20:07:05.032 Récupération de désynchronisation (XRUN) (165 sau

Si quelqu'un pourrait m'aider ce serait sympa car là je sature.
J'ai lu le site dans tous les sens et je comprends pas où sa cale.

Merci d'avance

++

Lectures: 2571

Messages: Tri: Rechercher :

Envoyé par pianolivier le Sat 17 Apr 2010 21:46 Articles: 3938 France

salut et bienvenue sur LinuxMAO !

on va donc commencer par faire marcher jack correctement :

tu renseigne trop de champs dans la fenetre de configuration de jack, voici les trucs a changer :

pilote MIDI : aucun
nombre de canaux d'entrée/sortie : defaut
timout : 500 ms

profites en pour augmenter la latence dans un premier temps, a réduire seulement que jack est deja fonctionel :

tampon (frame/period) : 1024

relance jack et raconte 😉

Envoyé par Sappy le Sat 17 Apr 2010 22:03 Articles: 6

Salut,

Merci pour ton aide.

J'ai effectué les changements.
J'ai toujours pas de son et je ne vois toujours pas le mode RT apparaitre dans Jack.
Je te met la fenêtre des messages en dessous.

Merci.

++

21:56:03.589 Baie de brassage désactivée.
21:56:03.593 Réinitialisation des statistiques.
21:56:03.657 Changement du graphique des connexions ALSA.
21:56:03.957 Changement des connexions ALSA.
21:58:10.283 Script de démarrage...
21:58:10.284 artsshell -q terminate
sh: artsshell: not found
21:58:10.687 Script de démarrage terminé avec statut de sortie=32512.
21:58:10.687 JACK démarre...
21:58:10.688 /usr/bin/jackd -P89 -p128 -dalsa -dhw:0,0 -r48000 -p1024 -n2
21:58:10.699 JACK a été démarrer avec le PID=7292.
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
21:58:11.873 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
21:58:11.875 Réinitialisation des statistiques.
21:58:11.877 Client activé.
21:58:11.879 Changement des connexions JACK.
21:58:11.886 Changement du graphique des connexions JACK.
21:58:11.958 Récupération désynchronisation (XRUN) (1).
21:58:13.883 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:15.885 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:17.888 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:19.891 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:21.894 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:23.897 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:25.900 Récupération de désynchronisation (XRUN) (39 sauté).
21:58:26.574 Client désactivé.
21:58:26.576 JACK s'arrête...
jack main caught signal 15
21:58:26.623 JACK a été arrêté avec succès.
21:58:26.626 Script post-extinction...
21:58:26.628 killall jackd
jackd: no process found
21:58:27.050 Script post-extinction terminé avec statut de sortie=256.
21:59:00.056 Script de démarrage...
21:59:00.057 artsshell -q terminate
sh: artsshell: not found
21:59:00.460 Script de démarrage terminé avec statut de sortie=32512.
21:59:00.460 JACK démarre...
21:59:00.461 /usr/bin/jackd -P89 -p128 -dalsa -dhw:0,0 -r48000 -p1024 -n2
21:59:00.467 JACK a été démarrer avec le PID=7326.
no message buffer overruns
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
21:59:01.597 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
21:59:01.598 Réinitialisation des statistiques.
21:59:01.600 Client activé.
21:59:01.602 Changement des connexions JACK.
21:59:01.609 Changement du graphique des connexions JACK.
21:59:01.654 Récupération désynchronisation (XRUN) (1).
21:59:03.605 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:05.608 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:07.612 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:09.376 Changement du graphique des connexions JACK.
21:59:09.621 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:09.935 Changement du graphique des connexions JACK.
21:59:09.962 Changement du graphique des connexions ALSA.
21:59:10.027 Changement des connexions JACK.
21:59:10.038 Changement des connexions ALSA.
21:59:10.244 Changement des connexions ALSA.
21:59:11.001 Changement du graphique des connexions JACK.
21:59:11.048 Changement des connexions JACK.
21:59:11.655 Récupération de désynchronisation (XRUN) (37 sauté).
21:59:13.660 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:15.664 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:17.669 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:19.674 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:21.680 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:23.684 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:23.717 Changement du graphique des connexions ALSA.
21:59:23.887 Changement des connexions ALSA.
21:59:25.691 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:27.695 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:29.698 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:31.701 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:33.704 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:35.707 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:37.710 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:39.713 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:41.717 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:43.720 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:45.723 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:47.726 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:49.730 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:51.733 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:53.737 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:55.740 Récupération de désynchronisation (XRUN) (38 sauté).
21:59:57.743 Récupération de désynchronisation (XRUN) (39 sauté).
21:59:59.746 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:01.750 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:03.753 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:05.757 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:07.760 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:09.763 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:11.766 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:13.769 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:15.835 Récupération de désynchronisation (XRUN) (40 sauté).
22:00:17.839 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:19.843 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:21.856 Récupération de désynchronisation (XRUN) (39 sauté).
22:00:22.263 Client désactivé.
22:00:22.267 JACK s'arrête...
jack main caught signal 15
22:00:22.293 JACK a été arrêté avec succès.
22:00:22.294 Script post-extinction...
22:00:22.295 killall jackd
jackd: no process found
22:00:22.713 Script post-extinction terminé avec statut de sortie=256.

Envoyé par pianolivier le Sat 17 Apr 2010 22:25 Articles: 3938 France

d'habitude je ne conseille pas d'activer directement le mode RT lorsque l'on commence avec des messages d'erreurs, le probleme ici c'est que je ne vois pas trop quelle est l'erreur (pas de message 😕)
le seul truc visible c'est que du as plein de sauts de signal, c'est peut etre ca qui fait arreter jack

donc dans ton cas il serai bon d'activer le temps réel, simplement en cochant "temps réel" dans la fenetre de configuration

aussi, je suspecte que tu l'ai deja fait et qu'il n'est pas pris en compte, j'ai ma petite idée la dessus, quelle est ta version de qjackctl ?

profites en aussi pour cocher l'option "verbose messages" (explicite), pour avoir un peu plus d'infos dans le log

Envoyé par Sappy le Sat 17 Apr 2010 22:32 Articles: 6

Le temps réel est activé.

Pour la version de Jack :
JACK Audio Connection Kit - Qt GUI Interface
Version: 0.3.6
Compilation: Mar 9 2010 20:05:25

J'ai juste démarré jack.

Merci pour ton aide.

22:31:02.910 Baie de brassage désactivée.
22:31:02.912 Réinitialisation des statistiques.
22:31:02.938 Changement du graphique des connexions ALSA.
22:31:03.263 Changement des connexions ALSA.
22:31:04.511 Script de démarrage...
22:31:04.513 artsshell -q terminate
sh: artsshell: not found
22:31:04.916 Script de démarrage terminé avec statut de sortie=32512.
22:31:04.917 JACK démarre...
22:31:04.918 /usr/bin/jackd -v -P89 -p128 -dalsa -dhw:0,0 -r48000 -p1024 -n2
22:31:04.924 JACK a été démarrer avec le PID=8424.
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
start poll on 3 fd's
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
new client: alsa_pcm, id = 1 type 1 @ 0x98cf5f8 fd = -1
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now alsa_pcm active ? 1 client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
8424 waiting for signals
22:31:06.075 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
22:31:06.076 Réinitialisation des statistiques.
22:31:06.078 Client activé.
22:31:06.080 Changement des connexions JACK.
22:31:06.086 Changement du graphique des connexions JACK.
server thread back from poll
new client: qjackctl, id = 2 type 2 @ 0xb7818000 fd = 14
start poll on 4 fd's
server thread back from poll
new client qjackctl using 15 for events
start poll on 4 fd's
server thread back from poll
++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now alsa_pcm active ? 1 client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1 client event poll on 15 for qjackctl starts at 9725364057
back from client event poll after 128 usecs
client qjackctl: wait_fd=9, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
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
22:31:06.137 Récupération désynchronisation (XRUN) (1).
client event poll on 15 for qjackctl starts at 9725404235
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9725455182
back from client event poll after 104 usecs
client event poll on 15 for qjackctl starts at 9725505128
back from client event poll after 898 usecs
client event poll on 15 for qjackctl starts at 9725555121
back from client event poll after 76 usecs
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
client event poll on 15 for qjackctl starts at 9725605128
back from client event poll after 898 usecs
client event poll on 15 for qjackctl starts at 9725655119
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9725705126
back from client event poll after 84 usecs
client event poll on 15 for qjackctl starts at 9725755171
back from client event poll after 883 usecs
client event poll on 15 for qjackctl starts at 9725805131
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9725855128
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9725905129
back from client event poll after 921 usecs
client event poll on 15 for qjackctl starts at 9725955122
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9726005126
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9726055119
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9726105130
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9726155122
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9726205127
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9726255288
back from client event poll after 184 usecs
client event poll on 15 for qjackctl starts at 9726305299
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9726355131
back from client event poll after 786 usecs
client event poll on 15 for qjackctl starts at 9726405289
back from client event poll after 159 usecs
client event poll on 15 for qjackctl starts at 9726455293
back from client event poll after 172 usecs
client event poll on 15 for qjackctl starts at 9726505144
back from client event poll after 815 usecs
client event poll on 15 for qjackctl starts at 9726555125
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9726605149
back from client event poll after 809 usecs
client event poll on 15 for qjackctl starts at 9726655128
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9726705127
back from client event poll after 84 usecs
client event poll on 15 for qjackctl starts at 9726755298
back from client event poll after 181 usecs
client event poll on 15 for qjackctl starts at 9726806186
back from client event poll after 839 usecs
client event poll on 15 for qjackctl starts at 9726856249
back from client event poll after 70 usecs
client event poll on 15 for qjackctl starts at 9726906268
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9726956244
back from client event poll after 72 usecs
client event poll on 15 for qjackctl starts at 9727006241
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9727056262
back from client event poll after 73 usecs
client event poll on 15 for qjackctl starts at 9727106244
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9727156241
back from client event poll after 68 usecs
client event poll on 15 for qjackctl starts at 9727206279
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9727256298
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9727306128
back from client event poll after 190 usecs
client event poll on 15 for qjackctl starts at 9727356128
back from client event poll after 81 usecs
22:31:08.083 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 9727406131
back from client event poll after 895 usecs
client event poll on 15 for qjackctl starts at 9727456126
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9727506126
back from client event poll after 867 usecs
client event poll on 15 for qjackctl starts at 9727556133
back from client event poll after 74 usecs
client event poll on 15 for qjackctl starts at 9727606129
back from client event poll after 893 usecs
client event poll on 15 for qjackctl starts at 9727656119
back from client event poll after 86 usecs
client event poll on 15 for qjackctl starts at 9727706144
back from client event poll after 881 usecs
client event poll on 15 for qjackctl starts at 9727756118
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9727806148
back from client event poll after 877 usecs
client event poll on 15 for qjackctl starts at 9727856120
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9727906147
back from client event poll after 879 usecs
client event poll on 15 for qjackctl starts at 9727956120
back from client event poll after 88 usecs
client event poll on 15 for qjackctl starts at 9728006123
back from client event poll after 91 usecs
client event poll on 15 for qjackctl starts at 9728056119
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9728106129
back from client event poll after 896 usecs
client event poll on 15 for qjackctl starts at 9728157255
back from client event poll after 70 usecs
client event poll on 15 for qjackctl starts at 9728207451
back from client event poll after 67 usecs
client event poll on 15 for qjackctl starts at 9728258207
back from client event poll after 127 usecs
client event poll on 15 for qjackctl starts at 9728308855
back from client event poll after 116 usecs
client event poll on 15 for qjackctl starts at 9728363306
back from client event poll after 3390 usecs
client event poll on 15 for qjackctl starts at 9728413130
back from client event poll after 541 usecs
client event poll on 15 for qjackctl starts at 9728464273
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9728514135
back from client event poll after 611 usecs
client event poll on 15 for qjackctl starts at 9728564159
back from client event poll after 190 usecs
client event poll on 15 for qjackctl starts at 9728614131
back from client event poll after 1019 usecs
client event poll on 15 for qjackctl starts at 9728664130
back from client event poll after 92 usecs
client event poll on 15 for qjackctl starts at 9728714126
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9728764131
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9728814128
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9728864140
back from client event poll after 559 usecs
client event poll on 15 for qjackctl starts at 9728914125
back from client event poll after 87 usecs
client event poll on 15 for qjackctl starts at 9728964127
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9729014164
back from client event poll after 601 usecs
client event poll on 15 for qjackctl starts at 9729064128
back from client event poll after 69 usecs
client event poll on 15 for qjackctl starts at 9729115283
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9729165142
back from client event poll after 90 usecs
client event poll on 15 for qjackctl starts at 9729215128
back from client event poll after 84 usecs
client event poll on 15 for qjackctl starts at 9729265270
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9729315269
back from client event poll after 101 usecs
client event poll on 15 for qjackctl starts at 9729365259
back from client event poll after 84 usecs
22:31:10.109 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 9729415205
back from client event poll after 824 usecs
client event poll on 15 for qjackctl starts at 9729465128
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9729515126
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9729565136
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9729615126
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9729665143
back from client event poll after 86 usecs
client event poll on 15 for qjackctl starts at 9729715129
back from client event poll after 1076 usecs
client event poll on 15 for qjackctl starts at 9729765268
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9729815127
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9729865163
back from client event poll after 1034 usecs
client event poll on 15 for qjackctl starts at 9729915167
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9729965246
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9730016257
back from client event poll after 944 usecs
client event poll on 15 for qjackctl starts at 9730066249
back from client event poll after 831 usecs
client event poll on 15 for qjackctl starts at 9730116251
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9730166242
back from client event poll after 90 usecs
client event poll on 15 for qjackctl starts at 9730216265
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9730266243
back from client event poll after 945 usecs
client event poll on 15 for qjackctl starts at 9730317215
back from client event poll after 202 usecs
client event poll on 15 for qjackctl starts at 9730367243
back from client event poll after 120 usecs
client event poll on 15 for qjackctl starts at 9730417243
back from client event poll after 87 usecs
client event poll on 15 for qjackctl starts at 9730467246
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9730517249
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9730567248
back from client event poll after 120 usecs
client event poll on 15 for qjackctl starts at 9730617251
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9730667241
back from client event poll after 835 usecs
client event poll on 15 for qjackctl starts at 9730717246
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9730767235
back from client event poll after 122 usecs
client event poll on 15 for qjackctl starts at 9730817242
back from client event poll after 833 usecs
client event poll on 15 for qjackctl starts at 9730867247
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9730917233
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9730967123
back from client event poll after 88 usecs
client event poll on 15 for qjackctl starts at 9731017145
back from client event poll after 84 usecs
client event poll on 15 for qjackctl starts at 9731067142
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9731117131
back from client event poll after 940 usecs
client event poll on 15 for qjackctl starts at 9731167131
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9731217146
back from client event poll after 91 usecs
client event poll on 15 for qjackctl starts at 9731267126
back from client event poll after 89 usecs
client event poll on 15 for qjackctl starts at 9731317218
back from client event poll after 105 usecs
client event poll on 15 for qjackctl starts at 9731367246
back from client event poll after 77 usecs
22:31:12.113 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 9731418191
back from client event poll after 84 usecs
client event poll on 15 for qjackctl starts at 9731468257
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9731518244
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9731568244
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9731618247
back from client event poll after 70 usecs
client event poll on 15 for qjackctl starts at 9731668129
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9731718127
back from client event poll after 73 usecs
client event poll on 15 for qjackctl starts at 9731768148
back from client event poll after 71 usecs
client event poll on 15 for qjackctl starts at 9731818125
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9731868126
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9731918143
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9731968267
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9732018125
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9732068292
back from client event poll after 191 usecs
client event poll on 15 for qjackctl starts at 9732118271
back from client event poll after 79 usecs
client event poll on 15 for qjackctl starts at 9732168128
back from client event poll after 82 usecs
client event poll on 15 for qjackctl starts at 9732218296
back from client event poll after 97 usecs
client event poll on 15 for qjackctl starts at 9732268131
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9732318167
back from client event poll after 97 usecs
client event poll on 15 for qjackctl starts at 9732368151
back from client event poll after 854 usecs
client event poll on 15 for qjackctl starts at 9732418264
back from client event poll after 95 usecs
client event poll on 15 for qjackctl starts at 9732468241
back from client event poll after 843 usecs
client event poll on 15 for qjackctl starts at 9732519274
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9732569248
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9732619248
back from client event poll after 945 usecs
client event poll on 15 for qjackctl starts at 9732669262
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9732719175
back from client event poll after 72 usecs
client event poll on 15 for qjackctl starts at 9732769241
back from client event poll after 73 usecs
client event poll on 15 for qjackctl starts at 9732819246
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9732869244
back from client event poll after 85 usecs
client event poll on 15 for qjackctl starts at 9732919147
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9732970098
back from client event poll after 90 usecs
client event poll on 15 for qjackctl starts at 9733020272
back from client event poll after 96 usecs
client event poll on 15 for qjackctl starts at 9733070244
back from client event poll after 833 usecs
client event poll on 15 for qjackctl starts at 9733120254
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9733170248
back from client event poll after 87 usecs
client event poll on 15 for qjackctl starts at 9733220253
back from client event poll after 929 usecs
client event poll on 15 for qjackctl starts at 9733270223
back from client event poll after 72 usecs
client event poll on 15 for qjackctl starts at 9733320574
back from client event poll after 218 usecs
client event poll on 15 for qjackctl starts at 9733371265
back from client event poll after 75 usecs
22:31:14.117 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 9733421166
back from client event poll after 94 usecs
client event poll on 15 for qjackctl starts at 9733471147
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9733521637
back from client event poll after 71 usecs
client event poll on 15 for qjackctl starts at 9733572243
back from client event poll after 69 usecs
client event poll on 15 for qjackctl starts at 9733623224
back from client event poll after 233 usecs
client event poll on 15 for qjackctl starts at 9733673244
back from client event poll after 83 usecs
client event poll on 15 for qjackctl starts at 9733724195
back from client event poll after 80 usecs
client event poll on 15 for qjackctl starts at 9733774247
back from client event poll after 69 usecs
client event poll on 15 for qjackctl starts at 9733824279
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9733874252
back from client event poll after 70 usecs
client event poll on 15 for qjackctl starts at 9733924241
back from client event poll after 70 usecs
client event poll on 15 for qjackctl starts at 9733974250
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9734024246
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9734074249
back from client event poll after 74 usecs
client event poll on 15 for qjackctl starts at 9734124244
back from client event poll after 75 usecs
client event poll on 15 for qjackctl starts at 9734174245
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9734225167
back from client event poll after 901 usecs
client event poll on 15 for qjackctl starts at 9734275246
back from client event poll after 76 usecs
client event poll on 15 for qjackctl starts at 9734325176
back from client event poll after 888 usecs
client event poll on 15 for qjackctl starts at 9734375249
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9734425245
back from client event poll after 77 usecs
client event poll on 15 for qjackctl starts at 9734475249
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9734526165
back from client event poll after 81 usecs
client event poll on 15 for qjackctl starts at 9734576244
back from client event poll after 78 usecs
client event poll on 15 for qjackctl starts at 9734627110
back from client event poll after 174 usecs
client event poll on 15 for qjackctl starts at 9734677235
back from client event poll after 839 usecs
client event poll on 15 for qjackctl starts at 9734727267
back from client event poll after 73 usecs
client event poll on 15 for qjackctl starts at 9734779072
back from client event poll after 71 usecs
22:31:15.531 Client désactivé.
22:31:15.532 JACK s'arrête...
server thread back from poll
+++ deactivate qjackctl ++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now alsa_pcm active ? 1 client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 4 fd's
server thread back from poll
marking client qjackctl with SOCKET error state = Not triggered errors = 0
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ... client alsa_pcm error status 0
client qjackctl error status 10000000
removing failed client qjackctl state = Not triggered errors = 10000000
removing client "qjackctl"
removing client "qjackctl" from the processing chain
+++ deactivate qjackctl ++ jack_sort_graph ++ jack_rechain_graph(): +++ client is now alsa_pcm active ? 1 client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 3 fd's
jack main caught signal 15
starting server engine shutdown
stopping driver
server thread back from poll
unloading driver
freeing shared port segments
stopping server thread
last xrun delay: 0.000 usecs
max delay reported by backend: 564.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
WARNING: 1 message buffer overruns!
cleaning up shared memory
cleaning up files
unregistering server `default'
22:31:15.647 JACK a été arrêté avec succès.
22:31:15.648 Script post-extinction...
22:31:15.650 killall jackd

Envoyé par pianolivier le Sat 17 Apr 2010 22:55 Articles: 3938 France

ok

pour commencer, ce sujet devient un peu long a scroller, édite tes messages précédents et utilise la syntaxe
*-{QUOTE()}ton log{QUOTE}
ou
*-{CODE()}ton log{CODE}
ce qui donne une boite repliable :

[+](plus d'info sur la syntaxe dans le manuel du site)

ensuite, pour le temps réel, j'ai deja rencontré ce probleme avec un autre utilisateur d'ubuntu sur le forum y'a pas longtemps, et tout ca c'est la faute à ubuntu !
qjackctl 0.3.6 (l'interface de jack) est incompatible avec les versions de jack inferieures à 0.118.0 ,plus d'infos dans cet édito

(qjackctl 0.3.6 est) Conforme avec jackd = 0.118.0 qui démarre maintenant en temps réel par défaut ; l'utilisation de l'option -R n'est maintenant plus supportée ; il faut utiliser l'option -r pour démarrer jack en mode non-temps-réel.

il te faut donc installer une version précédente de qjackctl
ou alors lancer jack en ligne de commande en attendant :

Copy to clipboard

/usr/bin/jackd -v -R -P89 -p128 -dalsa -dhw:0,0 -r48000 -p1024 -n2

Envoyé par Sappy le Sat 17 Apr 2010 23:20 Articles: 6

Voilà, j'ai changé de version, j'ai pris la 0.3.4

Il démarre bien, je vois le TR qui clignote et puis devient fixe de couleur jaune.
Et puis sa bloque et je suis obligé de quitter par le moniteur systéme.
Je n'ai pas le temps d'ourvir Rosegarden.
Pour pouvoir prendre les logs j'ai du quitter avant que sa plante sinon je sais plus rien
prendre.

Je pense que le problème maintenant c'est : jackd watchdog: timeout
(fin du log que j'ai pas su prendre )

En tout ca sa avance bien, merci pour ton aide.

Copy to clipboard

23:16:53.383 Baie de brassage désactivée.
23:16:53.481 Réinitialisation des statistiques.
23:16:53.524 Changement du graphique des connexions ALSA.
23:16:53.788 Changement des connexions ALSA.
23:17:04.649 Script de démarrage...
23:17:04.650 artsshell -q terminate
sh: artsshell: not found
23:17:05.053 Script de démarrage terminé avec statut de sortie=32512.
23:17:05.053 JACK démarre...
23:17:05.054 /usr/bin/jackd -v -R -P89 -p128 -dalsa -dhw:0,0 -r48000 -p1024 -n2
getting driver descriptor from /usr/lib/jack/jack_dummy.so
getting driver descriptor from /usr/lib/jack/jack_freebob.so
23:17:05.067 JACK a été démarrer avec le PID=10430.
getting driver descriptor from /usr/lib/jack/jack_oss.so
getting driver descriptor from /usr/lib/jack/jack_firewire.so
no message buffer overruns
getting driver descriptor from /usr/lib/jack/jack_net.so
getting driver descriptor from /usr/lib/jack/jack_alsa.so
jackd 0.116.1
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
server `default' registered
registered builtin port type 32 bit float mono audio
registered builtin port type 8 bit raw midi
clock source = system clock via clock_gettime
start poll on 3 fd's
loading driver ..
apparent rate = 48000
creating alsa driver ... hw:0,0|hw:0,0|1024|2|48000|0|0|nomon|swmeter|-|32bit
control device hw:0
new client: alsa_pcm, id = 1 type 1 @ 0x8a0f5f8 fd = -1
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
new buffer size 1024
registered port system:capture_1, offset = 4096
registered port system:capture_2, offset = 8192
registered port system:playback_1, offset = 0
registered port system:playback_2, offset = 0
registered port system:playback_3, offset = 0
registered port system:playback_4, offset = 0
registered port system:playback_5, offset = 0
registered port system:playback_6, offset = 0
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
10430 waiting for signals
23:17:06.251 Configuration du serveur enregistrée dans "/home/laurent/.jackdrc".
23:17:06.252 Réinitialisation des statistiques.
23:17:06.292 Client activé.
23:17:06.295 Changement des connexions JACK.
23:17:06.303 Changement du graphique des connexions JACK.
server thread back from poll
new client: qjackctl, id = 2 type 2 @ 0xb7878000 fd = 14
start poll on 4 fd's
server thread back from poll
new client qjackctl using 15 for events
start poll on 4 fd's
server thread back from poll
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
+++ client is now qjackctl active ? 1
client qjackctl: start_fd=7, execution_order=0.
client event poll on 15 for qjackctl starts at 12485578658
back from client event poll after 92 usecs
client qjackctl: wait_fd=9, execution_order=1 (last client).
-- jack_rechain_graph()
-- jack_sort_graph
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
client event poll on 15 for qjackctl starts at 12485603141
back from client event poll after 42 usecs
23:17:06.378 Récupération désynchronisation (XRUN) (1).
client event poll on 15 for qjackctl starts at 12485653274
back from client event poll after 42 usecs
client event poll on 15 for qjackctl starts at 12485703290
back from client event poll after 31 usecs
client event poll on 15 for qjackctl starts at 12485753267
back from client event poll after 43 usecs
server thread back from poll
start poll on 4 fd's
server thread back from poll
start poll on 4 fd's
client event poll on 15 for qjackctl starts at 12485803281
back from client event poll after 41 usecs
client event poll on 15 for qjackctl starts at 12485853261
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12485903245
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12485953243
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12486003266
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12486053273
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12486103248
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12486153255
back from client event poll after 51 usecs
client event poll on 15 for qjackctl starts at 12486203256
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12486253242
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12486303262
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12486353253
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12486403258
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12486453240
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12486503141
back from client event poll after 61 usecs
client event poll on 15 for qjackctl starts at 12486553244
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12486603246
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12486653232
back from client event poll after 64 usecs
client event poll on 15 for qjackctl starts at 12486703109
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12486753091
back from client event poll after 61 usecs
client event poll on 15 for qjackctl starts at 12486803116
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12486853095
back from client event poll after 63 usecs
client event poll on 15 for qjackctl starts at 12486903244
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12486953234
back from client event poll after 60 usecs
client event poll on 15 for qjackctl starts at 12487003245
back from client event poll after 47 usecs
client event poll on 15 for qjackctl starts at 12487053246
back from client event poll after 57 usecs
client event poll on 15 for qjackctl starts at 12487103245
back from client event poll after 58 usecs
client event poll on 15 for qjackctl starts at 12487153235
back from client event poll after 64 usecs
client event poll on 15 for qjackctl starts at 12487203266
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12487253244
back from client event poll after 61 usecs
client event poll on 15 for qjackctl starts at 12487303264
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12487353276
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12487403246
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12487453244
back from client event poll after 46 usecs
client event poll on 15 for qjackctl starts at 12487503121
back from client event poll after 58 usecs
client event poll on 15 for qjackctl starts at 12487553096
back from client event poll after 61 usecs
23:17:08.298 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 12487603245
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12487653248
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12487703267
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12487753248
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12487803262
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12487853266
back from client event poll after 62 usecs
client event poll on 15 for qjackctl starts at 12487903269
back from client event poll after 62 usecs
client event poll on 15 for qjackctl starts at 12487953253
back from client event poll after 62 usecs
client event poll on 15 for qjackctl starts at 12488003266
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12488053248
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12488103254
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12488153250
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12488203242
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12488253278
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12488303266
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12488353248
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12488403247
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12488453243
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12488503245
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12488553293
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12488603247
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12488653242
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12488703259
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12488753279
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12488803250
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12488853273
back from client event poll after 57 usecs
client event poll on 15 for qjackctl starts at 12488903243
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12488953279
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12489003242
back from client event poll after 44 usecs
client event poll on 15 for qjackctl starts at 12489053284
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12489103249
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12489153277
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12489203243
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12489253265
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12489303257
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12489353121
back from client event poll after 68 usecs
client event poll on 15 for qjackctl starts at 12489403112
back from client event poll after 68 usecs
client event poll on 15 for qjackctl starts at 12489453122
back from client event poll after 58 usecs
client event poll on 15 for qjackctl starts at 12489503241
back from client event poll after 52 usecs
client event poll on 15 for qjackctl starts at 12489553236
back from client event poll after 51 usecs
23:17:10.302 Récupération de désynchronisation (XRUN) (39 sauté).
client event poll on 15 for qjackctl starts at 12489603139
back from client event poll after 50 usecs
client event poll on 15 for qjackctl starts at 12489653246
back from client event poll after 53 usecs
client event poll on 15 for qjackctl starts at 12489703249
back from client event poll after 50 usecs
client event poll on 15 for qjackctl starts at 12489753252
back from client event poll after 51 usecs
client event poll on 15 for qjackctl starts at 12489803247
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12489853247
back from client event poll after 54 usecs
client event poll on 15 for qjackctl starts at 12489903242
back from client event poll after 56 usecs
client event poll on 15 for qjackctl starts at 12489953270
back from client event poll after 55 usecs
client event poll on 15 for qjackctl starts at 12490003233
back from client event poll after 59 usecs
client event poll on 15 for qjackctl starts at 12490053118
back from client event poll after 58 usecs
23:17:10.777 Client désactivé.
23:17:10.778 JACK s'arrête...
server thread back from poll
+++ deactivate qjackctl
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
start poll on 4 fd's
server thread back from poll
marking client qjackctl with SOCKET error state = Not triggered errors = 0
trying to lock graph to remove 1 problems
we have problem clients (problems = 1
++ Removing failed clients ...
client alsa_pcm error status 0
client qjackctl error status 10000000
removing failed client qjackctl state = Not triggered errors = 10000000
removing client "qjackctl"
removing client "qjackctl" from the processing chain
+++ deactivate qjackctl
++ jack_sort_graph
++ jack_rechain_graph():
+++ client is now alsa_pcm active ? 1
client alsa_pcm: internal client, execution_order=0.
-- jack_rechain_graph()
-- jack_sort_graph
-- Removing failed clients ...
after removing clients, problems = 0
start poll on 3 fd's
jack main caught signal 15
starting server engine shutdown
stopping driver
server thread back from poll
unloading driver
freeing shared port segments
stopping server thread
stopping watchdog thread
last xrun delay: 33.000 usecs
max delay reported by backend: 33.000 usecs
freeing engine shared memory
max usecs: 0.000, engine deleted
cleaning up shared memory
cleaning up files
unregistering server `default'
23:17:10.907 JACK a été arrêté avec succès.
23:17:10.908 Script post-extinction...
23:17:10.909 killall jackd
jackd: no process found
23:17:11.328 Script post-extinction terminé avec statut de sortie=256.

Envoyé par pianolivier le Mon 19 Apr 2010 14:33 Articles: 3938 France

pour commencer, ce sujet devient un peu long a scroller, édite tes messages précédents et utilise la syntaxe

[+]ou

[+]ce qui donne une boite repliable

[+]
essaye de lancer jack en changeant l'option timeout de 500 à 1000 ms

Aller au forum:

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

Thread actions

Contenu en relation