DIN SYNC run signal high after double stop

Hello all,

What could be the reason on a digitakt (and other Elektrons?) that with DIN24 / DIN48 SYNC, if you press a double stop, the Run signal goes and stays high? Nothing runs…

Is it a special situation for song position 0 like discussed here? AR/4/K Din-Sync Voltage Info (as a picture showing the high signal).

Could this be a bug or another case of a special double stop implementation?

Regards, Airell.

1 Like

Double stop is a way to reset everything back to zero - iirc there are also more midi messages transmitted when double stop is pressed, it’s certainly a more emphatic stop and different from a single stop. Maybe other users of Din Sync gear can chime in if this is standard implementation and what the purpose would be of going high(run) whilst the pulse train is off - interesting question

Yes I know, I think there is a program change 127 transmitted as well. This makes other gear go crazy. I my opinion a sysex should have been used for stuff outside the midi standard for special Elektron uses (or use the System Real-Time Message 11111100 = Stop the current sequence). I had this explained by Elektron. No change here.

That’s actually what I am wondering. Is it standard? Because it’s the run signal, but no clock, so nothing running.

1 Like

No it isn’t standard din sync behaviour, when stopped run/stop should be low. However it does come in handy for powering devices from the 5v, like the sync clock divider that one of the forum members sells (whose name escapes me now).

I don’t know whether the following applies to any Elektron gear other than the Analog Four, but the release notes for Analog Four OS 1.12 describe the following feature:

DIN Sync
When [STOP]+[STOP] is pressed the DIN Sync outputs are put in a ready to start mode, so that when the sequencer starts the synced units will be able to start directly with it. When placed in this mode a TB-303 can not be programmed. Therefore you can now exit this mode by pressing [STOP] and re-enter it by pressing [STOP]+[STOP].

2 Likes

I just discovered this bizarre behavior while building a piece of hardware that can follow DIN sync. I thought I’d test it with my Digitakt… and what the?

There seem to be four transport states in Digitakt:

  1. running
  2. paused (▷ from here will continue from where the transport is)
  3. stopped (▷ from here will restart from the beginning of the pattern)
  4. stop-stopped (like stopped)

But there are only three DIN sync states:

  1. running: clock line is going, run-stop line is high
  2. not-running: clock line is going, run-stop line is low
  3. weird: clock line is low, run-stop line is high

Sadly, when either paused or stopped, the DIN sync is in not-running mode - and you can’t tell the difference… so when the run-stop line goes high again, the other equipment doesn’t know if it should continue from where it left off, or restart from the top of the pattern. Sigh!

I’ve seen other spec docs for DIN sync that say to implement paused, the run-stop should remain high, and simply stop the clock. This makes sense… only that state is the wierd one on Digitakt, and clearly means full-stop, restart from top of pattern when ▷ is pressed.

The weird state is… well, weird? What ever is it for?