« Return to Thread: new patch to help jackd along

Re: new patch to help jackd along

by Fernando Lopez-Lezcano :: Rate this Message:

On Fri, 2008-05-09 at 12:20 +0200, Fernando Lopez-Lezcano wrote:

> On Thu, 2008-05-08 at 22:24 -0400, Paul Davis wrote:
> > Changes:
> >
> > * use poll+read, not just read, when waiting for clients to finish up
> > non-process "event" handling
> > * mark clients as Finished after their process callback has
> > executed
> > * remove clients that failed to respond to events
> > * add new -r option to completely remove the JACK shm registry
> > at startup (orthogonal to everything else, but in my codebase for
> > months)
> >
> > I would commit this directly, but I'm trying to be cautious for once. It
> > works much better for me now. Note that I believe there may be some
> > locking issues still to address in the code (insufficient locking, that
> > is, not deadlocks).
>
> thanks+++++++
> I'll try it out asap...

ardour is started:

----
15:55:57.269 ALSA connection graph change.
15:55:57.371 ALSA connection change.
**** alsa_pcm: xrun of at least 0.029 msecs

[[ always seems to happen, normal? ]]

15:55:57.504 XRUN callback (1).
15:55:57.723 JACK connection graph change.
15:56:06.041 JACK connection graph change.
15:56:06.287 JACK connection graph change.
15:56:06.388 JACK connection graph change.
unknown source port in attempted connection [system:capture_3]
unknown destination port in attempted connection [system:playback_3]
unknown source port in attempted connection [system:capture_4]
unknown destination port in attempted connection [system:playback_4]
unknown source port in attempted connection [system:capture_5]
unknown destination port in attempted connection [system:playback_5]
unknown source port in attempted connection [system:capture_6]
unknown destination port in attempted connection [system:playback_6]
unknown source port in attempted connection [system:capture_7]
unknown destination port in attempted connection [system:playback_7]
unknown source port in attempted connection [system:capture_8]
unknown destination port in attempted connection [system:playback_8]
15:56:06.582 JACK connection change.
----

start jackmix, quit jackmix, start jack-rack, load freeverb:

----
15:56:06.582 JACK connection change.
15:57:26.502 JACK connection graph change.
15:57:26.563 ALSA connection graph change.
15:57:27.551 JACK connection graph change.
15:57:27.685 JACK connection change.
15:57:30.171 JACK connection graph change.
15:57:30.291 JACK connection change.
15:57:35.850 JACK connection graph change.
15:57:35.869 ALSA connection graph change.
15:57:35.899 JACK connection change.
15:57:35.900 ALSA connection change.
----

quit jack-rack:

----
16:00:47.320 JACK connection graph change.
16:00:47.441 JACK connection change.
16:00:47.623 ALSA connection graph change.
16:00:47.644 ALSA connection change.
----

Good, it did not take down ardour with it!!

Now the interesting part: downgrade to the previous version of jackd I
had installed. Start ardour, start jack-rack, load freeverb, quit
jack-rack and _ardour is kicked out of the graph_!! So, your patch is
indeed fixing this particular problem (which was a bad one)...

Thanks...
-- Fernando

_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

« Return to Thread: new patch to help jackd along