MIDI via WiFi
MusiKraken can send MIDI events to other devices connected to the same local network. The events are sent using the RTP-MIDI protocol, so the receiving device needs to support this as well.
On iOS, you can use the official Apple implementation of the RTP MIDI protocol.
And I added my own implementation of the protocol, called Snarp Network MIDI, which runs on Android.
(Note: I previously also included the Snarp Network MIDI module on iOS, but removed it because iOS started blocking the ports needed for this.)
Core MIDI Network (iOS)
This can be used to send MIDI events to a different device (for example your computer that runs a DAW) via Wi-Fi. This control uses the Core MIDI implementation of the RTP MIDI protocol.
Ports:
MIDIIn:
All MIDI events sent to this port will be sent over Wi-Fi to any device connected to the Core MIDI default network session.
Snarp Network MIDI
This module uses my own implementation of the RTP MIDI protocol and mDNS to send MIDI events over the Wi-Fi to other computers.
Ports:
MIDIIn:
All MIDI events sent to this port will be sent over Wi-Fi to any device connected to this.
Settings:
Name: The name of the network instance as it will be shown on other devices in the network.
Target port: Which network port number should this instance use? Note that RTP MIDI always uses two ports, that is why this increases in steps of two.
Delay: How much into the future should the MIDI events be played? This is useful for any module that has a rhythm. As the latency between when a MIDI event is sent and when it is received by the target device can vary, the larger the delay, the more exact the rhythm will be. But of course large delays are more difficult to use (and more boring), so this setting should depend on your network speed.
Automatic reconnection: Should this module initiate the previously active network session, and make reconnection faster this way? Note that the usefulness of this depends on the receiving software. For example on rtpMIDI on Windows, the previous session will be reactivated automatically anyways (but slower), and if you enable this, there will be two connections.
