We moved to a new shop! head over here to see what's new

MF Twister Ableton Script

Description and Instructions

This script requires Ableton 9.6 or higher , if you are running an older version grab v1.2 from the sidebar

Introduction 

This mapping was made for Ableton 9.6 and is fully compatible with the Midi Fighter’s sequencer mode.

This guide refers to the 2.0 version of this mapping and it will be updated to reflect changes in following versions. 


Features

  • Track Select/Solo/Arm/Mute
  • Track Volume/Pan/Sends
  • Device control and navigation (On/Off, Next/Prev Bank, Next/Prev Device, Device Lock)
  • Focused Track Controls
  • Transport controls

Installation

After downloading Twister Ableton Script v2.0.zip from DJTechtools and unzipping it a folder will be created with the same name that will contain this guide and three more files: Twister_Ableton.mfs and a folder named Script.

1. Open the MF Utility and import the Twister_Ableton.mfs file via File > Import Settings.

2. Copy the contents of the Script folder (_Mono_Framework, _Tools and Twister) to your Ableton Live's MIDI Remote Scripts folder.

  • WINDOWS - Located in “C:\ProgramData\Ableton\Live 10 Suite\Resources\MIDI Remote Scripts”. Program Data folder is not visible by default, you might need to enable "Show hidden folders" as shown here).
  • MAC -  Right click on your Ableton's app and click "Show Package Contents” and navigate to “\Contents\App-Resources\MIDI Remote Scripts\".

3. Launch Ableton Live and the script should detect your device and set itself up. If this doesnt’t happen go to Preferences and under MIDI Sync tab select Twister in the Control Surface drop down list and set the correct input and output MIDI ports.


Notes:

  • Requires August 13th 2014 firmware or higher
  • Changing the side buttons’ order will break this mapping so avoid it to prevent losing functionality: If that is the case, reload the .mfs file.
  • If the script doesn't show up make sure you copied over all contents of the Script folder to the intended destination and NOT the Script folder as a whole.
  • This script was originally made by Amounra for the Livid Ohm64 controller and has been edited to extend part of it's functionality to Twister and PY files are included in this release. If you mod the original script or this one in any way don't forget to credit the original author.

Dsc_9426
Problem downloading or other issues? Let us know on the forum.
-
Comments for v2.1.0
mikael about 17 hours ago
Is there anywhere a better explanation on the different scripts with detailed info what bank , knob , function etc the script affects . Like a map ..it’s so messy to guess what bank and knob does what .. or is it just me ?
30724304_1878808445745894_9154228999033978880_n
Oxo 3 days ago
Are you planning to release a new version of remote scripts for Ableton 11? The current script 2.1.0 does not work in Ableton 11. In the new version of Ableton 11, Python versions have changed. Currently (in version 10) Python 2 was used. In the new version of Ableton it will be Python 3
Rob Roach about 1 month ago
I just can’t get this thing to work.. I followed the instructions, though the name of the script file to apply to the controller is incorrect. (documentation says filename is Twister_Ableton.mfs, but the file it contains is named MFT8.mfs, but ok) I am never able to see Twister listed as a control surface no matter what I do. Ableton sees midi data coming off the twister just fine, but never can be used as a control surface... Confirmed the files are in place. Any ideas?
Shinyoung Lee about 1 month ago
I already had a pre-existing _Tools folder in my \Contents\App-Resources\MIDI Remote Scripts\ folder. How should I resolve this? It currently contains __init__.py, CukeTestTemplates (folder), InstantMappings-HowTo.txt, and UserConfiguration.txt Any ideas?
Casey Bates 27 days ago

Copy over any unique files from the Midi Fighter Twister _Tools folder that do not exist on your pre-existing _Tools folder. Ignore the files that exist in both places. At least in my case, I found the contents of __init__.py to be the same in each folder, so there was no need to change anything on my hard drive.

JoostvdBerg about 1 month ago
Was wondering if it's possible to map bank 4 myself considering it has no use now, or does that interfere with this mapping you made?
Cat___roxy_arcos-20
padi_04 about 1 month ago

Bank 4 was left blank intentionally so feel free to map it however suits you best!