titixosaure wrote:pour verifier tu tapes:
ulimit -a | grep "rt prio"
et tu dois voir la prio à 20
C'est effectivement le cas pour moi mais qjackctl ne marche toujours pas avec mon utilisateur !!
Voici le message d'erreur :
12:21:59.449 Patchbay deactivated.
12:21:59.458 Statistics reset.
12:21:59.584 MIDI connection graph change.
12:21:59.670 MIDI connection change.
12:22:05.602 Startup script...
12:22:05.602 artsshell -q terminate
12:22:05.845 Startup script terminated with exit status=256.
12:22:05.845 JACK is starting...
12:22:05.845 jackd -R -dalsa -dhw:0 -r44100 -p1024 -n2 -i10 -o10
12:22:05.846 JACK was started with PID=27505 (0x6b71).
jackd 0.102.20
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 = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|10|10|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 1024 frames, buffer = 2 periods
ALSA: final selected sample format for capture: 32bit little-endian
ALSA: cannot set channel count to 10 for capture
ALSA: cannot configure capture channel
cannot load driver module alsa
12:22:05.930 JACK was stopped successfully.
12:22:08.023 Could not connect to JACK server as client. Please check the messages window for more info.
Mais en root tout va bien ! Il sembllerait que cela vienne plutôt d'alsa, non ?