MIDI Controller

iConnectivity mio 10 MIDI Interface

The iConnectivity mio 10 is a full-width 19-inch 1U MIDI interface providing ten 5-pin DIN input/output pairs with programmable routing and filtering. The USB multi-host capability lets it bridge MIDI between two computers, and the standalone routing operates without a computer connected.

Compare

Documented outputs: 1010 destination connections
Documented inputs: 11Based on documented inputs
Rack space: 1UBuilder checks available rail space
Power draw: 3W5W documented maximum
Catalog estimate: ~$299Use retailer rows for current price and stock

01 · What it does—and what that changes in your rig.

Product overview

Start with the payoff, then work through how it functions, where it fits, and the details that change a real build.

The payoff

MIDI Controller decisions, organized around the whole rig.

The mio 10 is a compact MIDI router and interface that earns its half-rack footprint by doing work that most rigs quietly need but rarely plan for carefully. Its ten ports break down as two TRS 1/8-inch MIDI ins, two TRS 1/8-inch MIDI outs, two USB Host ports, one USB Device port, and an Ethernet RJ45 port for network MIDI — giving you a surprising amount of reach for a box that weighs half a kilogram. Its real job is sitting at the center of a MIDI ecosystem, routing messages between playback computers, hardware controllers, in-ear mix systems, and any DIN-based gear that still lives in your rig.

Documented outputs: 1010 destination connections
Documented inputs: 11Based on documented inputs
Rack space: 1UBuilder checks available rail space

iConnectivity product panel1U · 3W

Function

How it works in the path

At load-in, the standalone routing matters more than almost any other spec on the sheet. Once you've programmed the mio 10's internal routing table, it powers up and works without a laptop attached — your scene-change triggers and patch changes fire the moment the rack comes on, not after a driver handshake. The dual USB Host ports let you connect two USB MIDI devices directly without a computer in the chain at all, and the Ethernet port opens up rtpMIDI or session-based MIDI over your show network if you're running that infrastructure. Power draw is negligible at 3–5 watts, so it won't stress a conditioner that's already feeding a full playback rig.

Best fit

Where it earns its place in the rack

This box belongs in any rig where a playback system or show controller needs to talk to more than one or two MIDI destinations reliably every night. It pairs logically alongside something like a PlayAUDIO12 in a shared 1U space, turning a single rack unit into a complete playback and MIDI nerve center. If your MIDI needs are genuinely simple — one keyboard talking to one sound module — this is more interface than you need and a basic single-port USB device will do. But if you're managing click, cues, IEM mix recalls, and lighting triggers from the same rig, the programmable routing and filtering here will save you from cable rats and show-stopping merge conflicts.

In the rack

Details worth deciding before load-in.

Mount it in the same 1U as a half-rack playback device using a half-rack blank on the other side, or pair it directly with a PlayAUDIO12 — they share a rack unit cleanly and their workflows are complementary.
Use the internal routing filter to block program-change messages on ports that feed your IEM system if your playback software sends them — one stray PC message during a set change can silently mute a mix.
Label both TRS MIDI cables at the connector with the device name, not just 'MIDI In' — TRS 1/8-inch cables are visually identical to headphone cables and will get swapped by someone on a fast changeover.
If you're running two laptops for redundancy, put one on each USB Host port and configure the mio 10 to merge or route between them internally — switchover doesn't require replugging anything at the interface.

02 · Know the whole path before you buy.

Signal path

Learn the route as a block diagram: source, product function, transport, and destination. Select any block to see what enters, what changes, and what leaves.

Interactive block diagramAuto-looping · hover, focus, or tap to hold a stage

Port-type signalProduct functionSystem boundary

Follow one signal from source to destination

Each block answers the same three questions: what arrives, what changes here, and what leaves.

01 · Source · selected

01 · Source

11 documented inputs

midi din5 + dc barrel

Arrives as: 11 documented inputs
Connector: midi din5 + dc barrel
Signal: data

03 · What this product asks of the rest of the system.

Compatibility

Treat connector names as the start of the check—not the answer. These are the boundaries that determine a complete working path.

Best fit · MIDI Controller

Use it when 1U and 140 mm of depth fit the case.

Plan the companion path

Complete the path with upstream and downstream gear that matches connector, direction, signal type, protocol, and wiring standard.

Connector boundary

Documented connectors: midi din5, usb a, usb b, RJ45. Match connector, direction, and signal type—not shape alone.

04 · Every connector, grouped by job.

I/O ports

Switch the product view and the documented port inventory updates with it—hardware and data stay side by side.

Every connector, grouped by job.

Switch panels to keep the hardware view and the documented port list in sync.

Panel view

Front panel

Rear panel

All documented ports for iConnectivity mio 10 MIDI Interface
Port	Panel	Connector	Direction	Signal	Channels
MIDI In 1 (DIN)	rear	midi din5	input	data	—
MIDI In 2 (DIN)	rear	midi din5	input	data	—
MIDI In 3 (DIN)	rear	midi din5	input	data	—
MIDI In 4 (DIN)	rear	midi din5	input	data	—
MIDI In 5 (DIN)	rear	midi din5	input	data	—
MIDI In 6 (DIN)	rear	midi din5	input	data	—
MIDI In 7 (DIN)	rear	midi din5	input	data	—
MIDI In 8 (DIN, front)	front	midi din5	input	data	—
MIDI In 9 (DIN, front)	front	midi din5	input	data	—
MIDI In 10 (DIN, front)	front	midi din5	input	data	—
MIDI Out 1 (DIN)	rear	midi din5	output	data	—
MIDI Out 2 (DIN)	rear	midi din5	output	data	—
MIDI Out 3 (DIN)	rear	midi din5	output	data	—
MIDI Out 4 (DIN)	rear	midi din5	output	data	—
MIDI Out 5 (DIN)	rear	midi din5	output	data	—
MIDI Out 6 (DIN)	rear	midi din5	output	data	—
MIDI Out 7 (DIN)	rear	midi din5	output	data	—
MIDI Out 8 (DIN, front)	front	midi din5	output	data	—
MIDI Out 9 (DIN, front)	front	midi din5	output	data	—
MIDI Out 10 (DIN, front)	front	midi din5	output	data	—
USB Host	rear	usb a	bidirectional	data	—
USB Device 1 (USB-B)	rear	usb b	bidirectional	data	—
USB Device 2 (USB-B, front)	front	usb b	bidirectional	data	—
Ethernet MIDI (RJ45)	rear	RJ45	bidirectional	data	—
DC In (9V, 2mm)	rear	dc barrel	input	power	—

Showing 25 of 25 documented physical ports. Scroll to review the remaining rows.

05 · Compare the decision, not just the price.

Alternatives

The rows are organized around fit, power, I/O, and system role so a cheaper unit cannot hide a more expensive workflow.

Compare	iConnectivity mio 10 MIDI InterfaceThis gear	Behringer FCB1010 MIDI Foot Controller	iConnectivity mio XL MIDI Interface	iConnectivity mioXM MIDI Interface
Fit	📐 1U	📐 Outside rack	📐 1U	📐 1U · half-rack
Power	⚡ 3W	⚡ 5W	⚡ 5W	⚡ 2W
Weight	⚖️ 1.1 lb	⚖️ 8.2 lb	⚖️ 2.2 lb	⚖️ 0.7 lb
I/O	🔌 25	🔌 1	🔌 16	🔌 12
Estimate	💵 ~$299	💵 ~$149	💵 ~$499	💵 ~$179
Deep dive	Current selection	Full comparison →	Full comparison →	Full comparison →

06 · Resolve the questions that can change the purchase or build plan.

Planning questions

Short, source-backed answers surface rack fit, power, cabling, and connection details before they become surprises.

How will the iConnectivity mio 10 MIDI Interface affect rack fit and case depth?

It occupies 1U. Its documented depth is 140 mm.

How much power does the iConnectivity mio 10 MIDI Interface draw?

Typical draw is 3W and documented maximum draw is 5W.

What connections does the iConnectivity mio 10 MIDI Interface have?

25 documented physical ports, including MIDI In 1 (DIN), MIDI In 2 (DIN), MIDI In 3 (DIN), MIDI In 4 (DIN), MIDI In 5 (DIN), MIDI In 6 (DIN).

07 · See this unit inside a real rack plan.

Builder preview

Placement is only the start. Builder checks space · depth · weight, power headroom, dependencies, and compatible signal paths around this exact catalog item.Open in Builder

08 · Related gear, in the order you may need it.

MIDI Controller

iConnectivity mio XL MIDI Interface

1U · 16 ports · ~$499

MIDI Controller

iConnectivity mioXM MIDI Interface

1U · half-rack · 12 ports · ~$179

MIDI Controller

Ableton Push 3

Outside rack · 3 ports · ~$1,099

External unit

MIDI Controller

Keith McMillen 12 Step MIDI Pedal

Outside rack · 1 ports · ~$199

MIDI Controller

Behringer FCB1010 MIDI Foot Controller

Outside rack · 1 ports · ~$149

External unit

MIDI Controller

Morningstar MC8 MIDI Controller

Outside rack · 2 ports · ~$359

Planning guides for midi controller systems.

Workflow · 14 min

Building a Click + Tracks Playback Rig: From Laptop to Multi-Output Interface

How to build a live-performance playback rig that runs click + backing tracks reliably — interface sizing, routing rules, software comparison, and what to do when the laptop crashes.

Workflow · 12 min

Redundant Playback: Two Laptops, an Auto-Switching Interface, and Why You Need One

How to build a fail-safe live playback rig with primary + backup laptops, an auto-switching audio interface, and a failover workflow you can actually trust on a Sunday morning.

Product overview

MIDI Controller decisions, organized around the whole rig.

How it works in the path

Where it earns its place in the rack

Signal path

11 documented inputs

Compatibility

Best fit · MIDI Controller

Plan the companion path

Connector boundary

I/O ports

Every connector, grouped by job.

Alternatives

Planning questions

Builder preview

iConnectivity mio XL MIDI Interface

iConnectivity mioXM MIDI Interface

Ableton Push 3

Keith McMillen 12 Step MIDI Pedal

Behringer FCB1010 MIDI Foot Controller

Morningstar MC8 MIDI Controller

Related articles

Building a Click + Tracks Playback Rig: From Laptop to Multi-Output Interface

Redundant Playback: Two Laptops, an Auto-Switching Interface, and Why You Need One