Scripts no longer appear in ableton control surface dropdown
Hi John and community,
Im using CSS 2.9.0 and ableton 11.3.43. This issue happens for all scripts i generate, including template and tutorial scripts and controller templates. All the global paths/settings appear fine and a folder with my script name is created in the appropriate place. For a time only some scripts would not appear in ableton, now all new scripts arent displayed.
I have also encountered some bugs with reactions. When they are sufficiently complicated, they often break and dont generate correctly.
I have also encountered an issue, where when deleting a reaction, its mode is deleted instead, breaking the whole script. I have also encountered the script generation error
get_mode_id error: map level out of range
I hope you still support v2.
Best wishes, Theo
I have gotten to the core of the issue. when something in any reaction fails, the whole script silently fails and no longer appears in the ableton drop down.
is there a way to debug reactions?
(the map level out of range error probably came from manually editing json)
Cheers, Theo
If you’re using custom code then you could use a “try…except…” statement to catch errors, so that they won’t fail the entire script.
@css_devs: would it be possible to implement these “try…except…” statements natively in all Reactions? For example with a general print to CSS’s log of the error’s details and a mention of what Reaction caused an error in Live’s status bar whenever an error occurs. And maybe even a kill switch variable that would stop a Reaction from firing again when an error has previously occurred.
The Action blocks in Reactions already use try and except statements. If a block causes an error, there is a message which is displayed in the css log. It includes the Action block number and Reaction name which has errored. Also the error message.
This usually prevents scripts from disappearing and allows debugging.
Sign up
User registration is currently not allowed.
Oh I just re-read your message and see you’re using 2.9.
We fixed those issues in CSS3.