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.
Very strange. I attached my select parameter script and controller template. Does it work for you? And could you post your script, so I can test it?
One more observation: so far I had snapping switched on, if I disable it the value does not jump to 100 but stays at 127 (instead of going to 0 as it should).
when snapping is on and the value jumps to 100, it displays the message that it auto snapped to max value
Great, thanks. I will look into this when I get a chance and report back.
I did quite some testing to narrow down the problem further, as it is a showstopper for me – I rely heavily on the buttons of my two MFTs. Things I tried with the problem persisting:
– Different computers: Macbook M4 and Macbook Air M2
– Different versions of Ableton: 12.2 vs 12.2b18
– Different MFTs (configured identically except for MIDI channels)
I have CSS 2.8 on my MacBook Air and I created a similar script with 2.8 and 3.0 and ran them simultaneously on two MFTs. Here is a video: https://youtube.com/shorts/hi21jI54Rro. On the left you see V2.8 working fine, on the right the new version with faulty behavior.
I also found a workaround: using knobs instead of buttons in the controller template. If the physical button is configured as a knob in CSS 3.0 it works. So after 2 full days of bug hunting I would say something with the implementation of the button is problematic. Possibly in conjunction with the specific environment (Python version, Mac/PC, whatever) as I seems to work on other computers.
I am happy I found the workaround because it allows me rewrite the template and continue with my work. But also I am afraid that this bug is not caught and the workaround remains permanent. @JohnC please test it on different computers, we see it already on 3 machines. It shouldn’t be impossible to reproduce. I want to see this fixed!
Yep, you got it. Well done. Thank you for your perseverance, much appreciated.
Thank you for your in depth analysis of the issue.
We will investigate further and hopefully have it working as expected soon.
On/off buttons should now work with parameters.
Re-generate your script to get the updated changes
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.