Le 30/01/2013 20:50, Ralf Mardorf a écrit :
On Wed, 30 Jan 2013 20:40:41 +0100, dAgeCKo <dage...@free.fr> wrote:
I wasn't and won't be able to make tests today, due to family issue.
Le 30/01/2013 11:44, Ralf Mardorf a écrit :
On Wed, 2013-01-30 at 11:40 +0100, Raffaele Morelli wrote:
AFAIK it could be his guitar cable, he's not posting anything useful
about running processes, etc etc...
Regarding to the issue of the thread (not the Jack2) issue, a broken
cable indeed is very likely, OTOH his settings 4 ms input + output
latency is very good, not many setups can go that low for the latency,
especially not when the CPU freq scaling gov is at ondemand.
You mean the physical cable ? I don't think so. Each time the problem
occurs, the problem resists until a reboot. Then after the reboot, there
is no more problem at all. I never faced a problem just after my system
booted.
Anyway, I'll make deeper tests about all of this and let you know.
What sound card, resp. sound device do you use?
Try a latency of >= 10.7 ms. Be aware that a lot of musical instruments
have a higher latency. Latency isn't an invention of digital gear. Don't
forget to switch to performance for the CPU frequency scaling governor.
Can you add the output of jack and uname -a?
Linux entropia 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
About jackd, unfortunately I have everything in french:
20:49:39.307 Baie de brassage désactivée.
20:49:39.315 Réinitialisation des statistiques.
20:49:39.334 Changement des connexions ALSA.
20:49:39.347 Script de démarrage...
20:49:39.347 artsshell -q terminate
20:49:39.363 Changement du graphique des connexions ALSA.
sh: 1: artsshell: not found
20:49:39.749 Script de démarrage terminé avec statut de sortie=32512.
20:49:39.749 JACK démarre...
20:49:39.749 /usr/bin/jackd -p128 -dalsa -r96000 -p128 -n3 -D -Chw:0 -Phw:0
20:49:39.752 JACK a été démarrer avec le PID=14787.
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
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 = 96000
creating alsa driver ... hw:0|hw:0|128|3|96000|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 96000Hz, period = 128 frames (1.3 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit float little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit float little-endian
ALSA: use 3 periods for playback
20:49:41.959 Changement des connexions JACK.
20:49:41.960 Configuration du serveur enregistrée dans «
/home/jd/.jackdrc ».
20:49:41.961 Réinitialisation des statistiques.
20:49:41.991 Client activé.
20:49:41.996 Changement de la taille du tampon (128).
**** alsa_pcm: xrun of at least 1.666 msecs
20:50:06.972 Récupération désynchronisation (XRUN) (1).
**** alsa_pcm: xrun of at least 4.360 msecs
20:57:14.425 Récupération désynchronisation (XRUN) (2).
**** alsa_pcm: xrun of at least 0.619 msecs
20:57:58.430 Récupération désynchronisation (XRUN) (3).
**** alsa_pcm: xrun of at least 4.139 msecs
20:58:25.919 Récupération désynchronisation (XRUN) (4).
The xruns I am facing only occur when I am playing with my windows (just
like starting a new program, and so on). If don't use my desktop, I do
not face any xruns.
When starting it manually (so certainly without all the same options
that I have threw qjackctl), here is the output:
jd@entropia:~/scripts$ jackd -R -P 0 -d alsa
jackd 0.122.0
Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn
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 ..
creating alsa driver ... hw:0|hw: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 float little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit float little-endian
ALSA: use 2 periods for playback
cannot use real-time scheduling (FIFO at priority 0) [for thread
535095040, from thread 535095040] (22: Invalid argument)
Also as a side note I have the nvidia drivers installed, so this helps a
lot in not using the CPU when having a WM/desktop running.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51097cdb.9060...@free.fr
