Affilliate Links help support the site
Earlier today, we reported that Ableton had announced that it was halting new development on Live 8 so that its developers could focus on bug fixes.
Hot on the heels of that announcement, Ableton has released Live 8.1.1, an update that addresses a long list of bugs.
Here's what's fixed in 8.1.1:
- A very short MIDI note at the beginning of a clip would not be audible. 
- Recording via 'Resampling' would not properly compensate latency. 
- Under certain conditions, it would be possible to get 2 Arranger tracks highlighted. 
- Using the Launchpad as control surface and additionally for manual mappings would not always work properly.
- When installing Live Packs which have dependencies to other content, Live would show the corresponding message twice. 
- Using a Rex file could crash Live. 
- 'lock control surface' function would not properly work in user remote scripts. 
- A particular Live set could not be loaded and would lead to a 'Invalid Product ID Error' message. 
- In the Arranger, punch In/Out would delay notes by the 'punch in time' in beats. 
- Using the pads of the Akai MPD18 would not work properly.
- Having a Live set with particular Drum Racks could increase the CPU usage of the main thread, which would result in very slow graphical updates. 
- Installing a new Library from within a second running instance of Live could crash Live. 
- Certain operations like sample crop/reverse/replace would remove the tempo envelope. 
- Using Novation's Launchpad, when switching between Automap and Live control would not work properly.
- Under certain conditions, editing or creating parameter automation would not work properly. 
- Playing a 32-bit audio file immediately after a 16-bit audio file could cause a click in the audio. 
- Moving the last track out of a track group onto a closed group track in the Arranger could crash Live. 
- In the Auto Pan device, switching shape to random would not show the 'Width' knob. 
- Loading a Max device would crash if Pluggo was already active.
- It would not be possible to create a new Project in the File Browser if the root is set to 'Workspace'.
- Fine tuning of macro knobs would not work via key modifier. 
- Starting clips via the Launchpad while changing parameters via mouse could crash Live. 
- Moving the mouse over a certain Sampler preset could crash Live. 
- Loading a Live set containing not yet authorized add-ons could crash Live. 
- Under certain conditions, fade creation would not work properly. 
- An Ableton preset of a third party plug-in would not change the On/Off mapping range. 
- Receiving an invalid parameter index from Max could crash Live.
- Inverting a macro mapping range would not work properly. 
- Under certain conditions, extracting an existing groove from a clip would crash Live. 
- Having a Max device sending many blob changes during saving could crash Live.
- A malformed database file would interrupt user interactions like renaming files, saving presets, recording, etc. 
- Having a particular Live set loaded and searching for media files could crash Live. 
- On Mac OS X, under certain conditions, making Live the foreground window could lead to a crash.
- The context menu of a frozen clip would have enabled audio fades commands. 
- In the Arranger, changing the mixer properties like volume, pan etc. would not show the changed value in the status bar. 
- Having a multi selection of Arranger track and use the 'Show Automation' command would destroy the selection. 
- Choosing a custom VST directory within the preferences would not keep this new directory until the next start of Live if the required rescan leads to a crash. 
- On Mac OS X, duplicating a track with Fab Filter Twin 1+2 could crash Live. 
- The Looper display would use the wrong colour in 'play' mode. 
- Holding SHIFT + Space Bar would make the transport play button flicker. 
- The area to click on an Arranger clip would be too small by a few pixels. 
- Particular Live sets, especially with a lot of transient data, could not be loaded. 
- Pasting 3 unstretched and crossfaded Arranger clips could crash Live 
Kudos to Ableton for following through so quickly with the bug fixes.
More From: ABLETON
Even more news...