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?
I also tried send, volume and (native) device parameters and you are right: it works – so I dug deeper. It appears only some knobs of M4L devices show the faulty behavior (although strangely many also don’t). For example the MultiMap M4L device which comes with Ableton: if I try to control the input dial with the new selected parameter mapping it snaps back to 100. Does it work for you?
In my case it is macros. Specifically macros on a chain. But I could not get it to work as expected for macros full stop.
right, macros also do not work!
Both the ‘Device parameter’ and ‘selected parameter’ mapping types work fine with Macros for me.
I also tested macros in a chain and with a max4live device. No issues.
I’m using Ableton 12.2b.18.
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.