A basic setup for you to get started working with TouchOSC. I’m going to experiment with the idle time and see how responsive i can make it, while making sure it runs flawlessly.
Touchosc editor help code#
The second code piece is my “Boilerplate” where I put the actual music loops. In a new template I have created a button that sends a keystroke, for example the M key (for toggle mute option in many audio and music apps) or the space bar (to start playing or stop anything). It works perfectly with the layout I linked above. I have seen that it is possible both in the old TouchOSC Editor and also using the old TouchOSC application for iOS. It’s not very complicated, just awfully repetitive. This first one is where I set up my communication with TouchOSC. This helped a ton, and now I can do fancy stuff with fading in and out and changing code snippets on the fly. So i also made a framework for having my five loops (one for each amplitude slider), and having them sleep when the amp is 0. I also ran into another problem, which is that since i wanted to fade my loops in and out, i needed them to run constantly. This script has a loop for each layout item, which waits for changes in the layout items. So what I did was to save a script for setting up the process of gathering data, and loading that in another buffer. Using get will give you the most up-to-date data, but it takes up a ton of resources, and even on the biggest machines Sonic Pi will start cracking and popping within 10 minutes or so. sync makes the code wait until something changes, whereas get continuously poll the device for data. With set, you can either get or sync the OSC data.
The general approach is to use set and get to store your OSC data in Time States and use those as a kind of global variable. This is where I ran into most of my trouble.
Touchosc editor help how to#
The question is how to save the data you get. You refer to it as a web address like “/osc/1/Slider1”, and TouchOSC gives you a floating point number back. It’s your instrument, after all!Īccessing the OSC elements is quite simple. OSC Layouts is a very personal thing, and I encourage you spend a bit of time making your own.
Touchosc editor help download#
You can download the layout file here and give it a try. My layout looks like this: 5 sliders for amplitude, 5 toggle buttons for on-off effects, and 6 sliders for messing with effects and parameters. Now launch Millumin, open the 'Device Manager' window (CMD+K) and choose the OSC tab. Once you got this part working, you’ll probably want to make a less expansive layout at first. If the connection works, you’ll see a ton of messages in the Cues section. Once you’ve done this, open Sonic Pi and TouchOSC, pick a layout on your app, and give one of the sliders a wiggle. You will also want to set the Outgoing Port field to 4559, since that’s the port Sonic Pi expects to get OSC messages from. In TouchOSC you will need to set up the connection between it and your computer by entering the IP Address of the machine. Then you need to grab the TouchOSC App from the App Store / Play Store. The first thing you need to do is go to settings -> Input/Output and allow Sonic Pi to receive external OSC messages. Hopefully this will help someone avoid a few of the problems I ran into. I spent easter getting TouchOSC to work with sonic pi and I thought I’d share my work.
0 kommentar(er)
