Broken Scripts

It’s a fact that generated Scripts may at times contain errors which prevent them from working. Control Surface Studio is extremely customisable while at the same time preventing you from creating broken scripts. However from time to time this can happen, so it's important that you understand why your script has stopped working and the steps you can take to fix it. Signs of a broken Script 1 The Script does not show as an option in Live's Control Surface Menu

MIDI Script not showing Ableton Live's Control Surface Options

2 The activation message does not show in the bottom of Live when the Script is activated.

Script Activation Message

3 Nothing happens when you press/move your MIDI Controller’s Inputs.

Script Activation Message

4 A red dot is displayed next to the Error Log in Control Surface Studio

Red dot displayed next to Error Log

Debugging your Script

If you are experiencing any of the above issues. Open the Error Log in Control Surface Studio to see the Remote Script Errors which Live has output. The errors read from bottom to top, the bottom being the latest error message and top the oldest. If the Error Log is also empty, ensure you have your settings configured correctly which we went through in the Configuration Step of this tutorial. If you have configured everything correctly but still not seeing Error Messages, you can manually check Live's log.txt file which you will find in one of these places: Mac OS X: /Users/[username]/Library/Preferences/Ableton/Live x.x.x/Log.txt

 Windows XP: \Documents and Settings\[username]\Application Data\Ableton\Live x.x.x\Preferences\Log.txt Windows Vista, Windows 7, Windows 8: \Users\[username]\AppData\Roaming\Ableton\Live x.x.x\Preferences\Log.txt Open the log.txt file in a Text Editor and search for 'RemoteScriptError'

Remote Script Errors in Log.txt file

Multiple lines can relate to the same error and can usually tell you the exact line in your Script which is causing the error. If the you have read through the errors and are not able to fix/understand what the error relates to, check the Forum for 'CSS Bug' posts which may be the same as what you're experiencing, post a new Topic if nothing similar exists. Or you can Contact Us directly.

Clearing your Error Log

Keeping your Error Log clear is important for a couple of reasons. 1 Old Error Messages still in your Error Log could confuse you when trying to debug your script. 2 Large log.txt files can slow Control Surface Studio down. To clear the Error Log, click the ‘Clear’ Button.

Clear Error Log button