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?
Check the button settings in the controller template or in the mapping(if you have overridden these in the mapping settings form), as we now have new midi velocity options for buttons (between), you may just need to re-configure this for your button
Also, I’m not sure how a css script could be crashing your twister when changing songs, unless you have added your own custom code in a Reaction?
no reactions. I can record a video if it is helpful
Here is a screen capture that demonstrates the Midi Fighter Twister (MFT) crashing. The 40 and 51 scripts were made with the most recent 2 version. The button test and chain 1 update scripts were made with CSS 3.0.1. You can see the MFT crashes when changing in and out of css 3.0 scripts. You can also see the button behaviour that has been introduced.
I didn’t show the change song crashes sorry but I can do that as well if needed.
In relation to the buttons, I tried a number of configurations but couldn’t get it to work as expected with css 3.0. Can you shed any light on on how to set this up as a simple on off toggle that works as per the previous mappings in the video?
Thanks
Thank you, Do you see any error messages in the css log when this happens?
Which version of Ableton are you using?
I have tested switching between CSS 3.0.1 scripts in Ableton Live 12 (12.2b17) without issue
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.