Frequently asked questions

To uninstall the remote script, navigate to Live's MIDI Remote Scripts folder and delete the folders named Tweaker and TweakerNav.

Windows

Ableton Live 9's default installation location is the ProgramData folder on the C: drive (C:\ProgramData). This folder is hidden by default, so you may need to set Windows to show hidden files and folders.

1. Go to ProgramData › Ableton › Live 9 › Resources › MIDI Remote Scripts
2. Scroll down to the Tweaker and TweakerNav folders, then select and delete them.

macOS

Ableton Live 9's default installation location is the Applications folder.

1. Find Ableton Live 9 in Applications, right-click the icon and choose Show Package Contents.
2. Go to Contents › App-Resources › MIDI Remote Scripts
3. Scroll down to the Tweaker and TweakerNav folders, then select and delete them.

Link to this answer

If you hit a "disk is damaged" error while installing the Ableton Live remote script, you need to change your Gatekeeper settings or allow the installation manually.

Gatekeeper prevents the installation of unsigned or unknown applications on macOS. You will find its options under:

Apple menu › System Settings › Privacy & Security — look under the heading for allowing applications downloaded from identified developers. On older releases of OS X this lived at Apple menu › System Preferences › Security & Privacy › General.

A quicker route that avoids changing the system-wide setting: right-click (or Control-click) the installer and choose Open, then confirm at the prompt.

Apple documents the behaviour at support.apple.com/en-us/HT202491.

Link to this answer

For Ableton Live's Drum Rack to respond to the Tweaker:

• Set MIDI From on the Drum Rack's host MIDI track to Tweaker (Port 1).
• Set the MIDI channel to All Channels or Channel 10.
• Arm the track for recording so that MIDI input triggers the Drum Rack pads.

Note: Track Input must be enabled for the Tweaker's In port in Live's MIDI preferences.

Link to this answer

Ableton has occasionally made changes that break third-party remote scripts in software updates, so there are several versions of the Tweaker remote script for different versions of Live. Make sure you install the correct script for your version — especially if you have more than one Live installation on the same computer.

All four versions remain available on the downloads page.

Link to this answer

Before you start: the Tweaker remote script must already be installed. Download it from the downloads page and check the version compatibility table.

For Live to respond to the Tweaker's commands it must be set up as a control surface in Live's MIDI preferences. Once the remote script is installed it becomes available in Live's control surface chooser.

1. Open Live's Preferences window and select the MIDI/Sync tab.
2. Select Tweaker from the first control surface chooser.
3. Select TweakerNav from the second control surface chooser.
4. Set the inputs and outputs for both control surfaces to Tweaker (Port 1).
5. Make sure Track and Remote are both switched on for Tweaker (Port 1) in the MIDI Ports list.

Link to this answer

Three mappings are available from Electrix: Decks A/B, Remix Decks C/D, and Track Preparation. All three are on the downloads page.

1. Download

Save the .tsi into Traktor's settings folder. Right-click the mapping file, choose Save target as, and navigate to:

Home › Documents › Native Instruments › Traktor 2.x.x › Settings

2. Install

1. Launch Traktor, open Preferences, and click the Controller Manager tab.
2. Under Device Setup, click Add and choose Import TSI › Import Other.
3. Navigate to Traktor's settings folder and select the TSI file you want to install.

3. Set the ports

Ports represent the physical connections on your hardware. Setting them tells Traktor where to send and receive MIDI. Multiple mappings assigned to the same ports will make the hardware behave erratically, because it receives conflicting messages.

• Under the In Port and Out Port pull-down menus, set the mapping you are using to Tweaker Port 1 — that is the USB port.
• Only one Tweaker mapping can be active at a time. Set every other Tweaker mapping to None.

Link to this answer

The Tweaker Editor includes several tools for testing your MIDI and hardware settings, covering both MIDI input and MIDI output. To open the Tools window, click the Tools button in the lower right-hand corner of the Tweaker Editor window.

Testing MIDI input

The View MIDI Input tool shows messages sent by the Tweaker. With the window open, move any control on the hardware and watch the incoming messages appear in real time.

Set the correct port from the pull-down menu. The default is Tweaker Port 1, which is the USB port on the Tweaker. If you are using the MIDI connections, or you have more than one Tweaker connected, change this value.

Testing MIDI output and LEDs

The MIDI Output Tools let you send messages to the Tweaker. This is most commonly used to test the LEDs.

Try this: under Send Many Notes, change the interval to 100 (the default is 1000), press Go, and watch the LEDs trigger across the Tweaker. You have just sent note-on and note-off messages to every control sequentially. The min value is the first note and the max value is the last note in the range — note 0 is the first button in the grid, and note 70 is the last drum pad. The interval controls how quickly each note fires.

You will notice the LED rings do not respond to Send Many Notes. The rings are driven by control change (CC) messages rather than note messages, so use the Send CC Ramps tool to test them instead.

Link to this answer

The Tweaker is a highly customizable control surface — which also means it is easy to get into a strange state. If your Tweaker is behaving oddly, or factory mappings are not responding correctly, reset it to factory settings using the Tweaker Editor.

Before you reset: save your current settings as a preset so you can recall them later. The Tweaker Editor Reference Manual covers saving presets.

1. Press the RESET TO DEFAULTS button at the bottom of the Tweaker Editor control panel. You will be asked to confirm before the change is committed.
2. Press SAVE TO TWEAKER to write the default settings back into the Tweaker's on-board memory.

Link to this answer

The following is the Tweaker's factory default MIDI note and CC configuration. Everything is on MIDI channel 1 unless noted.

General MIDI settings

• Local control: off
• Omni channel: off
• External MIDI jacks: enabled

Link to this answer

Check your current firmware version before updating.

1. With the Tweaker unplugged, hold down the round rubber button in the centre of the four directional navigation buttons while connecting the Tweaker to your computer.
2. A volume named TweakerDisk will mount on your system.
3. Drag the Tweaker firmware binary file and drop it onto the TweakerDisk volume.
4. The velocity pads will flash while the firmware updates. Do not disconnect the USB cable during this process.
5. Once the pads stop flashing it is safe to disconnect. Reconnect the Tweaker to return to normal operating mode.

Link to this answer

The current — and final — firmware version is 5.2.

You can check your version at any time by holding down the three buttons indicated in the Tweaker User Manual. While they are held, the firmware version is shown on the bottom encoder LED rings of both mixer channels.

• The left LED ring indicates the number before the decimal point.
• The right LED ring indicates the number after the decimal point.

Count both the red and the blue LEDs. For version 5.2, five LEDs light on the left ring and two light on the right.

Note: if you think you have 4.1, you most likely have 5.2 — make sure you are counting both the red and blue LEDs.

Link to this answer