OT sequencer stops unexpectedly

Elektron Gear Octatrack
#41

No

#42

Okayā€¦ well thatā€™s a good sign then. :wink:
I suppose using the OT as master is not an option for you?
It helped fixing issues for me. Anyway, good luck finding the culprit.

1 Like
#43

:thinking: That wouldnā€™t be the latest for me, Iā€™d try another midi monitor.
If it stops only when midi in connected, receiving midi data, Iā€™d double check. Iā€™d also try other clock sources (AR for instance).
Thanks for your patience and all the tests you did anyway !

Needed to record the most accurate internal loops. No overdub possible with Pickups if slaved (overdub still possible with Flex).

#44

Latest experimentā€¦ ran it at 32 and stopped fairly soon. Ran at 42 and same story. Ran at 52 and after 12 hours no stops.

#45

Here is some stuff from the midi monitor, though Iā€™m not getting stoppages at 52bpm.

14:45:05.315 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
14:45:06.123 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:41.584 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:42.292 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:42.980 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:51.313 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:52.022 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:34:52.710 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:35:24.721 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:35:25.520 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:38:40.031 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:38:40.840 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:39:06.684 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:39:07.493 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:44:43.127 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:44:43.935 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:45:21.853 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:45:22.661 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:47:09.691 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:47:10.500 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:47:50.107 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:47:50.901 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:47:50.915 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7
21:50:53.523 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 00 5D 60 F7
21:50:54.332 From MIDI In SysEx Unknown Manufacturer 10 bytes F0 00 21 27 19 14 01 3B 40 F7

#46

You are sending many sysex messages, these are big messages. Iā€™d definitely filter them, they can be the culprit.

Do they come from your clock source?
Any way to deactivate them?

#47

Looks like sysex header for Expert Sleepers ES-9ā€¦

Very weird about the tempo.
I mean, I have never tried running < 60 BPM for longer periods. Perhaps it could be a bug after all.

#48

Not that many, not that bigā€¦

OT should happily ignore these.

#49

Yeah, they have nothing to do with the stoppages. When the OT stops you will see NOTHING in the midi monitor. And despite all the sysex messages there is no stoppage when those appear.

#50

And still no instance where this happened with no MIDI connected?

Perhaps OT has a problem syncing up to a very slow clock.
I will try this myselfā€¦

#51

Correct, no stoppage at 32 standalone.

#52

A quick idea. Have you tried setting the OT pattern tempo to the same external BPM ? (Even if slaved)
With some sequencers, this can make a difference.
Just a shot in the darkā€¦

#53

Test in progressā€¦

#54

It shouldnā€™t though, really. That would be pretty bad.

Got mine running slave at 30 bpm now (120 bpm was internal tempo). Weā€™ll see how it goesā€¦

Edit: actually, Iā€™ll try 32 to replicate.

#55

Any (other) filters on the MIDI monitor?
Since I didnā€™t see any realtime/clock messages.
Transport is off right?

#56

Clock is the only filter. I had re-enabled transport IN.

#57

Iā€™ll be damned. It just stopped.

Will try 40 next.

#58

Same here. It stops at 42 as well. Had to go to 52 to get it to keep running.

#59

40 still running here.
What was the lowest tempo where you never experienced this?

Or, the highest you didā€¦ :wink:

#60

To pick up from an earlier post, what stops you from using OT as master? Is it important to have Pamā€™s as clock source?

With OT as master, you get the most accuracy, not least for the sampling and playback part.

When running as slave, the OT has to constantly interpolate and adjust for the incoming clock messages. It does this very well, but itā€™s still much better to use the internal clock.

I only slave to a DAW occasionally, even trying to avoid that.

As you are only sending clock to OT, itā€™s probably a very easy workaround.

ā€¦still runningā€¦

Edit: it stopped again after ~ 3h

Yeah, clearly a bug, I can reproduce this.
Youā€™re on 1.40A i assume?

I donā€™t see anything mentioned in Octatrack OS 1.40A: bug reports - you should post it there, and report via the Support Tickets section on elektron.se

Perhaps some of the old-timers can say if this problem has been around in earlier revisions.