Network MIDI

Neurode MIDI supports Network MIDI (RTP-MIDI), allowing wireless MIDI connections between devices over Wi-Fi or wired networks.

What is Network MIDI?

Network MIDI (also known as RTP-MIDI or AppleMIDI) is a protocol that enables MIDI data transmission over standard IP networks (Wi-Fi, Ethernet). It's built into macOS and iOS, making it easy to connect:

• DAWs to mobile devices wirelessly
• Multiple devices without physical MIDI cables
• Cross-room setups using existing network infrastructure
• Network-attached hardware like Korg plugKEY or iConnectivity interfaces

Enabling Network MIDI

1. Open Settings (gear icon in top navigation)
2. Scroll to the Connectivity section
3. Toggle Enable Network Session ON

Once enabled, Neurode MIDI appears as a network MIDI source on other devices running macOS/iOS with network MIDI enabled.

Connection Policies

Choose who can connect to your Network MIDI session:

Policy	Description	Use Case
Anyone	Any device on the network can connect	Home studio, trusted networks
Contacts Only	Only devices in your Directory	Public networks, collaborative sessions
No One	Network session is enabled but accepts no connections	Outbound-only connections

To change the policy:

1. Open Settings → Connectivity
2. Select Network Policy
3. Choose your preferred policy

How to Connect

macOS → macOS/iOS

1. On the sending device (macOS/iOS):

   • Open Audio MIDI Setup (macOS) or Settings → Bluetooth & Network (iOS)
   • Enable Network Session
   • Look for Neurode MIDI in the Directory list
   • Click Connect

2. On Neurode MIDI:

   • Ensure Network Session is enabled in Settings
   • Set policy to Anyone or Contacts Only
   • The connection appears automatically in the Sources list

iOS → macOS Running Neurode MIDI

1. On iOS device:

   • Settings → Bluetooth → scroll down to Session
   • Enable Network Session
   • Tap the device running Neurode MIDI

2. On Neurode MIDI:

   • Source appears in routing matrix automatically
   • Route to desired destinations

DAW Integration (Logic Pro, Ableton Live, etc.)

Most DAWs discover network MIDI sources automatically:

1. Enable network session in Neurode MIDI
2. In your DAW, check MIDI Input/Output preferences
3. Look for "Neurode MIDI" in available MIDI ports
4. Enable the port for input/output

Logic Pro

1. Logic Pro → Settings → MIDI
2. Under Inputs, enable Neurode MIDI
3. Tracks will now receive MIDI from Neurode MIDI

Ableton Live

1. Live → Preferences → Link/Tempo/MIDI
2. Under MIDI Ports, enable Neurode MIDI (Track + Remote)
3. Select Neurode MIDI as MIDI From on any track

Port Number

Network MIDI uses UDP port 5004 by default. Ensure this port is not blocked by:

• Firewall software (macOS System Settings → Network → Firewall)
• Router firewall rules (for cross-subnet connections)
• VPN software that may block local network discovery

Latency Considerations

Network MIDI adds 2-10ms latency depending on:

• Network quality (Wi-Fi vs Ethernet, signal strength)
• Network congestion (other devices on the network)
• Device distance (same subnet vs routed)

Best practices for low latency:

• Use 5 GHz Wi-Fi instead of 2.4 GHz (less congestion, higher bandwidth)
• Wired Ethernet when possible (lowest latency)
• Minimize Wi-Fi hops (connect devices to same access point)
• Disable power saving on Wi-Fi adapters (macOS: System Settings → Battery → Options)

Troubleshooting

Device Not Appearing

Problem: Remote device doesn't appear in Network MIDI directory.

Solutions:

1. Check both devices are on the same network (same Wi-Fi SSID or subnet)
2. Verify network session is enabled on both devices
3. Disable and re-enable network session on both devices
4. Check firewall settings (UDP port 5004 must be allowed)
5. Restart network session in Audio MIDI Setup (macOS) or Settings (iOS)

Frequent Disconnections

Problem: Network MIDI connection drops intermittently.

Solutions:

1. Move closer to Wi-Fi access point (improve signal strength)
2. Switch to 5 GHz Wi-Fi (less interference from Bluetooth, microwaves, etc.)
3. Use wired Ethernet if available (most reliable)
4. Reduce network congestion (pause large downloads, streaming)
5. Update router firmware (newer firmware often improves stability)

High Latency / Jitter

Problem: Noticeable delay or timing inconsistency.

Solutions:

1. Use Ethernet instead of Wi-Fi (latency typically drops to <2ms)
2. Switch to 5 GHz Wi-Fi (lower latency than 2.4 GHz)
3. Reduce Wi-Fi congestion (fewer active devices on network)
4. Disable power saving on Wi-Fi (prevents adapter sleep)
5. Check for background network activity (cloud sync, system updates)

Security Considerations

Network MIDI transmits unencrypted MIDI data over the network. Sensitive performance data is visible to anyone with network access.

Recommendations:

• Use Contacts Only policy on public/shared networks
• Connect via private Wi-Fi networks when possible
• Avoid public Wi-Fi for live performances (unreliable + security risk)
• Use VPN or encrypted tunnels for internet-based network MIDI (advanced)

Technical Details

Protocol: RTP-MIDI (RFC 6295) Transport: UDP/IP Default Port: 5004 (control) + 5005 (data) Latency: 2-10ms typical (network-dependent) Jitter Compensation: Built into CoreMIDI stack Maximum Connections: Limited by network bandwidth and device capabilities

Network MIDI sessions are managed by CoreMIDI's MIDINetworkSession class. Neurode MIDI configures the session policy and monitors endpoint availability, but CoreMIDI handles all protocol details (session establishment, keepalive, packet reassembly).

Related Features

• Bluetooth MIDI - Another wireless option (see Bluetooth MIDI)
• Virtual Ports - Create virtual MIDI ports for DAW integration (see Virtual Ports)
• Routing - Route network MIDI sources to any destination (see Routing Guide)

Advanced: Command-Line Tools

You can inspect network MIDI connections using macOS command-line tools:

# List all active network MIDI sessions
/usr/bin/dns-sd -B _apple-midi._udp

# Monitor network MIDI packets (requires Wireshark)
sudo tcpdump -i any -n udp port 5004

These tools are useful for diagnosing network-level connectivity issues.