Ableton have released Live Beta version 12.3.5b2 Which includes this fix: Fixed an issue with the Max for Live API that caused Live to lag or freeze. I’ve tested our lagging issue against this beta version and it appears to be fixed, but could anyone else with beta access please check their scripts too. Thanks […]
If you’re using the latest version: CSS 3.1 The log panel in the bottom right corner of the script editor now has a MIDI channel monitor menu. You can set this to None to prevent CSS from listening to incoming midi on any channel (or just one channel if you need).
This error is definitely not CSS script related, I see it in Live’s log file when certain Live sets load from disk regardless of whether a CSS, DIY, or No custom “remote script” is configured in Live’s midi options. This thread helped me figure that out. (and seems to be the only “valid” hit my […]
Live object model > tracks > Playing slot index self.song().tracks[0].playing_slot_index This is the slot/scene number of playing clip slot in a specific track, you can use this value to move the selected scene to.
Reactions add their code to which ever listener you select. So even though they are visually separated inside CSS they will be merged in the actual script. This is why ‘exit script here’ will cause this behaviour.
Your listener is wrong, it should be: Clip’s playing status value has changed Then you also need to press on the little hand icon next to it, and select Highlighted Clip Slot
Ableton have responded to me and said it is a bug which is under investigation. No promise of when a fix will be issued as yet.
You can create Reactions for that purpose: Toggle when Clip is played: ________________________________________________________ Listener: ”Clip’s playing status value has changed” (press on the little hand icon and select highlighted clip) Action Block1: Conditions: here you can test, if the waveform is visible or not, with: ”Application […]
For anyone wanting to use their scripts without the lags, you can download the Ableton version prior to 12.3 on their official page, and you can just install it as a second Ableton, that way you can use something like stem separation in the newest version (if you need it) and save the stems somewhere, […]
Late to the party, sorry just saw this thread. I am experiencing the same issue with my Midi Fighter Twister and 12.3. I have been in contact with Ableton support – yet to be resolved, although they did make it clear they are “not able to offer individualized support for custom remote scripts.” My mapping […]