On debian testing:
- start Pd with no jackd running
- jackd will be started by Pd
- Quit Pd (with ctrl-q, from menu, by closing window)
- Pd hangs with "watchdog: signaling pd..."
If you do a:
killall -9 jackd that also kills Pd
This does not happen if jackd was previously started and Pd connects to it.
jackd is version 1.9.9
Anonymous
I'm assigning this to IOhannes since he works on the Jack code. I rarely use Jack.
Is this still an issue? I included some fixes to Jack handling, please try the latest test release.
http://puredata.info/downloads/pd-extended/releases/0.43.4
Unfortunately its' still there.
When quitting this is the output:
JackEngine::XRun: client = pd_extended_0 was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = pd_extended_0 was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
~/Desktop$ JackEngine::XRun: client = pd_extended_0 was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackEngine::XRun: client = pd_extended_0 was not run: state = 1
JackAudioDriver::ProcessGraphAsyncMaster: Process error
JackTemporaryException : now quits...
watchdog: signaling pd...
watchdog: signaling pd...
...
The only way to quit is to kill jackd
Again, no issue if jackd was had already been started
ICBxxS <a href="http://kvsjcghaicty.com/">kvsjcghaicty</a>, [url=http://beelgbnhdser.com/]beelgbnhdser[/url], [link=http://refmhpzyiszk.com/]refmhpzyiszk[/link], http://lhggsnjxnpke.com/