View Single Post
Old 09-28-2020, 08:29 PM   #2
Human being with feelings
Join Date: Nov 2011
Posts: 27

Hey Kitarraman,

I took a glance at your layout and juding from its contents and your post I think you missed one important concept of how TouchOSC works and OSC in general.

If you configure its controls the way you did, by enabling MIDI messages to be sent, these messages won't be sent via the OSC protocol but as pure MIDI information. In order for TouchOSC to send pure MIDI to REAPER, some sort of "bridge" is needed in between them. OSC messages (not MIDI) can be sent directly to REAPER via Wi-Fi and through the selected ports. Pure MIDI messages get to your computer but they get stuck before getting to REAPER.

The "brige" I mentioned above exists though and Hexler made their own TouchOSC bridge which is in fact a companion for the mobile app for those who want to send pure MIDI (just like you). Here's the link to it:
1. Download it to your computer, install and run it.
2. You'll see its icon in your tray bar (if you're on Windows like me - don't know where it pops out on a Mac) and you can close it from there after you're done with it. For now you need it running though because it will serve as a mediator between TouchOSC and REAPER.
3. Go to REAPER.
4. There you need to configure your track to receive these messages.
4.1. Before that though, I believe that for the first time you need to enable TouchOSC Bridge in your MIDI devices (REAPER Preferences>Audio>MIDI Devices) if it's not already enabled by default when it's running - I'm not sure because I've done it quite some time ago - be sure to check it for yourself. If you don't see it there in the list of your MIDI devices, be sure to check it's running (tray bar) and then click the "Reset all MIDI devices" button which will rescan those which are available. As you might've guessed from everything written so far TouchOSC Bridge acts in REAPER as a MIDI device - like any other MIDI controller.
5. When you are sure that it's available and enabled, go to the track which should receive MIDI messages sent from TouchOSC and arm it.
6. Right-click on the track's input control and set its input to "Input: MIDI">"TouchOSC Bridge">"All channels" or "channel 1" in your case (judging from the channels you chose in your TouchOSC layout). You might've noticed that this is the same procedure as setting up a MIDI keyboard.
7. If you want REAPER to also send MIDI messages back to the TouchOSC app you also need to configure a MIDI Hardware Output send.
7.1. Open this track's routing and add a MIDI Hardware Output to TouchOSC Bridge. Now this track can also send MIDI messages back to the TouchOSC app.

As a final note: You can also send pure OSC messages which get converted in REAPER to MIDI messages and then I beleive they get sent via REAPER'S built in "Virtual MIDI keyboard" to your track (I haven't yet tried sending MIDI that way). This method does not require the TouchOSC Bridge application. You would need to configure your TouchOSC layout differently though and this is more complex than the above-described option I believe. In TouchOSC Editor you would need to go to the OSC tab and there untick the "auto" checbox. In the input field below it you would then enter a message which is defined in the .ReaperOSC file you plan to use as the "translator". The Default.ReaperOSC file for example defines several ways to send a CC message. One of them is this one "i/vkb_midi/@/cc/@". You would ignore the "i" before the first foward slash and copy paste the rest into the input field on TouchOSC Editor. Then you would have to replace the first "@" with the MIDI channel you want this MIDI data to travel through and the second "@" with the CC number.

I hope this helps somehow Cheers!
BenjyO is offline   Reply With Quote