Comrades!
I posted something similar in another thread but I think this might have been out of scope so I’m starting another thread in the hopes of finding an answer…
I have my OT as the master clock and transport send in my setup, with a KSP (clock and transport send off) sharing a Merge box, which then goes into the MIDI In of a pyramid. The MIDI out of the pyramid then goes into a Thru box, where these Outs then send to 6 different devices, one of which is my DT2.
Previous to adding the Merge box I left the KSP out and I had full control of sync and transport from the OT, DT2 reacted as it should, and all was well minus the ability to “play” the hardware connected to the Pyramid.
Since adding the KSP into the Merge, the DT2 has decided that play=stop, and stop=play - my transport is flipped on that device alone. I even reverted the setup, removing the KSP and the Merge box but the DT2 persists in having this inversion.
Has anyone had a similar issue? Would anything to do with the Merge box be able to alter the transport function in the DT2 alone? I am planning on updating or re-flashing the FW on all my hardware tonight to try to minimize errant bugs, but this feels so connected to including the KSP/Merge but that doesn’t seem right.
Help!
I believe I remember your other thread. So it’s still reversed even standalone, eh? Just to confirm, have you created a brand new project and started from there to verify the transport control issue isn’t somehow attached to the current project?
I’d think a firmware reload (preferably over sysex) would be the next step. There should be nothing native to the DT2 which would allow this to happen, it’s in some way glitched out. Was the DT2 possibly recieving it’s own midi out signal coming back into it? Midi loopback can cause strange things to happen.
2 Likes
Thanks for the input!
A new project seems to have cleared it up! I didn’t even think of that, I was just having fun continuing with the patch I had going.
FWIW there’s no midi out from the DT2, and no special internal routing other than any defaults, which I have to assume do not create midi loops.
I’m still moving forward with all my FW updates, good practice anyway, but I think it’s all making more sense now.
Thank so much!
1 Like
No worries, glad that worked for you. If possible, you should still report this in the bug reports thread. Especially if you know how to duplicate the issue, because that way the developers can reference your experience for future firmware updates.
1 Like
good call - I’ll need to see if I can indeed duplicate the issue, I was more than happy to just move on 