Hi all,
I'm afraid there's something wrong with Pd and new jackd releases (0.116.x). Pd gives some ; watchdog: signaling pd... and audio dropouts. The watchdog errors appears only on a gui-less pd, I can't say if it's the same for dropouts as the gui is likely to produce some audio clicks.
Everything performs well with old jackd ver 109.2.
I tried different revision of pd-extended from 0.39.2 to 0.41.4, watchdog and dropouts are here..
All the best Joël
Hi!
joel silvestre schrieb:
I'm afraid there's something wrong with Pd and new jackd releases (0.116.x). Pd gives some ; watchdog: signaling pd... and audio dropouts. The watchdog errors appears only on a gui-less pd, I can't say if it's the same for dropouts as the gui is likely to produce some audio clicks.
This might be the same issues which bothered me some time ago. Try running jack using '-R' and '-P' parameters together like:
jackd -R -P 15 -d alsa ....
You can also set -P in qjackctl
For me everything above 11 worked without these errors on alsa, for firewire audio I had to set it slightly higher.
Also have a look at what roman said in this thread, which was quite helpful: http://lists.puredata.info/pipermail/pd-list/2009-04/069267.html
cheers, Martin
Le jeudi 09 avril 2009 à 21:52 +0200, Martin Schied a écrit :
Hi!
This might be the same issues which bothered me some time ago. Try running jack using '-R' and '-P' parameters together like:
jackd -R -P 15 -d alsa ....
You can also set -P in qjackctl
For me everything above 11 worked without these errors on alsa, for firewire audio I had to set it slightly higher.
Also have a look at what roman said in this thread, which was quite helpful: http://lists.puredata.info/pipermail/pd-list/2009-04/069267.html
cheers, Martin
Hi Martin,
I try various rt priority settings without any success, dropouts are still here.
I think part of your problem comes form : zombified - calling shutdown handler To avoid this you can can try to increase the jackd timeout watchdog with option -t 5000 or disabling client zombification with option -Z.
Which version of jackd do you use?
All the best
Hi Martin,
I try various rt priority settings without any success, dropouts are still here.
I think part of your problem comes form : zombified - calling shutdown handler To avoid this you can can try to increase the jackd timeout watchdog with option -t 5000 or disabling client zombification with option -Z.
Which version of jackd do you use?
currently I'm using jackd version 0.116.1, before that I was using 0.109.2-3ubuntu1 (current intrepid version?), which already had this "issue".
I also noticed that different timeout settings made noticeable changes to this issue but it didn't solve the problem entirely, (btw. I already was using 9000ms, and this watchdog is not jack-related but built into pd / gui as far as i know.)
when trying different things concerning realtime permissions I also noticed that priorities for "audio" group in /etc/security/limits to something below 10 (don't know exactly anymore) also had an influence (because pd had no more rt permissions then).
now everything's fine when jack is started with sufficient priority, no matter which other settings I use with jack (except dropouts with too low latency or doing graphics stuff with gem in the same instance of pd).
Martin
currently I'm using jackd version 0.116.1, before that I was using 0.109.2-3ubuntu1 (current intrepid version?), which already had this "issue".
I also noticed that different timeout settings made noticeable changes to this issue but it didn't solve the problem entirely, (btw. I already was using 9000ms, and this watchdog is not jack-related but built into pd / gui as far as i know.)
when trying different things concerning realtime permissions I also noticed that priorities for "audio" group in /etc/security/limits to something below 10 (don't know exactly anymore) also had an influence (because pd had no more rt permissions then).
now everything's fine when jack is started with sufficient priority, no matter which other settings I use with jack (except dropouts with too low latency or doing graphics stuff with gem in the same instance of pd).
Martin
Strange but I have no dropouts when running those patchs on my laptop with both alsa and firewire jack backends. So I give a try on 2 others hardware and no matter what I do dropouts are always here ...
I think your case was different since I have no crash like " zombified - calling shutdown handler " but "only" watchdog: signaling pd... and dropouts. And troubles arises only when the -rt patch is started with -nogui.
Very simple patch like just [osc~] and [dac~] doesnt' trigger the watchdog.
Joël
Strange but I have no dropouts when running those patchs on my laptop with both alsa and firewire jack backends. So I give a try on 2 others hardware and no matter what I do dropouts are always here ...
I think your case was different since I have no crash like " zombified - calling shutdown handler " but "only" watchdog: signaling pd... and dropouts. And troubles arises only when the -rt patch is started with -nogui.
Very simple patch like just [osc~] and [dac~] doesnt' trigger the watchdog.
Joël
I digg a litlle further and found out it's probably a scheduling issue. When the gui send the "I am happy" signal to the watchdog process all is fine but when there is no gui this task is devoted to the main process and sometimes fails to do it in time. As a very ugly workaround I comment out the kill(getppid(), SIGHUP); line in s_watchdog.c Watchdog is still signaling as before but dropouts are gone! To be sure the pd patch outputs a 1Khz sinewave monitored with jaaa in peak hold mode.
That's all my little knowlegde can do...
All the best Joël
-
joel silvestre -
Martin Schied