While we are far from perfect, over the course of development we have become expects at not just creating CsoundForLive plugins, but in finding brand new ways to break them.

As far as the release version goes, 95% of the problems our Beta Testers have encountered have been solved by one of these ways:

1. Reinstalling all of the required programs:

In most cases only Csound and CsoundForLive needed to be reinstalled, but in certain situations reinstalling Ableton Live and Max For Live cleared things up.

2. Updating all of the software to our reccomended versions.

As of release that means Ableton Live v8.2.2 and Csound v5.13. This is hugely important and especially in the case of the Live update, several Max For Live bugs were corrected that impacted the performance of our software.

3. Searching our CSD Update Archive for fixes.

'Under the hood' of every CsoundForLive plugin is a CSD (Csound Document) running the show. Should any performance bugs come to light, they will almost always be able to be corrected by tweaking this document - and we have created the CSD Update Archive to provide an immediately accessible fix for these cases.

While this is may be an inelegant solution, it is far easier than having all users reinstall a portion of their software and is the quickest way to get solutions straight from the developer to you. Simply click on the "CS" icon in our control panel to open the CSD, and paste in the corrected code.

If reinstalling and updating your software and scouring the archive haven't yeilded results, send us a message at:

support@csoundforlive.com

And be sure to include the following:

Your operating system and version number.

Which versions of Csound and Ableton Live you are using.

If you have a full version of Max/MSP installed, which version.

The plugin were you using when you experienced the crash.

Specfic details about what was being attempted (i.e. Automation, internal patch exploration, etc.) when the session failed.

Any other plugins, Cs4L or otherwise, that were also active when the crash occurred.

Please be understanding that we will do our absolute best to get back with you regarding your problem as soon as we possibly can - although it may take us a bit of time.