New Max for Live Updates Released Live 8.2.2 and Max 5.1.8 have now been released. This update includes major enhancements that many Max for Live users have been begging for. Devices inside Racks can now be accessed via the Max for Live API!!!!
Full details available from Ableton.com here: http://www.ableton.com/latest-release-notes
Some of these changes may introduce bugs with existing devices in the Library so please make sure you note in the device details which version of both Live and Max are required for your device.
From Ableton.com:
(*) Devices inside Racks can now be accessed via the Max for Live API
(*) Return tracks can now be observed via the Max for Live API
(*) Live devices and parameters can now be much more easily mapped to controls in Max devices. Devices can safely be moved within a Live Set without breaking any existing mappings. Also, devices and Sets can be saved and loaded without breaking existing mappings. The following changes make this possible:
(*) There is now a simple way to observe the selected parameter via the Max for Live API, using "live.path live_set view selected_parameter." This can be used, for example, to build a custom "map mode" to quickly map parameters in your Live Set to controls in a Max device.
(*) Live objects like tracks, clips or parameters retain their identity (id nn) during operations like move, save/restore, cut/paste, delete/undo, the identity is global and can be communicated via Maxs Send and Receive objects.
(*) live.object, live.observer and live.remote~ are now able to remember their target objects when Live sets or presets are saved and restored or when objects are moved within the Live set.
(*) Ableton protected samples can now be used in Max for Live device, via the Live.drop object fixed a bug where clip slots would lose their id on moving a clip
fixed navigating and observing control surfaces via the LiveAPI
(*) Repeatedly calling "goto control_surfaces" on a live.path object was producing a different id each time
(*) Fixed a crash that occurred when deleting a Rack containing a Max for Live device, where a Remote~ was controlling one of the Macro knobs, and then
Undoing the delete action
(*) Navigating the Live Object Model is about two times faster
Fixed a crash that occurred when moving tracks that contained automated Max for Live devices
(*) Fixed a crash that occurred when replacing one Max for Live device with another if certain modulations existed
(*) If a native Ableton device has parameters that are mapped to a Max for Live device, the mappings will be preserved after hot-swapping the Ableton device
(*) The Track/Chain Activator and Song Tempo are now accessible via the "selected_parameter" property and their path can be queried "live_app" and "live_app view" can now be persistent in the Max for Live API
(*) Mapping some mixer component on the APC40 (for example) through the Max for Live API wouldnt work without pressing the Pan or Send button on the APC40, which reset the component. This has been fixed.
(*) "goto live_set tracks 2 devices" in a set with one track produced id -1, which is wrong. Now it produces id 0.
(*) If the LOM id of the observer is persistent, the property of an observed LOM object is persistent, even if it is dynamically changed using a message.
(*) Max for Live devices that control the Application objects (e.g. live_app (live_app view)) or which get information about the Live version and document name (e.g. get_major_version (focus_view)) will work when loading the Set, without requiring user interaction.
