Your DAW sees it as hardware. The data travels over Ethernet.
Virtual MIDI ports, zero configuration, mDNS peer discovery. LAN-native.
Zero config. Real time. LAN native. — No cables. No drivers. No reboot. No surprises at showtime.
Define your virtual MIDI ports, set the direction, choose the network interface. MIDInet handles the rest — peer discovery, routing, transport. No IP addresses to manage.
The [STARTUP COMMANDS] section
runs console commands automatically at launch — perfect for unattended stage rigs.
No GUI. No preferences window. No menu bar. MIDInet runs entirely from a terminal REPL with command history, live monitoring, and instant peer visibility.
MIDInet is for musicians, engineers, and technicians who run multiple computers in a studio or on stage and need them to speak MIDI to each other — without dedicated interfaces, MIDI-over-USB hubs, or manual network configuration. If you already have a LAN, you already have the cable.
MIDInet is a purpose-built tool. Not a platform, not a framework — a router. Here is exactly what it does.
Virtual MIDI ports that your DAW and applications see as physical hardware. Data travels via UDP multicast on 239.0.100.1:47910. No special driver, no virtual loopback cable.
Peers discover each other via mDNS-SD (_midinet._udp.local.). Bring a second machine onto the network and it appears automatically. No IP addresses, no address book, no pairing step.
Each virtual port is independently bound to a specific network interface — Ethernet, Wi-Fi, Dante NIC. In multi-homed setups you control exactly which network carries which MIDI signal.
Every port has a configurable direction. TX: your DAW sends, data goes to the network. RX: network data arrives, your DAW receives. BIDIR: both simultaneously. LOOPBACK: TX port receives its own transmitted data for monitoring.
Full terminal REPL with command history. show · monitor · filter · reload · send · test · debug. Reload config without restarting the process. Filter monitor output by message type.
Every UDP packet carries a MNET magic header, version field, sender UUID, per-device sequence counter, microsecond timestamp, and CRC32. Malformed or corrupt packets are silently dropped.
One TX port reaches all RX ports simultaneously. No unicast fan-out, no central broker, no server to maintain. The network handles distribution. Scope is LAN-only — data does not leave your subnet.
No internet connection required. No cloud, no license server, no telemetry. Runs on an isolated LAN. Startup commands in config.ini execute automatically — zero interaction needed on stage systems.
Discover all MIDInet peers visible on the LAN from a single machine. The built-in ping command measures round-trip response time for each peer and reports the MIDInet version running on it — so you know the entire network is up before a show starts.
Mac and Windows machines talk to each other — no exceptions.
MIDInet is not "cross-platform" in the sense that it runs on multiple OS separately. A Mac and a Windows PC on the same LAN exchange MIDI data in real time, transparently. A mixed setup — some Macs, some Windows machines — works exactly like an all-Mac or all-Windows rig. The OS is invisible to the network.
| Command | Syntax | Description |
|---|---|---|
| show | show | Status table for all virtual MIDI cards: mode, loopback, network, IP, status, connected peers |
| monitor | monitor on|off | Enable or disable real-time display of MIDI messages with timestamp, direction, card, and message type |
| filter | filter realtime|sysex|pc|short|off | Hide message types from monitor output. Multiple filters accumulate. off clears all filters |
| discovery | discovery on|off|<seconds> | Set mDNS peer discovery polling interval. Lower = faster detection, more CPU. Default: 3s |
| reload | reload | Full in-process restart: destroy all devices, re-read config.ini, recreate ports, re-register mDNS, run startup commands |
| send | send <card> [note|cc|pc|realtime|sysex] | Simulate a MIDI message from a card. Useful for testing transport without a physical MIDI source |
| test | test <device> <note> | Send Note On (velocity 100) to a specific device. Quick connectivity test |
| debug | debug | List all detected network interfaces with IPs and all MIDI devices visible to the system |
| config | config | Show loaded configuration summary: card count, startup commands |
| quit / exit | quit | exit | Graceful shutdown: deregister mDNS services, close sockets, exit |
No subscription. No activation server at runtime. Activate once, use forever on up to 2 computers.
activation command in the MIDInet console. Max 2 simultaneous activations per license. Deactivation frees a slot.
30-day free trial · full features · no credit card required
Mount the DMG · drag MIDInet to Applications · launch from Terminal
Run the installer · launch MIDInet from Windows Terminal
MIDInet runs for 30 days without a license key. All features are fully available during the trial.
To activate, purchase a license and run the activation command in the MIDInet console:
Up to 2 computers can be activated simultaneously per license. Deactivating a machine frees a slot.
Network: All machines must be on the same LAN segment. UDP multicast must not be blocked. UDP port 47910 and mDNS port 5353 must be open and reachable between all hosts.
Ports: Any number of virtual MIDI ports can be created, each with a custom name. Ports are added and removed at runtime — no reboot required.
Performance: MIDInet is a lightweight CLI binary. Typical RAM usage <15 MB. No GPU, no audio driver required.
Lifetime license · up to 2 computers · offline after activation
Secure payment via PayPal. You will receive your license key by email within minutes.
For support, licensing questions, or feedback on MIDInet, write to info@azlive.io or use the form.