CSS script not showing in Ableton

Submitted by danicroitor on Tue, 07/02/2019 - 16:26
danicroitor
Pro User

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.

Topic Category: 

14 Responses

Comments

John Carney
Forum Admin
#1

Do you have any errors in your Error Log?

danicroitor
Pro User
#2

none

danicroitor
Pro User
#3

actually yes!

upload files: 
danicroitor
Pro User
#4

the thing is that I've tried with brand new script, I've just added the Mode. and it does not show up in Ableton

John Carney
Forum Admin
#5

I see this causing the error: 12_id_235
Have you named something '12' rather than using letters/words?
Naming mappings with numbers at the start will crash the script and yeah prevent it from showing in Live.

danicroitor
Pro User
#6
danicroitor
Pro User
#7

I think that was it.

Maikoos
Pro User
#8

Hi there. Thanks for pointing out this post Dani. I've checked my script and can't find anything beginning with a number. How sensitive is this? For example I have "M4L " and "LP-1" and "LP-2" as names for controllers. Is that too number sensitive? There are errors in the log.txt but I dont know how to interpret them. There seems to be a problem in line 49?
Resources/MIDI Remote Scripts/css_slmk2_impro/css_slmk2_impro.py
1600 ms. RemoteScriptError: ", line
1600 ms. RemoteScriptError: 49
1600 ms. RemoteScriptError:

1600 ms. RemoteScriptError:
1600 ms. RemoteScriptError: self.controller_LED_on =

also a syntax error later on??

I attach the json and the log.txt.
Thanks

upload files: 
John Carney
Forum Admin
#9

Hi Maikoos,

It sounds like the attached Controller for your script is missing LED On and LED Off settings.
In the Controller Manager, open the Controller's settings form and set these.
See the attached screenshot.

You also said:
"How sensitive is this? For example I have "M4L " and "LP-1" and "LP-2" as names for controllers. Is that too number sensitive?"
This should be fine. It's only an issue if you begin the name with a number.

Maikoos
Pro User
#10

Thanks John that worked. Ableton now sees the script in the preferences BUT it doesnt work at all.
None of the controls work. Very strange as this script worked almost perfectly before the update. Not sure what's been lost in translation.
Is it to do with the LED implementation perhaps? If I set the Global LED feedback to ON do the feedback settings for the individual controllers in CSS need to be OFF? OR if the CSS script is sending feedback to a controller on the KB that doesn't have an LED will that result in an error?
I attach the latest log.txt, and CSS json file (which is the same as above)
Also in the remote script folder there seems to be 2 json scripts number 19 and 24, whats going on there? (See screen shot.)
Thanks John,
Mikey

John Carney
Forum Admin
#11

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.

Maikoos
Pro User
#12

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

John Carney
Forum Admin
#13

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

Maikoos
Pro User
#14

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