How to fix a broken midi remote script

by John Carney last updated Aug 03, 2017

It can be extremely frustrating if you create a script and it doesn't work.
So it's important to know how you can figure out what the problem is and fix it.

Here's some things you can quickly check:

The first thing you should be aware of is assigning multiple mappings to the same midi control will brake the script.

Check that you haven't done this, you can filter the mapping list in Remotify to specific cc values in order to make this process quicker.

filtering midi mappings

Although we've now put checks in place to prevent you making this mistake, older scripts could be suffering from this problem.

Note:
Midi controls on separate midi channels are fine.
Controls set to different 'modes' are also ok.

Have you duplicated the script folder?

It's important that the script folder has the exact same name as the script files contained within it.
Before you unzip your folder, make sure you don't already have a folder with the same name in the place you're unzipping to.
If you do it will rename the newly unzipped script folder by adding a number to the end.

renamed midi remote script

Is it a problem with the script or something else?

When you select a Remotify script in the midi preferences menu of Ableton, you'll see a message appear at the bottom of the Ableton application which includes the words 'script made in remotify'.
If you don't see this message then that indicates there's a problem with the initialisation of the script.
If you do see this message and Ableton is responding to your controls, this suggests that the problem lays elsewhere (possibly with your midi controller or Ableton configuration).

connection message

Debugging using the log.txt file (advanced):

If you're still having problems with your script, you can see if any error messages are being output to the log.txt file.

You’ll find the log.txt file here (based on your operating system)

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

Mac OS X
/Users/[username]/Library/Preferences/Ableton/Live x.x.x/Log.txt

Open it in a text editor,
1. First I’d recommend you close the Ableton application and delete the contents of the log.txt file and hit save. This will ensure you're not seeing old errors which may not be related to your current setup.
2. Open Ableton again, activate your midi remote script then do a search for 'script error’ in the log.txt file. if one of your remote scripts is causing an error it will be output in here.
3. If there’s an error then you’ll usually see multiple lines relating to the same issue. The name of the the script which is causing an error will be detailed on on of these lines. It will also name related Ableton framework files which are affected, don't be fooled into thinking the error is in one of these as framework files usually don't have errors.

If you're still stuck, feel free to contact us with your findings and we'll do our best to help you resolve it.

Create your own perfect Midi Controller integration for Ableton

Become a Pro Now