Posts: 1,279
Threads: 7
Joined: Jan 2020
Reputation:
65
6
The issue has not been pinned down precisely, however a solution was found using another routing and like the good book says: "If you can make it work another way, no more debugging for today!".
Jesse
Posts: 94
Threads: 18
Joined: Oct 2021
Reputation:
5
1
There are a few foundational principles to midi in general
Don’t configure midi ins, if your unit is only a departure. Don’t configure midi outs if your unit is only a destination
Out and thru are not the same thing
You can only have one clock and clocks wandering around through midi out/thru loops will choke the system.
I always design my setups like a cascaded downstream, never circular. If you need circular setups, only do it with destinations that supports local off.
Posts: 94
Threads: 18
Joined: Oct 2021
Reputation:
5
1
USB is bi-directional, DIN is not. Not a roque connection causing a loop there? (All leds off?)
As it sounds like a flooding problem.
When on USB is the keystep then still connected via DIN as well? maybe feeding other units directly?
Is midi clock set to ext/slave on all devices?
I didn’t meant my previous post to be pedantic, but these setups are complex and it’s easy to overlook something.
I work 37 midi devices between a MioXL, MRCC, Syncgen II, NDLR, Toriaz Squid, Korg SQ-64 and Cubase (Oxi One on the way)