Ableton Remote Scri...

[Sticky] Ableton Remote Scripts  


Joined: 2 years ago
Posts: 357
13/11/2018 10:09 pm  

The script requires Live 9.6 or later.

Unzip the file in Live’s MIDI Remote Scripts directory. Please close Live before transferring this folder.

On Windows, Live’s MIDI Remote Scripts directory is in one of the following locations:
Windows: C:\Users\[Username]\AppData\Roaming\Ableton\Live x.x.x\MIDI Remote Scripts\

On OS X, to get to Live’s MIDI Remote Scripts directory:
Go to Applications, find or Ableton Live, right-click and select Show Package Contents. The directory is located at:
Contents/App-Resources/MIDI Remote Scripts
Chameleon run on Windows, but you can send MIDI from Chameleon running on a Windows touchscreen/tablet trough WiFi and or wired network.

If the simple process of install is performed correctly you see a red container of 4x4 clips.
You can change at any time based on what you need.


The following settings will be found in Preferences on the MIDI/Sync tab.

Select Chameleon as a Control Surface.
Set the Control Surface’s Input and Output to the desired MIDI ports.

The script’s functionality does not require turning on any switches under MIDI ports. However, if you’d like to be able to use MIDI mapping in Live, you will need to turn on the Remote switches for the MIDI ports selected above. If these switches are turned on, this will open up the possibility for conflicts with mappings created by other controllers.

This is due to the way Live’s MIDI mapping works; it’s based purely on MIDI messages and MIDI mapping overrides Control Surface mapping. To avoid such conflicts, other controllers shouldn’t use any of the MIDI messages this script uses for MIDI mapping.

The Chameleon folder contains a file named UserPreferences.txt that has some easily modifiable variables that you may want/need to change (such as the number of Tracks and Scenes the script provides). After making changes to this file, you will need to restart Live in order for the changes to take effect.

The script supports a variable number of Tracks (1 to 8) and Scenes (1 to 8), which can be set via the Script Variables. The MIDI messages that are used are the same regardless of the Track and Scene count.

Clip grid with 4 Tracks and 4 Scenes, the CC numbers you’d use for launching Clips would look like so:

If want build 8x8  grid the first row will be  0 - 1 - 2 - 3 - 4 - 5 - 6 - 7 


The Track EQ functions will apply to the first EQ3 or EQ8 Device on a Track or within a Rack on the Track.

By default, the Track Solo and Arm functions will obey the user’s preference setting for Exclusive Arm and Solo. When Shift is pressed, the Track Solo and Arm functions will do the opposite of the user’s preference setting.



The Device functions apply to the Device selected on a Track (denoted by a hand icon on the Device’s title bar).

By default:
The Clip Slot functions will launch Clips.
The Scene Launch functions will launch Scenes.
The Clip Grid Bank functions will move the Clip Grid by increments of 1.

When Shift is pressed:
The Clip Slot functions will select Grids of Clips.
The Scene Launch functions will move between Banks of Grids.
The Clip Grid Bank functions will move the Clip Grid by increments of the Clip Grid’s width and height.


These values can be changed via the Script Variables.
Chameleon provide Ready to use Ableton Live Clip


The Clip Loop functions all apply to the Clip that is selected.

By default, the Clip Loop Dec/Inc functions will adjust the Clip’s Loop in increments of 1 beat. When Shift is pressed, the increment will be 1/16th of a beat. Also, these apply to the Clip’s Loop when Loop is turned on. When Loop is off, these will apply to the Clip’s Start and End.

By default, the Tempo Encoder function will adjust the Tempo in 1-BPM increments. When Shift is pressed, the increment will be 1/10th of 1-BPM. In both cases, the maximum Tempo that can be set is 999.0 BPM. This can be changed via the Script Variables.

You can set the resolution used for the Clip Loop Dec/Inc and Tempo Encoder via the Script Variables.



Each time the script is initialized, it will write some lines into Live’s Log.txt file. These lines all start with SM LOG ------- and contain info on the version of the script, version of Live and info about Script Variables that were read. The Log.txt file will also contain info on MIDI settings and errors that occur in the script. This is all very useful for troubleshooting.

On OS X, you’ll find Log.txt in (if you’re using OS X Lion or beyond and need help locating your Library folder, please see this article:
Users\(your name)\Library\Preferences\Ableton\Live x.x.x

On Windows, you’ll need to ensure Hidden Files/Folders are shown as Log.txt is in a hidden folder.
You’ll find Log.txt either in:
Documents and Settings\(your name)\Application Data\Ableton\Live x.x.x\Preferences
Or: Users\(your name)\AppData\Roaming\Ableton\Live x.x.x\Preferences

Feel free to change, improve and share, the scripts include the source code, and are compiled in automatic way when run Ableton.
.py files  are the source code files.



This topic was modified 11 months ago by SaveTheHuman5

Facebook, Twitter, Instagram: @SaveTheHuman5


Please Login or Register