From Michael E Caloroso Sent Thu, Dec 27th 2018, 02:52
From Michael E Caloroso Sent Thu, Dec 27th 2018, 02:52
> 3) Although 99% of MIDI devices have MIDI Thru wired properly with 0 late= ncy from MIDI > In, I seem to recall hearing about a few MIDI devices that have CPU proce= ssing on the > MIDI stream for MIDI Thru, and that would introduce latency. That would b= e in violation of > the MIDI standards, so I hope you don=E2=80=99t have any devices like tha= t. The telltale is a device with a port labeled "MIDI OUT/THRU" or only IN/OUT ports but no THRU. Buried in the menu system may be a configuration to change the OUT port to a THRU. Under this condition the "THRU" signal isn't the circuit spelled out by the MMA and is actually coming from the CPU on the device, which WILL have some delay to it. I'm not a fan of chaining THRU ports as one too many can distort MIDI signals to the point where they are not recognized at the receiving device or can appear as another erroneous MIDI message. I'm not talking clock messages, I'm talking performance messages like note on/off and CC messages. MC