Ableton Forum

Yes, it definitely can.

https://www.youtube.com/watch?feature=p ... 6HCdhdPREI

My bandmate and I are putting out an EP of around 10-12 ringtones in the near future, to be called Not Much, For Not Very Long, Again & Again & Again . We put up 6 of them on our Soundcloud.

http://soundcloud.com/liesandmurders/sets/ringtone-teaser

All of these are completely original. The contain ...

My guess: when you map a control on the apc40, ableton tries to send midi feedback for that control, which sends on the same channel as the controller, out of all midi interfaces which have remote output enabled. Is remote enabled in the midi prefs for whichever interface the Mopho is hooked up to ...

Actually it depends on if the device you are trying to reach is a max device or an ableton device.

Max devices can get their own id by sending "path this_device" to a live.path and then broadcast this over send/receive, which can then be used by other devices.

What's so aggravating about the ...

this is pretty easy to do with M4L, and I don't know of any way to do it without M4L.

No midi device will accept floating point note values, actually. The MIDI standard just doesn't allow anything but an integer in the range 0-127.

You're right. I'm not exactly sure why I thought they didn't.

Loadbang not functioning seems like a bug to me. Loadbangs won't send when you move a device around (re-ordering or moving to a different track) or when a live set opens, but definitely should send when you drag in a new instance.

ID numbers are not ordered in a sensible way - they're actually assigned in the order the API needs them (as far as I can tell).

What you want to do is send "path this_device" to a live.path, input that ID number into a live.object, then send "getpath" to that live.object. This will give you the ...

To sum up: to receive information about a set's tempo, use the transport object; to change that tempo, use the Live API. Have I got this correct?

It is not possible, currently, to use live.path to address devices in racks - the only parameters available to the live api are the 8 macro knobs. This is a limitation of the live object model and one that I think is a serious oversight by cycling/ableton.

It is however possible to use live.remote ...

http://www.cycling74.com/docs/max5/refpages/m4l-ref/m4l_live_object_model.html is the relevant documentation. It is also available on your hard drive under Help > Max For Live <click> Live Object Model. It is not, however, strictly complete, especially as regards the control surfaces section, and ...

open up the device, open the freeze button's inspector. go to the parameter tab and next to "Parameter visibility" select "Automated and Stored" rather than "Hidden".

Save the device and close it. freeze should be mappable now.

Yes they work just fine, I use several externals regularly.

However it should be said that none of those apps have the power of the lemur, really. The Lemur has more UI objects to play with (multiball, range, etc.) and most importantly, has the ability to control objects with other objects, i.e. to let, say, a slider control the physics parameters of a ...