[LAD] someone can smash this seq24 bug?

torbenh torbenh at gmx.de
Thu Sep 8 17:56:02 UTC 2011

On Mon, Aug 08, 2011 at 05:30:08PM +0200, Florian Paul Schmidt wrote:
> On 08/07/2011 11:24 PM, Renato wrote:
> >Hello, seq24 is affected by this bug:
> >
> >https://bugs.edge.launchpad.net/seq24/+bug/803385
> >
> >basically with recent versions of jack, when jack transport is enabled,
> >seq24 doesn't start playing. This makes it practically unusable, which
> >is a real pity :(
> >
> >any brave dev want to give him some love? eternal glory will ensue :)
> >
> What do you offer besides eternal glory? ;D Will take a look when i
> find time..

the problem is that seq24 is registering a jack_sync callback.
this is not correct. and i pretty much said that this was going to

a quick fix would be to register an empty process_callback()
this would retain the old behaviour.

however, this is still wrong.
seq24 is not a slowsync client.
you should probably do what is done in the sync callback from inside the
process cb. the process_cb is called always, and not only when the
transport starts, so one needs to go through a few hoops to obtain the
same behaviour.

i remember, that i tried to fix this, but i dont find the patch, and
reading through archives, i might have hit a few problems, when i tried
to fix it.

> Flo
> _______________________________________________
> Linux-audio-dev mailing list
> Linux-audio-dev at lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-dev

torben Hohn

More information about the Linux-audio-dev mailing list