CSS 3 Breaks Button behaviour and crashes MFT when changing Ableton songs
CSS 3 breaks the behaviour of buttons on the midi fighter twister. The previous workaround (with settings at 127%) is now broken and I am unable to get the buttons functioning as expected.When I change the setting back to 100% I now get 3 values – 0, 127 and then 100. If the solution involves rewriting entire scripts (I have 16×16 buttons programmed) this is getting ridiculous.
The scripts totally crash my Midi Fighter Twister when changing songs in Ableton.
Any insights?
12.1.11
Here are the error messages below I get in CSS when loading Ableton – I don’t see any error messages when it is happening.
cannot import name ‘_MxDCore’ from ‘_MxDCore’ (/Applications/Ableton Live 12 Suite.app/Contents/App-Resources/MIDI Remote Scripts/_MxDCore/__init__.pyc)
Traceback (most recent call last):
File “”, line 1, in
File “/Users/st———————-/Music/Ableton/User Library/Remote Scripts/Showsync/__init__.py”, line 5, in
from Showsync import l11l11l_boe
File “/Users/st———————Music/Ableton/User Library/Remote Scripts/Showsync/l11l11l_boe.py”, line 10, in
from _MxDCore import _MxDCore as l11l1ll_boe
ImportError
:
cannot import name ‘_MxDCore’ from ‘_MxDCore’ (/Applications/Ableton Live 12 Suite.app/Contents/App-Resources/MIDI Remote Scripts/_MxDCore/__init__.pyc)
You have errors coming from ‘Showsync’ and ‘_MxDCore’. These are not errors related to a CSS script.
I removed the Showsync folder and I am no longer getting error messages in CSS 3.0.1. The crashing behaviour of my MFT continues regardless.
Edit – I think it is related to the underlying controller template. I can reproduce (or remove) the issue when I change controller templates. This is not ideal but I think I can work around this.
I haven’t been able to find a simple on/off toggle solution though, and this is a deal breaker…..
I have the same problem with the MFT buttons. The value goes to 127 but does not reset to 0 but to 100 instead although the MFT sends clearly a 0. This makes my formerly working scripts totally unusable because I cannot switch off anything! I tried it also with a fresh MFT controller template from the website, played around with the settings, but the problem persists. Looks like I need to go back to CSS 2 to be able to work. Sad.
(using CSS 3.0.1 and Ableton 12.2b18 as well as 12.2)
also tried it with a new empty script, same thing
In CSS3.0.1
I can’t replicate this issue with a button on the midi fighter twister.
I’ve tested with a send, device parameter and track volume. They all function as expected going from max to min with each button press.
Check the following
– the midi velocity settings in the controller input in the controller template
– In the mapping’s ‘Input Control Override’ section – if you have set this to ‘custom’ then check the settings here also
– the midi settings in your MIDI fighter utility app for the twister
Sign up
User registration is currently not allowed.
I have the same problem with the MFT buttons. The value goes to 127 but does not reset to 0 but to 100 instead although the MFT sends clearly a 0. This makes my formerly working scripts totally unusable because I cannot switch off anything! I tried it also with a fresh MFT controller template from the website, played around with the settings, but the problem persists. Looks like I need to go back to CSS 2 to be able to work. Sad.