noob question: can nome II as master respond to transport?

[RayBloodyPurchase]

Hey,

Is it possible for the Nome II to respond to transport when it's master clock, or does 'play' always have to come from the Nome? I'm used to having a couple different transports, eg: oxi = master and transport, digitakt can also transport; or daw is master+transport and digi or oxi is a secondary transport.


cheers.

[simntonic]

Hi RayBloodyPurchase,

Nome can respond to external transport (start/stop) over USB MIDI, but it depends a bit on how your setup is configured.

If you’re not using U-SYNC, you can send MIDI start/stop directly to Nome via USB and it will follow.

If you are using U-SYNC, the better approach is to map your other device’s play/stop to the DAW transport. Nome will then follow the DAW, keeping everything in sync.

[RayBloodyPurchase]

Thanks for the reply.

I'm not using U-Sync. Nome is master clock, sending clock out din1 via the mioxl, and digi sending transport via mioxl to the Nome. Nome transport works fine.

I can trigger play from the digitakt, but pressing 'pause' on the digi is ignored by Nome, and pressing 'stop' on digi locks up the digitakt and the Nome. Midi monitor shows the 'stop' message getting stuck indefinitely - it seems like there is a feedback loop where pressing stop on the digi triggers stop on the nome which triggers stop on the digi etc, and the only way to unlock them is to power cycle one or the other device.

I tried filtering different messages on the digitakt, filtering stop obviously solves the problem but then I only have 'play' form the digitakt.

I will try with a different secondary device today, but I'm wondering if anyone has any experience with the digitakt 2. Is there a way to get the Nome to respond to digitakt 'pause' and 'stop' successfully?

[simntonic]

Yeah, that definitely sounds like a feedback loop.

What’s happening is basically:
Digitakt sends Stop, Nome forwards it, Digitakt receives it again, and it keeps bouncing back and forth. That’s why everything locks up on stop.

The fix is just to break that loop somewhere. For example: don’t send transport from Nome back to the Digitakt (only clock), or filter transport in one direction so only one device is in control

About the pause message, that one isn’t handled consistently across devices, so it’s normal it doesn’t behave the same as play/stop.