Specific known problems with plug-ins========================Last Updated: 18 May 2010

Note that this list only features problem that we were able to verify. Please report to support@ableton.com if you find a problem with the latest version of Live and a plug-in which is not mentioned here. Please read carefully the instructions of Live and the plugin before reporting. For more general information about plug-ins, please check our FAQ here.

LennarDigital Sylenth1 crashes LiveFormat: VST Platform: Windows (reproduced on multiple Windows versions)Status: We're in contact with LennarDigital about the issue. There are reports that it is fixed in Sylenth1 v2.21 beta

Synthogy Ivory Live GUI doesn't work after closing the Ivory custom windowFormat: AUPlatform: MacStatus: We're working with Synthogy on the issue.

UVI Engine based plug-ins don't handle the transfer from one platform to another correctly. The preset gets lost when transfering a Live Song from PC to Mac or other way round. Format: VSTPlatform: Win & Mac

Access Virus TI- Freeze/render to disk doesn't work in all situations. - Play through latency is too high (AU only)Format: AU & VSTPlatform: Win & MacStatus: We are working with Accsss on the problems. There is no solution in the Audio Unit standard yet for the latency issue.

Native Instruments Reaktor 5 and other instruments can't input text.Format: VSTPlatform: PC Status: We are working with Native Instruments to find a solution.

IK Multimedia synths and effects random crashes.Format: AU & VSTPlatform: PC & MACStatus: We are not able to verify the problem. Please contact us, if you can reproduce this problem reliably and also contact the IK Multimedia support. Thanks.

Waves Several problems with Waves plug-ins crashing or misbehaving in versions prior to Waves 5.9.7.Format: AU & VSTPlatform: PC & MACStatus: Waves VST is compatible with Live 7 from version 5.9.7. Please update to the newest version.

iLok based plug-ins crash when iLok not inserted.Format: AU & VSTPlatform: PC & MACStatus: Because of the nature of the iLok copy protection, it's impossible to track the problem down. Please report to the plug-in developer and iLok developer.

Computer keys input doesn't work in some plugins on WindowsFormat: VSTPlatform: PCStatus: If the DebugOption "-_EnsureKeyMessagesForPlugins" is set in the Options.txt, we make sure that all key messages reach a plugin's window in front. That way, edit fields are again editable in the NI VST plug-ins. On the downside, key messages do not reach Live anymore as soon as some objects in the window of the VST plug-in are selected. Thus, for example, once an edit field has been edited, Live's playback cannot be started via Space until Live's main window regains focus.

FXpansion plugins don't work with configure modeFormat: VST/AUPlatform: PC/MacStatus: FXpansion doesn't send automation information at all. They plan to provide a correct VST/AU SDK support in later versions.

VST & AU Host Information==================

- Live 5.2 and later requires a VST 2.4 plug-in on Intel based Mac OS X machines as suggested by Steinberg, the creators of the VST standard.

- Live doesn't support Cocoa Views for Audio Units at the moment.

- It is essential for the plugins to correctly support parameter gestures (BeginEdit, EndEdit for VST) according to the plugin standards to let the configure modus work. If you find a plugin not working with configure mode in Live, please report to the plugin developer.

I just noticed that if you embed a vst plugin inside an instance of Kore2, it is possible to use the computer keyboard to type text into the plugin's gui (but still not into Kore2's gui, even though you can save performances onto you hdd with a user defined name which kind of relaxes the issue a bit).

I just noticed that if you embed a vst plugin inside an instance of Kore2, it is possible to use the computer keyboard to type text into the plugin's gui (but still not into Kore2's gui, even though you can save performances onto you hdd with a user defined name which kind of relaxes the issue a bit).

The options .txt workaround that Frank mentions works for all NI plugins as far as I know.