CSS script not showing in Ableton
Maybe a bug,
I’m exporting my script from the last version of CSS. It goes to the right folder in Ableton but it does not appear in the list in Ableton.
Hi Maikoos,
Thanks for posting your log.txt file. I can see that the script is erroring due to this line:
self.global_feedback_active =
To fix it, in your script’s settings form, set ‘global feedback’ to custom then select an option for the Global Feedback on/off option below it. Do the same for LED On / Off too if they don’t already have an option set.
(see the attached screenshot).
The script settings override the Controller Default LED settings. You can now set this back to ‘Default’ if you don’t want to override the Controller’s LED settings.
Probably best to go into your Controller’s settings form too and make sure you have options for LED On and Off set. As if they’re blank this can also cause an error.
LED Feedback options work like this.
Mapping LED Feedback Options override the Script’s Global LED Feedback settings. And the Script’s LED settings override the Controller’s Default LED settings.
The reason for you having 2 json scripts is probably because at some point you have created a script with the exact same name as previous script.
Hi John
Thanks for the trouble shooting. I’ve gone through and adjusted all the LED feedback settings as advised,. We’re nearly there I hope. Script is half working though I still am getting lots of errors (see the attached log.txt file) and corresponding non functioning controls.
One issue that stared ocurring before the update and is continuing on is that when I select a device, particularly if its embedded in a chain, it no longer displays in the bottom LH corner of Live. It selects, but doesnt display. In the past whenever I selected a device that device would be lined up on the bottom LH side of the screen (see examples attached)
Also a question regarding text feedback. I’m wondering if its possible to have real time feedback of text such as names and controller info as you move around live, like with the Push or with my keyboard the Novation SLMK2. With the supplied Novation template you see the names of devices displayed in the LCD window on the Kb.
Just a thought.
Regards,
Mikey
Hey Mikey,
I had a look at your log.txt file see this error repeated a few times:
414134 ms. RemoteScriptError: AssertionError
414134 ms. RemoteScriptError: :
414134 ms. RemoteScriptError: Registry key (176, 0) registered twice. Check Midi messages!
The only time this error appears with Control Surface Studio Scripts is when you duplicate MIDI Messages for Inputs in your Controller. By duplicates I mean that they have the exact same MIDI Channel, Type and Value settings. Each Input in your Controller should be unique with at least one of these.
We will add an automatic check for this in the near future but in the meantime I would advise you to check all your Input MIDI Messages.
There’s another error:
4788 ms. RemoteScriptError: ImportError
4788 ms. RemoteScriptError: :
4788 ms. RemoteScriptError: No module named nanoKONTROL
4788 ms. RemoteScriptError:
But I don’t think this is related to a CSS Script as we don’t use anything from the nanoKONTROL script.
Thank you for the Feature Request regarding text feedback, this is an interesting one which we have made a note of.
Thanks
John
Hi John,
Hope its not too hot for you over there at the moment.
Thanks for the suggestion. I checked my controller midi messages and sure enough the keyboard I’d put on the controller was sending the same CC message from each key. Strange but pre update that hadnt been an issue. Maybe pre update it was sending note on/off messages to different notes by default? That has resolved that issue so thanks. The NanoKontrol refers to another script I have for the a different setup so not relevant to this one.
Also putting the ADVANCE script into the Ableton live remote script box has fixed the problem with devices not diplaying properly.
Regards,
Mikey
Hi Neil,
It’s is very strange that none of your scripts appear in the 10.1.1 list.
From looking at both log.txt files there was an error showing in 10.0.6 for your script: css_nca_red_box_script_02
This doesn’t even appear in 10.1.1
This leads me to think that there is a new midi remote script folder for 10.1.1.
In your email you also sent you said you changed the location of midi remote script folder in your settings but did you re-install the scripts into the new midi remote script folder?
Also, is the midi remote script folder in your screenshot from this location:
ProgramDataAbletonLive 10.1.1ResourcesMIDI Remote Scripts
And not
ProgramDataAbleton10.0.6ResourcesMIDI Remote Scripts
Sign up
User registration is currently not allowed.