On Fri, 14 Dec 2007, Kjetil S. Matheussen wrote:
On Fri, 14 Dec 2007, Stéphane Letz wrote:
>
> Paul Davis:
> >
> > > Unless jack is
> > > fixed (or extended) so that it can recover from errors (including
> > > letting its latency be adjusted on the fly)
>
> <...>
> >
> > JACK has a number of problems, some of them significant. The things
> > you've spoken about are not among them.
> >
>
> I'm not sure what other problems you are thinking of? I completely
> agree this is the main problem with jack. Its not unusual that a
> program connecting to jack can make jackd crash. And it is
> even possible to prevent this! (I know it tries to prevent
> it though, but it does fail very often too).
Is it something occurring in jackd only? or also jackdmp?
I'm not sure. I haven't used jackdmp that much. But here is a
way to check.
1. Start jackdmp -R
2. Start xmms
3. Play something in xmms
4. Start jackrack
5. Load this ladspa plugin:
http://www.notam02.no/arkiv/src/ladspasleep.tar
[1]
6. Drag the "usecs to sleep" slider quite high.
7. Enable the plugin.
8. Drag the "usecs to sleep" slider back and forth a lot.
This is a quite sure way to make jackd crash.
Just tried with jackdmp, and jackdmp handles this situation
perfectly. No crashes, and neither jackdmp or jackrack is shut
down, and jackrack even starts producing sound again when it
doesn't use too much cpu time anymore. I'm switching
back to jackdmp now.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
