Some MxDCore.py error

98 viewsCSS Controller Templatescontroller template
0
0 Comments

Hi there !

Just wanted to edit a Twister template with Ableton live 12.3b11 and noticed some errors that stop the script to be generated and i need some help because i dont know where to look at

File “..\..\..\output\Live\win_64_static\Release\python-bundle\MIDI Remote Scripts\_MxDCore\MxDCore.py”, line 1612, in _observer_update_listener
File “..\..\..\output\Live\win_64_static\Release\python-bundle\MIDI Remote Scripts\_MxDCore\MxDCore.py”, line 1641, in _observer_install_listener
RuntimeError
:
Track has no frozen state

Thanks a lot !!!

Glenn V. Answered question September 29, 2025

1 Answer

1
Glenn V. 2 Comments

I don’t have a straightforward solution but am willing to dig a little into the problem:

“MxDCore is the bridge between Live’s Python scripting environment and Max – it’s the glue that makes the Live control and feedback in M4L possible”

“‘freeze’ function, allowing you to reduce the CPU overhead of tracks by bouncing them to audio in the background. When a track is frozen, all the CPU-intensive tasks are temporarily committed as recorded audio.”

From the error message it seems MxDCore is expecting a frozen track (i.e. one that’s bounced to recorded audio).

Glenn V. Posted new comment October 1, 2025
Walt_A commented

Hi Glenn and thanks for the answer
Well thought that its a weird error too , but, cannot send my template to Ableton anymore..
Glenn V. commented

When you generate your script in the CSS app, does it show a green box that it was succesful? If it does, then you should be able to find a folder inside Ableton’s app that contains your script. To find this folder: right-click the Ableton app, select show contents, then navigate to “contents > App-Resources > MIDI Remote Scripts” and scroll down inside the folder until you reach folders starting with “css_” (these are your scripts). If you find the name of your script, then it was succesfully generated.

However, on start-up of Ableton, Ableton will load all the Control Surface Scripts that were set in the settings. When it encounters an error, the script that produced the error won’t be in that list of scripts anymore. So it could be the script conflicts in some way with your Ableton setup.

Could you maybe try and set the mappings you’ve changed in your script to invisible (by clicking the “eye” icon on the same line as the mapping, so the eye becomes crossed out and the text fades) and re-generate your script? If the script now loads succesfully in the MIDI settings of Ableton, then (at least part of) the problem lies with one of the mappings.

Categories