RTP MIDI User Space Driver Daemon for Linux
Real Time Protocol Musical Instrument Digital Interface Daemon
Alpha software. Use at your own risk.
rtpmidid allows you to share ALSA sequencer devices on the network using RTP
MIDI, and import other network shared RTP MIDI devices.
rtpmidid is an user daemon, and when a RTP MIDI device is announced using mDNS
(also known as Zeroconf, Avahi, and multicast DNS) it exposes this ALSA
There is many hardware with RTP MIDI support, normally controllers, but for example Behringer DeepMind12 Synthetizer has support over Wifi.
- raveloxmidi - Intended to be used directly with hardware devices or emulate midi over FIFO.
- rtpmidi from McLaren Labs. It is a feature complete, GUI driven, Comercial implementation. Very similar to Tobias Erichsen's rtpmidi.
On MacOS there is support included in the OS.
To test I used
MIDI Network and
MIDI Wrench. The first to manage
connections, the second to test.
I was able to communicate exporting at rtpmidid side conneting my gadget to the
Network port. Then use the
MIDI Network on the iPad to make the connection.
- rtpmidi by Tobias Erichsen.
Mobile / Tablet
There are also many Apple iPad / iPhone and Android programs with rtp midi support. I will try to list them as I find them:
How to use
rtpmidid provides two modes of operation, one focused on importing another on
For each found mDNS item, and connections to port
5004 (by default), it creates
alsa seq ports which provide the events on those endpoints.
For mDNS discovered endpoints, the connection is delayed until the alsa seq connection.
Also it can connect to other endpoints by ip and port. Right now it is only possible at but in the future via some other running mechanism, as watching for a config file changes.
To export a local alsa sequencer port, connect it to the "Network" port.
It will create the server, announce the mDNS service so other endpoints know it exist, and accept connections.
MIDI data is rerouted to the proper endpoint by checking the source port.
When connecting the Network port to an input, it merges all the midi events from all exported services. Normally this is not the desired behaviour, so it is recomended to export output ports, not input ones. This will be fixed in the future.
- Daemon, no need for UI
- ALSA MIDI -- Inputs as ALSA MIDI inputs, outputs a ALSA MIDI outputs
- Autoconfigurable for mDNS Endpoints
Features and status
Development status / plan:
- mDNS client/server
- Async framework (epoll with callbacks based code)
- mDNS publish and learn when there are rtpmidi running on the network
- Create the alsa ports for found rtpmidi servers in the network
- When there is any connection to the alsa sequencer port
rtpmididcreates the rtpmidi connection
- Any message from alsa seq is sent to the MIDI rtp extreme
- Any message from rtpmidi is replayed on the alsa seq
- Can export local ports, with user deciding which ones to export.
- Server mode at a known port, when remote side request connections, create the alsa seq virtual port for that connection and connect both ports.
- Allow several connections on the server port. Each its own aseq port.
- Send all MIDI events to rtpmidi
- Receive all MIDI events from rtpmidi
- Periodic check all peers are still on, no new peers
- Remove ports when peer dissapears
- Client send CK every minute
- Can be controlled via Unix socket, but not required.
- Jack MIDI support instead of ALSA seq
- Use rtp midi timestamps
- Journal support for note off
- Journal support for CC
- Journal support for Program Change
- Journal support for Pitch Bend
There is a basic CLI that used the Unix socket control.
Unix socket control
It is possible to change runtime parameters.
To do it there is an optional control socket that could be use in the future by a GUI.
By the moment, only direct connection works. Check CONTROL.md file for more information, but as a teaser, the following command creates a new ALSA port that connects to this IP and port:
echo "create DEEPMIND12 192.168.1.17 5004" | nc -U /var/run/rtpmidid/control.sock"
Requires C++17 (Ubuntu 18.04+), and libfmt-dev, libasound2-dev, libavahi-client-dev.
To compile and run, execute:
There are some command line options:
Share ALSA sequencer MIDI ports using rtpmidi, and viceversa. rtpmidi allows to use rtpmidi protocol to communicate with MIDI equipement using network equipiment. Recomended use is via ethernet cabling as with WiFi there is a lot more latency. Internet use has not been tested, but may also deliver high latency. Options: -v Show version -h Show this help -n name Forces a rtpmidi name -p port Opens local port as server. Default 5400. Can set several. hostname Connects to hostname:5400 port using rtpmidi hostname:port Connects to a hostname on a given port name:hostname:port Connects to a hostname on a given port and forces a name for alsaseq
RtpMidid is GPLv3 licensed. This basically meass that you are free to use, modify and share it, given that you share your modifications with your users.
This includes embeded software uses (anti tivoization clause of the GPLv3).
If you think the license does not fit your use case, please contact me at email@example.com for alternative licensing options. I'm a freelancer looking for new projects.