If you want REAPER to also send MIDI messages back to the TouchOSC app you also need to configure a MIDI Hardware Output send.ħ.1. You might've noticed that this is the same procedure as setting up a MIDI keyboard.ħ. 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). 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.Ħ. As you might've guessed from everything written so far TouchOSC Bridge acts in REAPER as a MIDI device - like any other MIDI controller.ĥ. 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. 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. There you need to configure your track to receive these messages.Ĥ.1. For now you need it running though because it will serve as a mediator between TouchOSC and REAPER.Ĥ. 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. Download it to your computer, install and run it.Ģ. 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). Pure MIDI messages get to your computer but they get stuck before getting to REAPER. OSC messages (not MIDI) can be sent directly to REAPER via Wi-Fi and through the selected ports. In order for TouchOSC to send pure MIDI to REAPER, some sort of "bridge" is needed in between them. 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. 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. I'll leave attached my custom layout, just in case I expected TouchOSC to work with Reaper right out of the box but I was apparently wrong □ Well, after reading the documentation in Default.ReaperOSC I have no idea on how should I code my custom layout.Īnyone of you guys here managed to get their custom layouts working? Can you help a fella out? I tried reading the code on LogicTouch.ReaperOSC but couldn't make much of it, there's almost no tutorial on YT on how to use a custom layout on Reaper and, at this point, I'm wondering if I should've gone with Jon Tidey's ReaperWRB instead. So I dig deeper into the Hexler documentation and, for what concerns TouchOSC integration with Reaper, they send you to the ReaperOSC page for documentation. Hi folks, I spent the whole day yesterday trying to set a Custom Layout on TouchOSC in order to control the Control Changes on my Virtual Instruments.Īfter I finished working on my Layout, I uploaded it on my device via TouchOSC Editor and it wasn't working, it was sending MIDI signals to Reaper but with no effect on the virtual instrument.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |