Ableton Forum

Hi folks,

The first public beta for the upcoming 7.0.3 bug fix update is available now.

The current beta, Live 7.03b3, is free for every Live 7 customer and will expire on the 14th March.

http://www.ableton.com/_common/download ... 3b3_en.zip
http://www.ableton.com/_common/download ... 3b3_en.dmg

Please send your beta related feedback to [email protected] or use the Bugs and Problems section of the forum.

Please keep in mind that it is helpful to know if a certain bug or problem you run into already exists in Live 7.0.2.


Kind Regards
/Alex



Changes from Live 7.0.2 to Live 7.0.3b1


Improvements

Updated several texts.

Updated English manual.

Added control surface support for the Akai MPD24. The volumes of tracks 1 to 6 are mapped to the faders. The encoders are mapped to macro controls.
The order of the mapping is based on the feedback of this forum poll: http://www.ableton.com/forum/viewtopic.php?t=82431

Support for dynamic adjustment of the plug-in buffer size for Audio Units. For technical reasons, an Audio Unit device must be instantiated for a buffer size change.

Improvements for dialog to set up a Library when starting Live without one.

On Mac OS X, Live now supports up to 256 input & output mono channels of the selected audio device.



Bug fixes

Under certain conditions, the chooser for the Library path would not update properly.

The message box saying that the selected Library is not available would not be displayed properly.

When Live is running as the MIDI clock master, the first two sent MIDI clock messages could have the same time stamp. A Options.txt entry called ”-_Live6ClockOutputCompatibility” brings back the old behavior if required.

Analog instrument with unison enabled would always use CPU power even if it was not used.

Dropping an instrument on a pad or chain that has devices would not replace the chain.

Quitting Live because the expiration date was reached would lead to a crash on Mac OS X 10.5.x.

Deleting a track with a Rack in Mappping mode would crash Live.

Switching Sampler or Simpler presets during playback could lead to a short but heavy audio signal distortion.
http://www.ableton.com/forum/viewtopic.php?t=83014

When using more than 8 return tracks, the return track volume mixing would not work properly.

Under certain conditions, a song loop back jump could lead to a hard disk overload.

Starting up Live with a corrupt header template document would lead to a crash.

When using particular audio files, Live could crash for certain warp actions.

In the inline mixer, resizing a chain would resize all other chains too.

When scrubbing behind the loop within a clip, looping would not work properly after the next song start / stop.

On Windows, when loading a Rack that contains an AudioUnit (which is disabled on PC), Live would crash when opening or closing Rack chains, or when turning one of the other rack marbles on or off.

Installing a content package update could result in an imprecise success message.

Okay,MPD 24!
Faders and macros working fine but
how about the transport control?

Yes PLEASE !! As i already said it in this forum :

http://www.ableton.com/forum/viewtopic. ... 297#655297

It would be so so nice !! Have you checked it on Reason 4 ? It's so usefull... So what's the problem with MMC messages ??
Big thanks if it's possible...
Cheers !

I'm running XP SP2. This bug happens both in 7.0.2 and 7.0.3b3.

I get the message that any ALAC .m4a file "could not be read. It may be corrupt or not licensed." when I attempt to preview it in the browser. When I attempt to drag a clip into session or arrangement view, I get the error "The file XXXX could not be decoded using Quicktime (error code -50)."

logman wrote:I'm running XP SP2. This bug happens both in 7.0.2 and 7.0.3b3.

I get the message that any ALAC .m4a file "could not be read. It may be corrupt or not licensed." when I attempt to preview it in the browser. When I attempt to drag a clip into session or arrangement view, I get the error "The file XXXX could not be decoded using Quicktime (error code -50)."

i think this is a Quicktime 7.4.1 error because I am getting this on my MacBookPro with ALAC files in Live 7.0.2 when they worked fine with the 7.4 version of QT.

something in the update forced me to change my midi offset delay settings....weird

evilxsystems wrote:something in the update forced me to change my midi offset delay settings....weird

By what amount, less delay or more? Maybe they optimized something for better Midi performance, or maybe they worsened something about Midi for better overal performance.

tricil wrote:

logman wrote:I'm running XP SP2. This bug happens both in 7.0.2 and 7.0.3b3.

I get the message that any ALAC .m4a file "could not be read. It may be corrupt or not licensed." when I attempt to preview it in the browser. When I attempt to drag a clip into session or arrangement view, I get the error "The file XXXX could not be decoded using Quicktime (error code -50)."

i think this is a Quicktime 7.4.1 error because I am getting this on my MacBookPro with ALAC files in Live 7.0.2 when they worked fine with the 7.4 version of QT.

That problem started with QT 7.4 - Live is unable to convert from ALAC to WAV. If it wasn't happening for you with 7.4 its likely the tracks were already stored in the Live cache in WAV format so didn't need converting.

Ableton are aware of the problem but are blaming QT. Though personally I'm not convinced - I use other applications which rely on QT for coded conversions (Mixed In Key for example) which are still working. Whilst QT 7.4 has got compatibility issues I haven't read of any regarding audio only (they are all video related).

I worked by going back to the previous version of QT, then loading all my tracks to get them in to the Live cache in WAV format and then going back to the latest version of QT. It works provided you've got enough disk space.

tricil wrote:

logman wrote:I'm running XP SP2. This bug happens both in 7.0.2 and 7.0.3b3.

I get the message that any ALAC .m4a file "could not be read. It may be corrupt or not licensed." when I attempt to preview it in the browser. When I attempt to drag a clip into session or arrangement view, I get the error "The file XXXX could not be decoded using Quicktime (error code -50)."

i think this is a Quicktime 7.4.1 error because I am getting this on my MacBookPro with ALAC files in Live 7.0.2 when they worked fine with the 7.4 version of QT.

Looks like this has been fixed with the latest update to QuickTime - well, its working ok for me at least. Plus the release notes said there were more compatibility fixes.