Ableton Forum

recently some of the basic concepts of the Live API clicked for me. stuff I wish someone would've sat down and shown me months ago. the LOM now makes sense to me and I can finally make use of live.path, live.object, live.remote etc without using other peoples' code.

I wish I could sit down with the myself from 3 months ago, maybe I can do that for someone else. I'm talking basics, I can't help with more advanced stuff.

likewise if anyone has any good resources for BASIC Live API, that could help too.

given the steep learning curve of all this I'd like to keep this to really basic stuff.

I'm normally lost looking at the documentation. I have to look at other peoples examples that are close to what i'm doing and copy them.

If you had a revelation on the basics you should share it!!

I'm very much waiting myself from 3 months in the future to come have a friendly chat with me about the API, LOM and ETC ... Would _love_ that actually ... I'd be sure to makes us hot cup o choco and buy some cinnamon rolls!

What's wrong with the LOM for you guys?

For me it was working out which of the objects to use....

live.object = to get a value once or make a value change once, eg is a clip looping or not? Fire a clip.....

live.observer = slow response time if many in a device but you can make gradual changes to a control without much impact on cpu, think of this as using on a eq basis whereby gradual changes are required rather than swift ones. The advantage of using this object is that it doesn't disable the control it's pointed at from being modulated by other methods for example through a midi mapping.

live.remote = disables the control so you lose the ability to midi map the control it's pointing at. However massive advantage in that it's update rate is as real time as you can get....

That's me 2p's worth....
Cheers
D

bulo wrote:What's wrong with the LOM for you guys?

explain the various functions and when to use them.

explain the 3 outputs of live.path.

why can I exercise a live.object with a live.path id output but when I tie a message box with "id 1" to live.object's path id it doesn't work until after I use a live.path object to find the path for id 1?

oops

Where I am lost is in what can be done with the components returned by M4L.apl.SelectComponent from the ControlSurface object (I am using the Launchpad.) I've googled around but come up with nothing on this topic.

bobseekone wrote:Where I am lost is in what can be done with the components returned by M4L.apl.SelectComponent from the ControlSurface object (I am using the Launchpad.) I've googled around but come up with nothing on this topic.

yep.

where can you find the path, parameters and functions that work with the Launch Pad?

I know some of this is because the documentation isn't done yet and all that is on hold due to the 'Quality' statement, but until then, whassssup??

It does seem to be a case of routing around for forum posts from intrepid explorers. Let's hope some official documentation appears soon.

Personally I'm looking for a solution to controlling the LED rings around the knobs on the APC40 for disconnected parameters. I'm sure there must be a way, just damned if I can find it.

Tone Deft wrote:

bobseekone wrote:Where I am lost is in what can be done with the components returned by M4L.apl.SelectComponent from the ControlSurface object (I am using the Launchpad.) I've googled around but come up with nothing on this topic.

yep.

where can you find the path, parameters and functions that work with the Launch Pad?

I know some of this is because the documentation isn't done yet and all that is on hold due to the 'Quality' statement, but until then, whassssup??

For this you need the Live.api.explorer device....

When you navigate to the control surfaces it tells you what is attached, what the paths are and what functions can be called, it won't tell you what to do with them or what messages to send but half the job is done then....

Cheers
D

@s4racen

you lost me with live.observer.....isn't that a notification object to notified of changes ? how would you change values with it ?

especially as changing values upon getting notifications is not allowed in M4L.

monohusche wrote:@s4racen

you lost me with live.observer.....isn't that a notification object to notified of changes ? how would you change values with it ?

especially as changing values upon getting notifications is not allowed in M4L.

http://www.cycling74.com/docs/max5/refp ... erver.html

"After an object id and property is specified, its value is sent out the left outlet. From this moment on, the value is sent on each change of the property ('notification') as well as in response to bang messages... Also, it is not possible to modify the live set from a notification, i.e. while you are receiving a value message spontaneously sent by a live.observer 's outlet. "

maybe you can't do it from the same object. one to get, one to set.

as I said, live.observer can't be used to set values

From this moment on, the value is sent on each change of the property

1. navigate the LOM
2. set the id
3. specify the property to be observed
4. live.observer reports the current value once
5. from now on, live.observer reports the value whenever there is a change (e.g. by other means such as MIDI controller or mouse)


live.observer doesn't support a "set" message.

monohusche wrote:@s4racen

you lost me with live.observer.....isn't that a notification object to notified of changes ? how would you change values with it ?

especially as changing values upon getting notifications is not allowed in M4L.

Good point well made, i used to watch a control with an observer and change it with a live.object, quite glitchy and lags at times but you can still midi control the original control....

Cheers
D