[NO BUG] Connected Octatrack stopping by itself

[XORadmin]

Given Thomas’ latest reply just above, I’m inclined toward dragging the thread back to this question from a few days ago:

Can you give us a rundown of the involved physical MIDI connections? Active/passive splitting, thru jacks or boxes, MIDI processors, etc?

Nerseq OUT -> Erica midi box IN

Erica OUT -> Intellijel 1U midi IN (currently not used for CV or clock)
Erica OUT -> Disting EX IN (currently not used in any patterns)
Erica OUT -> Octatrack IN (master mix fed through ES-9 to PC via USB, then routed to Motu for monitoring via VCV Rack mixer) 
Erica OUT -> Analog Rytm IN
Erica OUT -> Motu IN -> USB-C -> Mac (midi monitor software)

Everything is clocked by Pam's (x24) -> Nerdseq clock/reset IN (Mod.Clock24)
Nerdseq Reset OUT -> Pam's run input
Nerseq Midi clock OUT (DIN-Sync24)

Keep in mind the stoppages exist with nothing but Nerdseq OUT to Octatrack IN.

Yep! But like this it is not possible to monitor the midi data. It looks like the Erica device is sending things on it's own, or your midi device on your mac has kind of a loopback enabled.

[mntbighker]

Yep! But like this it is not possible to monitor the midi data. It looks like the Erica device is sending things on it's own, or your midi device on your mac has kind of a loopback enabled.

Got another guy on Elektronauts who replicated my results on his Octatrack. It seems it has issues with anything much under 50bpm sustained. The minimum you can set internally is 30.

The Sysex messages are supposedly from my Disting EX.

[XORadmin]

Yep! But like this it is not possible to monitor the midi data. It looks like the Erica device is sending things on it's own, or your midi device on your mac has kind of a loopback enabled.

Got another guy on Elektronauts who replicated my results on his Octatrack. It seems it has issues with anything much under 50bpm sustained. The minimum you can set internally is 30.

The Sysex messages are supposedly from my Disting EX.

Yep, you were monitoring the wrong source then.

However, it turns out to be a Octatrack problem as it seems and I will close the bugreport here then.

[mvdirty]

Got another guy on Elektronauts who replicated my results on his Octatrack. It seems it has issues with anything much under 50bpm sustained. The minimum you can set internally is 30.

Interesting! A shame that their clock following implementation is bugged like that, but at least now we know!

[mntbighker]

Thanks gents for all the help. It ran all night at 52, and that seems to be about as low as it will reliably go with external midi clock.