MIDI out vs. Thru

Qwave · Post by **Qwave** » Wed Apr 28, 2004 2:41 pm

I am using a Voyager 2.1 and did this:
- Local off
- MIDI IN and MIDI OUT both set to ON

I did this to play an external synth expander from the Voyager's keyboard while the Voyager itself was meant to play incomming MIDI data from a sequencer (Manikin Schrittmacher).

But the MIDI OUT also includes the MIDI signal presented at the MIDI IN. Much like the MIDI THRU.

Why is MIDI IN signal also present at the output? This is not the behavier of my other synth at home. Is this a bug or by design?

MC · Post by MC » Wed Apr 28, 2004 9:29 pm

OS v2.x includes a MIDI Merger which merges data at the MIDI IN jack with data generated within the Voyager. You can disable the Merger in the MASTER menu.

MIDI THRU is a direct copy of data in the MIDI IN jack - it does not contain ANY data generated by the synth. There are hardware and software THRU implementations in MIDI products; a hardware THRU is always on its own dedicated jack, while a jack labeled OUT/THRU is no doubt a software THRU. The advantage of a hardware THRU is there is no cpu latency between IN and THRU, the delay is extremely short.