seq24 0.9.2 doesn't respond to JACK Transport (JACK 0.12x.x)

Bug #803385 reported by autostatic
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Seq24
New
Undecided
Unassigned

Bug Description

LS,

I'd like to update JACK on my machine from 0.118.0 to the current 0.121.2 version but then seq24 doesn't respond to JACK Transport anymore, actually, it doesn't want to start at all if Jack Transport is enabled in seq24. This issue has been addressed before: http://lists.linuxaudio.org/pipermail/linux-audio-user/2010-November/073848.html
Apparently patches have been provided, unfortunately I can't find them anymore. If I do find them back I will post them so that they hopefully might get included in a possible future release.

Thanks!

Jeremy

Revision history for this message
Nareto (rennabh) wrote :

I can confirm this with jack 0.120.2, haven't tried yet if the issue disappears with jack 0.118

Revision history for this message
Nareto (rennabh) wrote :

yes, downgrading to 0.118 (and recompiling seq24) solves the issue for me too

Revision history for this message
autostatic (autostatic) wrote :

The developer who created the patches can't find them back anymore. But they have been sent to the seq24 dev team so hopefully they can be dug up again. I'd like to test jack-session but this is holding me back.

Best,

Jeremy

Revision history for this message
Nareto (rennabh) wrote :

Just went through 2010-2011 archives of seq24-devel mailing list and only relevant thing I could find was this

http://sourceforge.net/mailarchive/forum.php?thread_name=20101111203416.GA18268%40traun.gscholz.bayernline.de&forum_name=seq24-devel

patch by torben to add jack-session support. It would seem unrelevant to this bug, but if you read his second mail he seems to say that jack transport wasn't working for him on the then jack-svn which had the jack session API, which is now currently in jack1 > 0.118

so it could be related to that?

yes this bug is pretty severe IMHO as it makes seq24 unusable with other apps.

Revision history for this message
Nareto (rennabh) wrote :

sorry, I confused. It's actually in this mail

http://lists.linuxaudio.org/pipermail/linux-audio-user/2010-November/073848.html

on LAU in November that he was saying he couldn't get jack transport in seq24 working with jack1-svn

Revision history for this message
Nareto (rennabh) wrote :

I can confirm this bug on latest bazaar version, 125

Revision history for this message
Lieven Moors (lievenmoors-3) wrote :

Hi,

I stumbled into this bug as well when switching to Arch Linux.
Seq24 doesn't run at all with newer jack.
By following the linuxaudio mailing list link above, I saw that there
is a quick and dirty fix possible, until somebody fixes up jack transport
properly. All you have to do is register an empty process callback with JACK.

That's what I've done in the patch below, and it worked fine for me.
Is there somebody of the seq24 team that could apply this patch,
so that a lot of people can actually use seq24 again?
A quick release with this patch would be advisable too, I think.

Greetings,

lievenmoors

Revision history for this message
Nareto (rennabh) wrote :

Hi, you're sure it's the same bug? For me (also on Arch) with jack transport disabled the playback works fine...

Any news on this?

Revision history for this message
autostatic (autostatic) wrote :

Yes this is the same bug. JACK transport works again for me with this patch (which has been applied upstream: http://bazaar.launchpad.net/~seq24team/seq24/trunk/revision/128).

Jeremy

Revision history for this message
Nareto (rennabh) wrote :

hadn't tested enough: it works for me also but only if set as Jack Master

Revision history for this message
mykhyggz (linux-f) wrote :

I just found this patch and applied. My findings are the same: it only works when seq24 is set as jack master.

Revision history for this message
autostatic (autostatic) wrote :

Not necessarily, you can use another application (like Qtractor) as JACK master and seq24 will follow.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.