Changes from Live 8.1b9 to Live 8.1b10

[Alex]

Known issues:

- Documentation is currently only in English.

Please note that the Lessons, Reference Manual and Info Texts are also in beta. In addition to reporting bugs about the software, please report any documentation bugs (missing or incorrect feature explanations, typos, etc.)


Common Live changes from 8.1b9 to 8.1b10


Bugfixes

On Mac OS X, it would be possible to open the Preferences dialog during a modal progress bar dialog, which even could crash Live. [5587]

Splitting clips in arranger could lead to wrong playing.

When double-clicking a session clip while the clip is not visible, it was possible to accidentally move the clip to a different slot. [5974]

Editing pseudo-warp markers on long audio files could let the waveform display disappear. [5939]

Start playing a particular arranger clip from certain position would not actually play the clip. [6129]

Dropping a clip onto playing clip would not send the required feedback for control surfaces. [5859]

Clicking on a track or a scene could result in heavy MIDI feedback traffic for controller surfaces. [5975]

Copying clips from the arranger into the session so that new scenes must be created could crash Live. [6133]

Envelope loop changes would not always trigger the refreezing of a track. [6140]






Specific Max related changes from 8.1b9 to 8.1b10

Improvements

Max patches are not longer saved self-contained or frozen from within Live, as the corresponding behavior of previous betas was inconsistent and could still result in missing files. Therefore we decided to remove that functionality.


Bugfixes

Undo/redo issues for Max objects which state is saved in presets but not automatable would not work properly (like live.grid or storage-only live.dials).

Using Undo on the 'Reverse' parameter in the Note Operations Max device could rash Live.

On Mac OS X, mouse wheel handling on over a Max device would only work sometimes.

Max devices would crash Live under rare circumstances. [6125]

After the delete of an edited Max device, the edit button of another Max device of the same kind would stay disabled.




Changes from beta 8 to 89
http://forum.ableton.com/viewtopic.php?f=35&t=129220

Changes from beta 7 to 8
http://forum.ableton.com/viewtopic.php?f=35&t=128533

Changes from beta 6 to 7
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 5 to 6
http://forum.ableton.com/viewtopic.php?f=35&t=127311

Changes from beta 4 to 5
http://forum.ableton.com/viewtopic.php?f=35&t=126139

Changes from beta 3 to 4
http://forum.ableton.com/viewtopic.php?f=35&t=125366

[hoffman2k]

Undo/redo issues for Max objects which state is saved in presets but not automatable would not work properly (like live.grid or storage-only live.dials)

Does this include live.remote~?

[hoffman2k]

Undo/redo issues for Max objects which state is saved in presets but not automatable would not work properly (like live.grid or storage-only live.dials)

Does this include live.remote~?

Ooh Awesome. It does
I may have to travel with a pallet of beer next time to cover all you guys. I think I owe Ralf many beers now.

You guys rock!

- Bjorn

[Surreal]

Known issues:

Specific Max related changes from 8.1b9 to 8.1b10

Improvements

Max patches are not longer saved self-contained or frozen from within Live, as the corresponding behavior of previous betas was inconsistent and could still result in missing files. Therefore we decided to remove that functionality.

So, how do we build collectives for M4l?

it wants to save it as mxf.

[cassiel.com]

So, how do we build collectives for M4l?

Use the Freeze button inside Max itself, presumably.