CC#64 (sustain) echo issue using MIDI loopback

I used midi loopback with OT only most of the time, eventually with it’s Thru.
Safe as long as you control audio tracks with midi tracks.

Maybe I used it with a merger only once.

OT quick double stop sends an all notes off message.

1 Like

Ok thanks, good to know!

And also when you double stop OT will send all CC’s for unmuted midi tracks, muted midi tracks will after double stop send there CC’s once you unmute them, regardless if they are the same values as the last ones sent…

Just throwing that out there, some folks know, some folks don’t… :slight_smile:

I didn’t know that either… might explain some WTF moments I have had … thnx!

2 Likes

I forgot double stop sends set midi track program changes as well, haven’t tested if the same unmuted/muted track behavior is the same as CC’s or if it just sends them straight away…
Also double stop is when sequencer is stopped, triple stop if running…

1 Like

Double / Tripple stop sends also the activated CCs set in CTLR1/2 IIRC.
Not sure about mutes…

Even when the sequencer is not running? That would certainly suit me

Yes. No choice anyway with double / triple stop.

While running you can send all ccs after receiving the CC61 SEND REQUEST.

1 Like

Are you saying that, while running, I send CC61 with my pedalboard to the OT, all channels I send it on will send out their complete CC sets? Now that’s something!

I don’t know how to remember all this… What a huge amount of information to swallow . I must say that I updated a lot of my gear recently, and the OT is not the only new kid on the block here… my head is exploding with info’s and I dream about user manuals of all sorts and recite midi implementation charts while showering…

1 Like

That’s what I meant in my first post before the one I mentioned PC change…
After double/triple stop OT sends set and activated cc’s immediately for unmuted midi tracks, and it will send set and activated CC’s for the muted midi tracks as soon as you unmute them.

2 Likes

Yep. Never tried.

Ok sorry, misunderstood! Tired and French!
I thought you were saying it was sending mute states.

1 Like

Same here. I think I’m off to bed… thanks guys, much appreciated

2 Likes

I’m super tired lately, kinda running on a built up sleep deficit, my posts aren’t as clear as usual, and I’m perhaps a bit moody… :grin:

I have an analog delay that has potentiometers but can be controlled by midi. I’m going to use OT to make presets for it and load them by double stop.
Nap time… :sleeping_bed:

2 Likes

Yep, that was what crossed my mind too when I read this. Many possibilities here.

2 Likes

:sleeping_bed:

2 Likes

Thank you for documenting your findings @pinup57! I was experimenting with the midi loopback technique yesterday in a setup which also involved sending CC’s to a downstream device. I quickly started having glitches while trying to set parameters in the midi sequencer, but setting a dummy audio track to the same midi channel where the CC’s were going to (and actually having the CC receiving disabled in the audio track settings) solved the issue! Nice!

Since this issue is already a couple of years old, would anyone know whether there are other workarounds/solutions to a setup like this, or do the newer firmwares have some alternative settings for this? I’m still below 1.40 in my OT MK1, but planning to upgrade eventually.

I don’t think anything was made to correct those things in new firmares, and I never read about other workarounds.
All I can say is midi loopback is safe as long as channels are shared between audio and midi tracks. Midi processors can be used to re-route midi channels.

@pinup57 has suspended is account.

Maybe @roadmoviemusic want to express new discoveries?

:innocent:

1 Like