Manually adding RTP sessions
TouchDAW's RTP sessions will usually be announced over multicast DNS and will appear automatically in rtpMIDI and OS X's Network MIDI control panel. If that is not possible (a network might not allow for multicast for example) you can add sessions manually in the drivers' control panels. Here's how (screenshots from OS X, this works in exactly the same way with rtpMIDI on Windows with one little difference shown below)
- Click the "+" underneath the Directory listing.
- In the upcoming dialog shown above
- Add a session name (whatever you like best will be fine).
- Enter the device's IP address. TouchDAW shows it at Setup / Global / System Info. For teethered or hotspot networks it will be predefined by Android in most cases:
- For USB tethering: 192.168.42.129
- For Bluetooth tethering: 192.168.44.1
- Android portable hotspot: 192.168.43.1 (This may be 192.168.1.1 with some HTC phones)
These numbers are based on observations made on numerous devices. They always seem to be the same. However, you usually can not take anything for granted with Android, so if the weather is bad they may be different. TouchDAW will tell you which IP address and port number it wants to use when you select a MIDI connection.
- enter the port number for the resp. session. This will be 6504 for TouchDAW's first connection (DAW Controller) and 6506 for the second session (Keyboard, XY, etc.).
|Note that rtpMIDI does not have a seperate port field, but wants IP address and port number in a single line, seperated by double-colon. For example 192.168.44.1:6504.
- Click OK and a new entry will appear in the Directory. Manually added sessions look a bit different and will be stored permanently until you delete them. (other than discovered session, which will disappear when the device does no longer respond to DNS queries).
- After this you can proceed as with any other RTP session: Select it in the directory, click ""Connect", see it appear in the Participants listing on the right and exchange MIDI over it. Note that non-WIFI sessions may take a few seconds until they become fully functional and you see data flow.