Really loving iPhone TouchOSC + OSCulator + Live right now. But I haven't been able to make TouchOSC's toggle buttons actually toggle things in Live. I think I've tried every combination of OSCulator mappings but so far I haven't been able to get it to work correctly.
I just want to do simple things like solo tracks, turn devices on/off, etc. - anybody got this working?
Thanks,
Matt
TouchOSC toggles?
Re: TouchOSC toggles?
MIDI LEARN.Did you try this?Calhoun wrote:Really loving iPhone TouchOSC + OSCulator + Live right now. But I haven't been able to make TouchOSC's toggle buttons actually toggle things in Live. I think I've tried every combination of OSCulator mappings but so far I haven't been able to get it to work correctly.
I just want to do simple things like solo tracks, turn devices on/off, etc. - anybody got this working?
Thanks,
Matt
http://www.myspace.com/djvakis
http://mix2r.fm/audio/user/221
----------------------------------------
MacBookPro 13" Core 2 Duo 2.26Ghz 2GB
Live 8 -Operator -Sampler
AKAI LPD8-GENELEC 1029A-iPhone runing TouchOSC.
http://mix2r.fm/audio/user/221
----------------------------------------
MacBookPro 13" Core 2 Duo 2.26Ghz 2GB
Live 8 -Operator -Sampler
AKAI LPD8-GENELEC 1029A-iPhone runing TouchOSC.
I am using MIDI learn. There's no other way to assign MIDI messages to Live's controls, is there?
Thanks for the pointer to the templates. I hadn't been using those, but I just opened up Mix16.oscd and it's very similar to what I had already set up. And toggles don't work correctly for me with either one.
For example, Mix16.osc has /2/toggle1 mapped to MIDI CC 22 on channel 1. In Live, I turn on MIDI learn, select the Solo button on one of my tracks, then hit the appropriate button in TouchOSC. This actually does create the mapping; it just doesn't work correctly. I have to hit the TouchOSC button twice for the Solo button to change state, and the TouchOSC button's state only matches the Live button's state half of the time.
Can you confirm that something like this is actually working correctly for you, i.e. that when you hit a TouchOSC toggle button to turn it on or off, a corresponding control in Live is immediately put into the same state?
This isn't a connectivity problem - the sliders and XY pads are very responsive.
Thanks for your help. Even with just the sliders and XY pads I'm having a blast, but I really want to get it all working.
Take care,
Matt
Thanks for the pointer to the templates. I hadn't been using those, but I just opened up Mix16.oscd and it's very similar to what I had already set up. And toggles don't work correctly for me with either one.
For example, Mix16.osc has /2/toggle1 mapped to MIDI CC 22 on channel 1. In Live, I turn on MIDI learn, select the Solo button on one of my tracks, then hit the appropriate button in TouchOSC. This actually does create the mapping; it just doesn't work correctly. I have to hit the TouchOSC button twice for the Solo button to change state, and the TouchOSC button's state only matches the Live button's state half of the time.
Can you confirm that something like this is actually working correctly for you, i.e. that when you hit a TouchOSC toggle button to turn it on or off, a corresponding control in Live is immediately put into the same state?
This isn't a connectivity problem - the sliders and XY pads are very responsive.
Thanks for your help. Even with just the sliders and XY pads I'm having a blast, but I really want to get it all working.
Take care,
Matt
OK, I think I just figured out what the problem is, but not how to solve it.
OSCulator is sending 2 different values for the MIDI CC messages. It sends 127 for on and 0 for off. Presumably this is because TouchOSC is sending 2 different messages from its toggle buttons. But the Live controls change state in response to a single control value. My Solo button in the example above is responding to the CC 22 messages with a control value of 127 and ignoring those with value 0.
Strangely, according to Live's manual (if I'm reading it right), Live should be responding correctly to both the 127 and the 0 values. Isn't that exactly what the "Switches" paragraph in section 23.2.3 says?
Of course, I'm hoping someone who has this working correctly can tell me I've got it all wrong, and I really just need to press this one button somewhere, and all will be right...
Matt
OSCulator is sending 2 different values for the MIDI CC messages. It sends 127 for on and 0 for off. Presumably this is because TouchOSC is sending 2 different messages from its toggle buttons. But the Live controls change state in response to a single control value. My Solo button in the example above is responding to the CC 22 messages with a control value of 127 and ignoring those with value 0.
Strangely, according to Live's manual (if I'm reading it right), Live should be responding correctly to both the 127 and the 0 values. Isn't that exactly what the "Switches" paragraph in section 23.2.3 says?
Of course, I'm hoping someone who has this working correctly can tell me I've got it all wrong, and I really just need to press this one button somewhere, and all will be right...
Matt
Think I've found my answer here: http://forum.ableton.com//viewtopic.php?t=103118. Some of Live's toggle-able controls respond one way to MIDI CCs, and others respond differently. It depends on whether the controls can be automated (apparently solo can't - I didn't know that). Track activate buttons can be automated, and they work perfectly with TouchOSC's toggle buttons.
As I was composing my feature request for automate-able solo, I found this good argument for not automating the solo buttons: http://forum.ableton.com//viewtopic.php?t=107958. In light of that, I guess my request should be for consistent MIDI map behavior for all switch controls, regardless of whether they can be automated.
Matt
As I was composing my feature request for automate-able solo, I found this good argument for not automating the solo buttons: http://forum.ableton.com//viewtopic.php?t=107958. In light of that, I guess my request should be for consistent MIDI map behavior for all switch controls, regardless of whether they can be automated.
Matt
Re: TouchOSC toggles?
glad you figured some stuff out (i would have replied earlier but was out of town).
i noticed that certain controls in are assigned in the OSCulator templates as toggles / buttons / faders. . but am not sure how to edit these parameters.
but ones that are assigned as buttons seem to do what you are asking.
i would suggest you contact mr.hexler himself - seems like he's pretty good with support mails. keep us posted.
i noticed that certain controls in are assigned in the OSCulator templates as toggles / buttons / faders. . but am not sure how to edit these parameters.
but ones that are assigned as buttons seem to do what you are asking.
i would suggest you contact mr.hexler himself - seems like he's pretty good with support mails. keep us posted.
-
sans soleil
- Posts: 218
- Joined: Sat Jan 29, 2005 6:59 pm
- Location: toronto
- Contact:
Re: TouchOSC toggles?
in OSCulator, go into the touchOSC template and, for the buttons you want to assign, change the 'event type' from midi ccs to note numbers...that should do it.
Re: TouchOSC toggles?
Thanks for the responses. Here's what I've figured out:
TouchOSC has two types of buttons: "push" buttons and "toggle" buttons. The push buttons are stateless, and your suggestion works perfectly with them. In fact, they work just fine when mapped to MIDI CCs as well.
But the toggle buttons, which are what I'd like to map to Live's solo buttons, have a state of either On or Off (see why it makes sense to map them to solo?). Their state is indicated in the UI by the button appearing either filled or empty. And more importantly, these buttons send two different OSC messages depending on whether they're transitioning from On to Off or vice versa.
As you pointed out, OSCulator can map these OSC messages to MIDI CC or MIDI Note messages. But either way, OSCulator is still going to spit out, and Live is still going to receive, two different MIDI messages: CC messages alternating between control values 0 and 127, or Note messages alternating between Note On and Note Off. Buttons in Live that can be automated respond correctly to these messages; buttons that can't be automated don't.
So there are really two obstacles to doing what I want to do (which is solo my return tracks as part of a performance - not sure I ever mentioned that):
- Solo buttons don't respond in the same way as Live's other On/Off buttons to alternating MIDI messages.
- Solo buttons can't be automated anyway, so that part of the performances wouldn't be recorded even if they did work with TouchOSC.
I'm still trying to figure out whether it's reasonable to ask Ableton to change these 2 things.
Matt
TouchOSC has two types of buttons: "push" buttons and "toggle" buttons. The push buttons are stateless, and your suggestion works perfectly with them. In fact, they work just fine when mapped to MIDI CCs as well.
But the toggle buttons, which are what I'd like to map to Live's solo buttons, have a state of either On or Off (see why it makes sense to map them to solo?). Their state is indicated in the UI by the button appearing either filled or empty. And more importantly, these buttons send two different OSC messages depending on whether they're transitioning from On to Off or vice versa.
As you pointed out, OSCulator can map these OSC messages to MIDI CC or MIDI Note messages. But either way, OSCulator is still going to spit out, and Live is still going to receive, two different MIDI messages: CC messages alternating between control values 0 and 127, or Note messages alternating between Note On and Note Off. Buttons in Live that can be automated respond correctly to these messages; buttons that can't be automated don't.
So there are really two obstacles to doing what I want to do (which is solo my return tracks as part of a performance - not sure I ever mentioned that):
- Solo buttons don't respond in the same way as Live's other On/Off buttons to alternating MIDI messages.
- Solo buttons can't be automated anyway, so that part of the performances wouldn't be recorded even if they did work with TouchOSC.
I'm still trying to figure out whether it's reasonable to ask Ableton to change these 2 things.
Matt
-
sans soleil
- Posts: 218
- Joined: Sat Jan 29, 2005 6:59 pm
- Location: toronto
- Contact:
Re: TouchOSC toggles?
ey...good to know.
i've been using touchosc mainly with bidule, but was going to try mapping it to ableton @ some point.
i'm kind of surprised that solo buttons can't be automated.
have you tried iTouchMidi's MCU ?
it gives you a little mackie control emulation mixer with mute and solo buttons.
http://www.itouchmidi.com/?q=node/32
i've been using touchosc mainly with bidule, but was going to try mapping it to ableton @ some point.
i'm kind of surprised that solo buttons can't be automated.
have you tried iTouchMidi's MCU ?
it gives you a little mackie control emulation mixer with mute and solo buttons.
http://www.itouchmidi.com/?q=node/32
Re: TouchOSC toggles?
Looks interesting - I'll give it a try.
But I'm already so enamored of TouchOSC that I'm willing to try to work out the kinks over time. I haven't even tried some of the more complex controls yet. And the next version is supposed to have a means for creating custom UIs. That may be the point at which I get rid of all my MIDI control surfaces.
And surely it's only a matter of time before Live has native OSC support...
Matt
But I'm already so enamored of TouchOSC that I'm willing to try to work out the kinks over time. I haven't even tried some of the more complex controls yet. And the next version is supposed to have a means for creating custom UIs. That may be the point at which I get rid of all my MIDI control surfaces.
And surely it's only a matter of time before Live has native OSC support...
Matt