What is MIDI Merge? Does a 2-in-1 MIDI Box Still Show Two Input Sources After Merging?

Many people who use MIDI hardware or build custom MIDI controllers have tried 2-in-1 MIDI merge boxes. A common question arises: after merging two MIDI inputs, the MIDI monitor still shows two distinct input signals. Does this count as genuine MIDI Merge?

Is a visible dual-input signal still real MIDI Merge?

The short answer is yes. This is standard MIDI Merge. There is a widespread misunderstanding that merging means mixing two streams into one completely indistinguishable signal, but that is not how MIDI Merge operates.

MIDI is a serial event stream. A single MIDI cable can only transmit one set of bytes at a time. A 2-in-1 MIDI merge box works in this way:

1. Two input ports receive MIDI events independently, including Note On, Note Off, CC controls, pitch bend and more.
2. The internal chip handles timing arbitration. It forwards events from Input A or Input B as they arrive. If two events trigger simultaneously, the box will stagger bytes slightly to avoid collision.
3. All MIDI events from both inputs are forwarded to one single MIDI output bus.

Simply put, MIDI Merge combines multiple physical MIDI data streams onto one physical output line. It does NOT modify the MIDI channel information inside each event.

MIDI Stream Merge vs MIDI Channel Remapping

It is critical to distinguish MIDI Stream Merge from MIDI Channel Remapping.

MIDI Merge (Stream Merge)

Multiple physical MIDI inputs → One physical MIDI output. MIDI channel numbers remain unchanged.

• For traditional 5-pin DIN MIDI: there is no source tag. If both inputs use the same MIDI channel, the receiver cannot tell which input the note came from, only that notes are stacked.
• For USB MIDI with UMP (Universal MIDI Packet): packets carry port source IDs. That is why your software monitor can still tell which input each MIDI event comes from after merging. This feature is normal and does not mean the merge failed.

MIDI Channel Remapping

Rewrite events from different channels into a single MIDI channel. Once remapped, the receiver cannot tell the original source. This is NOT MIDI Merge. You need to add channel remapping after MIDI Merge if you want all messages on one channel.

MIDI Merge vs MIDI Thru

• MIDI Thru: copies incoming events and forwards them. It is 1-in multi-out and cannot combine multiple MIDI sources.
• MIDI Merge: collects multiple input events and outputs them to one port. It is multi-in 1-out.

Known limitations of MIDI Merge boxes

1. Timing jitter: Heavy simultaneous MIDI traffic needs queueing, introducing minor latency.
2. Stuck Notes (Note Stuck): Poor arbitration logic may drop Note Off events, causing sustained notes.
3. Channel conflict: If two inputs share the same MIDI channel, notes and CC messages will overlap and cause unexpected controller behaviour.