#TOUCHOSC EDITOR COLOR FOR ANDROID#
#TOUCHOSC EDITOR COLOR ANDROID#
#TOUCHOSC EDITOR COLOR SOFTWARE#

I even tried entering that address in the host section of the TouchOSC configuration screen, and that didn't get the TouchOSC working to control SONAR transport, either. Also, there was a local IP address at the bottom of the TouchOSC configuration screen that was different from those listed under Host (guessing). I still get '0, Active clients' after I push done on the TouchOSC screen. There's something I'd like to point out: In your instructions you write to 'Put the Host you see into TouchOSC configuration.' Well, on the AZCtrl Options Tab, when I press 'Configure' in the 'OSC' section, the AZCtrl shows near the bottom: Host (guessing) 169.254.113.9 169.254.174.220 192.168.19.2 I tried all those addresses in the TouchOSC configuration screen, but they didn't work. I went and downloaded the AZ Controller test version (azctrl_0_5r0b310) from your forum and downloaded the 2 files you linked to (the spp file and the OSC_Phone_1_0 file, , followed your steps from , but it's not working.

#TOUCHOSC EDITOR COLOR ANDROID#

And the very last note: all labels you see on the picture except standard button names are coming from Sonar, not from TouchOSC editor and not from photoshoping.Īzslow3: I went and bought the TouchOSC App for my android to test this out. Also with several in parallel, also in combination with conventional MIDI and joystick devices.

#TOUCHOSC EDITOR COLOR SOFTWARE#

OSC freedom is great No other software on PC side is required (no OSCMIDI bridges), the solution can be used with any OSC capable Apps. Unlike other solutions, it is not limited by Mackie Control. For other use cases not only layout but also functionality can be different. Buttons on the lower part are ACT buttons directly (and they function as such, of course with feedback)That setup is for controlling Sonar remotely, when you can not see the screen. The parameter can be selected pressing left (ACT Faders) or right (ACT Knobs) buttons. After tests with 'encoders' and 'knobs', I came to the conclusion it is better have on good working fader (touch sensitive, for overwriting automations) then many half functional touch knobs. On the third screen you can see ACT Dynamic mapping, with ProChannel/FX Bin support (pressing 'FX' button round switching between all existing FX and ProChannel plug-ins for focused strip) as well as corresponding Synth.You can solo/mute consequent channels by swiping On the second screen you can see 16 channels, with mute and solo status.Mute/Solo/Rec/Automation Read/Write, all together without switching 'modes'.You can see compete strip names (not cut by 6-8 characters!), the are also active, the middle one can be touched to switch between track and buses and it change the color to indicate the fact.Time display change the color when in Play and Recording mode.Pan is touch sensitive (can be used to overwrite automation), the volume fader is also touch sensitive (but that you could see before).'Sync' is to recall all information from Sonar, for example in case you have switched the phone off for a while.On the top of the first screen you can see marker names, they are updated 'real time' and they are touch sensitive.But let me point you on some details you have not seen, at least not when that (or any other such) program is used with Sonar:

#TOUCHOSC EDITOR COLOR FOR ANDROID#

Sure, the pictures are from TouchOSC for Android ( ). So I have decided to share 'print screens' from my phone (3 screens from different tabs, combined into one picture): After quick looking at the picture, you can conclude that you have already seen many such 'setups'. And I am happy to see it is really working. AZ Controller 0.5 Sneak preview (OSC support for Sonar)

Touchosc editor color