I know that this has been brought up a few times with limited results, but I thought I would bring it up again with some different context.
So I built a box a couple of weeks ago (rp4 4gb, PiSound module) to act as both an effects box as well as a way to sync my DJ setup (Serato DJ 2.5, turntables and mixer) to my hardware synth setup by acting as a bridge between Ableton link tempo to MIDI clock out. So, when I sync the box to an external iOS app with Ableton link sync using MIDI my Modep box will both sync to the clock provided as well as act as a MIDI thru for tempo, but when I create a patch that has the MIDI clock Lv2 plugin (or any plugin capable of sending MIDI out), when I choose to sync the MODEP to Ableton Link itself, the MIDI clock output of the Modep host is disabled, even for plugins. This means that the Modep cannot act as a bridge for tempo, making the device really fun, but limiting itself from a frankly insanely exciting application.
I’ve done some poking around at the Jack Link libraries and it might be an issue with the Jack Link library, meaning that the solution would ultimately be somehow creating a separate MIDI output divorced from the Jack transport (which I’m not sure is possible). Other than that, I’m not you guys, so I’m not sure that I have an elegant solution. I can tell you however that if this can be solved, the implications in the broader DJ community would be HUGE, especially for those of us who are trying to do larger DJ hardware/software/audio/visual setups. (I can name twenty DJ’s who would build a box tomorrow if this worked).
Pretty easy. Activated Ableton link on both Serato and Modep. Link works perfectly (Serato tempo follows Modep). I can sync any software I want, but the moment I activate Ableton link the midi output is deactivated. (This includes both clock and transport output).
Yeah, definitely have experience this myself. I’m surprised this hasn’t been fixed yet as in theory it affects products like the Mod Devices (and of course MODEP) which tout connectivity as one of its selling points.
mod-ui uses mod-host. It may be fixed in a newer version of mod-host, or it could still be there, or the plugin author might be wrong. Too bad he didn’t elaborate on what issue he assumed the host has.
I wish I had a mod device, then I could test it on original hardware which might give more weight to my argument that something somewhere is not working! Feels strange and unlikely that I’m the only one experiencing this issue or that more mod owners haven’t spoken up about it.
Maybe first try pinging the plugin author for his insights?