RTP-MIDI setup
RTP-MIDI carries MIDI over your local network. FrenschPress accepts connections or connects to saved participants itself. Either way, MIDI travels in both directions. The role only decides who starts the connection.
Enable it
- Open Settings → RTP-MIDI.
- Turn on Enable RTP-MIDI and choose Save Settings. The session name is the device name.
- Open Sessions & status. This is where you set up the connection and see the live status.
Connection mode
| Connection mode | Use it when |
|---|---|
| Responder — accept incoming connections | The computer or MIDI router connects to FrenschPress |
| Initiator — auto-connect to saved peers | FrenschPress should establish the connection itself and restore it after a restart or network loss |
Only one side of a connection acts as initiator.
Setting up initiator mode
- Choose Initiator — auto-connect to saved peers.
- Under Available peers, choose Refresh peers. FrenschPress searches for advertised RTP-MIDI participants.
- Select a participant. Its address and port are filled into the form. For devices that don't advertise themselves, enter the IPv4 address and Control port manually.
- Optionally add a second peer. You can enter up to two peers.
- Choose Save connection settings. The settings only apply after this.
The usual control port is 5004; the data port is one higher. Use the values configured on the destination, and fixed addresses or DHCP reservations.
Connect from a computer
In responder mode, the computer starts the connection:
- Mac: open Audio MIDI Setup → MIDI Network and connect the discovered FrenschPress to your session.
- Windows: a configured RTP-MIDI application establishes the connection.
Then select the matching MIDI input and output in your show software.
Reading status
| Display | Meaning |
|---|---|
| Disabled | Network MIDI is off |
| Waiting for a connection | The service is running, no participant is connected yet |
| Connected | At least one participant is connected |
| Session members | Participant name, address, connection state and last synchronisation |
| Traffic & diagnostics | Sent packets and error counters since boot |
The display refreshes while the dialog is open. A sent packet only means it was handed to the local network interface. Check the destination to confirm the intended cue ran.
Troubleshooting
| Symptom | Check |
|---|---|
| No connection | Address, control port and network. The peer must be reachable. |
| No connection in initiator mode | Does the destination accept connections? |
| Refresh peers finds nothing | Discovery only works on the local network. Enter the peer manually; this works with an empty list too. |
| Connection drops repeatedly | Cables, switches and WiFi signal |