Ableton Forum

These aren't officially out in the wild yet, so keep your hat down, but here are a few sneak peek videos featuring some of the new Max For Live API features that will be in Live 8.2.2 and Max 5.1.8! Check 'em out:

*** Selected Params
http://www.youtube.com/watch?v=z3IG17LfiG4

*** Persistent IDs
http://www.youtube.com/watch?v=u3ooZgNmDog

*** live.thisdevice
http://www.youtube.com/watch?v=FNPL7wgtizI

For all you "early adopters," thanks for checking out the beta!

-Ben

benbracken wrote:*** Persistent IDs
http://www.youtube.com/watch?v=u3ooZgNmDog

Hey Ben,

The last line of this video is incorrect. While ID's are set local, if they're stored inside the live.xxx objects, they will also work in Live presets and Live Clips.
This is some magic you guys added in the latest betas.

You can for example create a Rack with a MFL device that is mapped to several things in that Rack.
You can then load as many instances of that Rack as you want and there won't be any mapping conflicts. If the ID already exists, a new ID is created. But it doesn't actually lose the path/ID that was stored. It just magically replaces it.

Ben this is stealer stuff, just at the point of releasing a new device i've been able to streamline the entire start up process, get rid of complicated delays and pattrs that are now unnecessary!

Thank you so much!

Cheers
D

Hi Hoffman,

You are correct with regards to mappings within Rack presets - they will be persistent across sets. This is an (albeit important) exception that we didn't mention in this video. In general, persistence of IDs are Set specific.

For example, if you create a preset, and then place it in another set, it will *not* retain its ID mapping. Please let us know if you find otherwise.

Thanks for pointing it out,
-Ben

hoffman2k wrote:

benbracken wrote:*** Persistent IDs
http://www.youtube.com/watch?v=u3ooZgNmDog

Hey Ben,

The last line of this video is incorrect. While ID's are set local, if they're stored inside the live.xxx objects, they will also work in Live presets and Live Clips.
This is some magic you guys added in the latest betas.

You can for example create a Rack with a MFL device that is mapped to several things in that Rack.
You can then load as many instances of that Rack as you want and there won't be any mapping conflicts. If the ID already exists, a new ID is created. But it doesn't actually lose the path/ID that was stored. It just magically replaces it.

I hope I didn't offend you there. It just sounded wrong to hear you can't save these mappings with devices. Especially after you guys went through the trouble of solving the massive mind-bender of being able to deal with paths in Rack Presets.

No offense taken! Its a great feature, and an important distinction to make. But, again, to clarify, you cannot save mappings with regular presets, they get saved with the set. Rack presets are a special case - they are a little different than a normal preset file.

-Ben