- #32 lives ableton crashes mac os
- #32 lives ableton crashes update
- #32 lives ableton crashes manual
The Looper display would use the wrong colour in ‘play’ mode.
#32 lives ableton crashes mac os
On Mac OS X, duplicating a track with Fab Filter Twin 1+2 could crash Live. 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. Having a multi selection of Arranger track and use the ‘Show Automation’ command would destroy the selection. would not show the changed value in the status bar. In the Arranger, changing the mixer properties like volume, pan etc. The context menu of a frozen clip would have enabled audio fades commands. On Mac OS X, under certain conditions, making Live the foreground window could lead to a crash. Having a particular Live set loaded and searching for media files could crash Live. A malformed database file would interrupt user interactions like renaming files, saving presets, recording, etc. Having a Max device sending many blob changes during saving could crash Live. Under certain conditions, extracting an existing groove from a clip would crash Live. Inverting a macro mapping range would not work properly. Receiving an invalid parameter index from Max could crash Live. An Ableton preset of a third party plug-in would not change the On/Off mapping range. Under certain conditions, fade creation would not work properly. Loading a Live set containing not yet authorized add-ons could crash Live. Moving the mouse over a certain Sampler preset could crash Live. Starting clips via the Launchpad while changing parameters via mouse could crash Live. Fine tuning of macro knobs would not work via key modifier. It would not be possible to create a new Project in the File Browser if the root is set to ‘Workspace’. Loading a Max device would crash if Pluggo was already active. In the Auto Pan device, switching shape to random would not show the ‘Width’ knob. Moving the last track out of a track group onto a closed group track in the Arranger could crash Live. Playing a 32-bit audio file immediately after a 16-bit audio file could cause a click in the audio. Under certain conditions, editing or creating parameter automation would not work properly. Using Novation’s Launchpad, when switching between Automap and Live control would not work properly. Certain operations like sample crop/reverse/replace would remove the tempo envelope. Installing a new Library from within a second running instance of Live could crash Live. 
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. Using the pads of the Akai MPD18 would not work properly. In the Arranger, punch In/Out would delay notes by the ‘punch in time’ in beats. A particular Live set could not be loaded and would lead to a ‘Invalid Product ID Error’ message. ‘lock control surface’ function would not properly work in user remote scripts. When installing Live Packs which have dependencies to other content, Live would show the corresponding message twice. #32 lives ableton crashes manual
Using the Launchpad as control surface and additionally for manual mappings would not always work properly.Under certain conditions, it would be possible to get 2 Arranger tracks highlighted.Recording via ‘Resampling’ would not properly compensate latency.A very short MIDI note at the beginning of a clip would not be audible.
#32 lives ableton crashes update
Ableton has followed up on yesterday’s announcement that it was refocusing its development on bug fixes with the release of Live 8.1.1, an update that addresses over 40 bugs.
0 kommentar(er)
