Hi I’m looking for somebody to help me through the process of setting up touchOsc to control Renoise.
I’m aware there are a few more steps involved than just plug and play and want to get a firm grasp on it.
So I’m running Renoise 3.1 on a 2008 MacBook, touchOsc on an IPad Air 2. I’ve also got an octatrack synced over midi to Renoise so potential for more fun.
I’m going to play dumb here as I have an idea how to do it but pretty sure I’m going to screw something up.
What have you done so far? Have you created custom OSC address pasterns in TouchOSC, things that correspond to the patterns that Renoise will understand?
I haven’t used TouchOSC in a while, and never on any Apple devices, so I don’t recall if the TouchOSC editor allows you to create address patterns that play nice with the default Renoise OSC handlers.
.
Have you looked at https://forum.renoise.com/t/renoise-ultimate-touchosc-ipad-template/34127 ?
No I haven’t created anything in touchosc yet, only downloaded the app. Not through laziness, I’ve got kids so the rare moments I get to make music I like to spend making tracks rather than twiddling.
I’ve got a cloned sample library of anything I’ve got going on in Renoise on my octatrack so I can switch between software and hardware when the fancy takes me. I’ve also got an mpk49 controlling the main stuff in Renoise. Would adding touchOsc into the mix add anything for me do you think or am I headed for controller overload?
I’ll have a look at that thread and see what’s what. Many thanks
That should give you an idea of one way to get rolling with TouchOSC, and perhaps see how to change things to suit you interests.
I can’t say if you’re headed to controller overload. OTOH, if you don’t already see how something is supposed to fit into your recording/composing/performance routine then there may be little reason to pursue it. But also believe that often you don’t know the value of something until you’ve played around with it.
One of the nice things about TouchOSC is that you can create your own control surfaces (in contrast to physical hardware, unless you build your own).
I’ve gotten great use out of Control (http://charlie-roberts.com/Control/) by creating my own screens. I prefer it to TouchOSC because it gives better control over definfin OSC address patterns. The downside is that it’s a bit flakey and (as best I can tell) notactivelymaintained.
I’ve also written a simple Android app to provide a flexible OSC controller. The ability to define a UI and OSC messages to suityourselfis a powerful option so I’d encourage exploring TouchOSC andgettingfamiliarwith what it can do with Renoise.
I’ll have a look at that thread and see what’s what. Many thanks
Duplex comes with this iPad template. You just need to specify the usual port information and you should be ready to use it.
Of course, TouchOSC is basically just a bunch of buttons and sliders. So that example is an improvement because it makes them actually do something. All of that is achieved through the TouchOSC example configurations, which again is using the “applications” that come with Duplex. It’s a quite flexible system B)
But yeah, how deep you want to go is a matter of preference.
