fabio m

I created a layout with the android app TouchOSC with a few buttons and by now I'm using OSC Bridge 

and Ableton midi mapping to remotely control the transport buttons and to launch specific clips.

Wanting to get rid of the Bridge, I tried to do this with M4L device OSC TouchOSC but I couldn't find a way to map it's output buttons to the transport and the clips buttons, after learning the buttons from the android app into the inputs of the M4L device.

And any serious and comprehensive documentation?

I created a layout with the android app TouchOSC with a few buttons and by now I'm using OSC Bridge 
and Ableton midi mapping to remotely control the transport buttons and to launch specific clips.

Wanting to get rid of the Bridge, I tried to do this with M4L device OSC TouchOSC but I couldn't find a way to map it's output buttons to the transport and the clips buttons, after learning the buttons from the android app  into the inputs of the M4L device.

Any help?
And any serious and comprehensive documentation?

I created a layout with the android app TouchOSC with a few buttons and by now I'm using OSC Bridge 
and Ableton midi mapping to remotely co

osc-can-i-map-m4l-touch-osc-to-transport-or-to-launching-clips

Hi Fabio, I'll be making a tutorial in the next week or two on doing this with my Scheme for Max external. I can post here when I do. You could also join the youtube channel if you want to get notifications, it's called "Music With Lisp" on youtube. You could of course do this without my external too, but doing it in Scheme is very pleasant. As they say, "it's the kind of thing you'll like, if you like that kind of thing." ;-)

Hi Iain, all that to me sounds too complicated. 

I just want to trigger Live transport button without the need of OSC Bridge running in the background and I thought that the main purpose of M4L OSC TouchOSC device was that. But to me it seem you cannot map the transport buttons. Hope I'm wrong and somebody tells mi how.

Hi Iain, all that to me sounds too complicated. 
I just want to trigger Live transport button without the need of OSC Bridge running in the background and I thought that the main purpose of M4L OSC TouchOSC device was that. But to me it seem you cannot map the transport buttons. Hope I'm wrong and somebody tells mi how.
Thanks.
f.


Hi Iain, all that to me sounds too complicated. I just want to trigger Live transport buttons without the need of OSC Bridge running in the background and I thought that the main purpose of M4L OSC TouchOSC device was that. But to me it seems you cannot map the transport buttons. Hope I'm wrong and somebody tells me how. Thanks. f.

 Hi Iain, all that to me sounds too complicated.  I just want to trigger Live transport buttons without the need of OSC  Bridge running in the background and I thought that the main purpose of  M4L OSC TouchOSC device was that. But to me it seems you cannot map the  transport buttons. Hope I'm wrong and somebody tells me how. Thanks. f. 

Well, you can't just "map the transport buttons", because Live doesn't speak OSC the way it does midi. You need to make or use an M4L device that receives OSC and then uses the Live API. There are a bunch out there that you can use as starting points, and you might also find some that already do exactly what you want. But it's not a simple matter like the way midi mapping is in Live. Something has to parse the OSC message and then control Live.

When I read about the "Connection kit" I thought that the "OSC TouchOSC" device would have done just that: translate OSC messages into midi and/or Ableton commands. And it does it, but not for the transports and the clip launching. So to me it seems it's a limitation of the device itsef (but maybe it's the Live API).

The same goes with the M4L "OSC Send" device. You can map there the state of some buttons (track on/off, traack arm, etc.) but not the state of the transport and of the loop toggle.

Unfortunately I'm not a programmer so I have to rely on other's people work.

The same goes with the M4L "OSC Send" device. You can map there the state of some buttons (track on/off, traack  arm, etc.) but not the state of the transport and of the loop toggle.

Unfortunately I'm not a programmer so I have to rely on other's people work.
Thanks.
f.



In live, there's a difference between midi for playing stuff, and midi for Control Surfaces, as they call it. Control surfaces actually run in a different (lower priority) thread. You can make these in Max or in Python (which is what control surfaces from device manufacturers re written in). Either way, under the hood they use the Live API in it's thread, so I believe that's what's going on there - as far as I know, transport and clip launching has to be done that way.

In live, there's a difference between midi for playing stuff, and midi for Control Surfaces, as they call it. Control surfaces  actually run in a different (lower priority) thread. You can make these in Max or in Python (which is what control surfaces from device manufacturers re written in). Either way, under the hood they use the Live API in it's thread, so I believe that's what's going on there - as far as I know, transport and clip launching has to be done that way. 

But if I'm wrong, someone correct me! They do keep improving things... :-)

OSC: can I map M4L Touch OSC to transport or to launching clips?