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 😕
#Touchosc editor no jvm how to
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 kommentar(er)
