Your shopping cart is empty.
🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left...
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Control Surface Studio User
Hey John and all.
So today I wanted to update some old scripts and fix some stuff. Haven't used it in a while so the new version told me that there was a v2-reactions and all that stuff. So I had to fix a script for my launch control.
Fair enough, I thought. Nothing. Nothing worked. Everything I tried - nothing in this controller worked. The script was installed, and I could see it in Ableton etc. But nothing.
So I made a new one with just a play button. Nothing. Once again - everything seems fine, and the pads even send midi data in ableton. But nothing.
So my frustration grew, and I was troubleshooting for an hour. The weirdest part is that my script for my midi fighter works fine. BUT. I thought, ok, lets try adding a button in this script. Nothing. The old functions work but nothing that is added.
And then... All of a sudden when I restart CSS, all the scripts are gone.
So I try to reinstall. Now it gets even worse.
I set Live Location, but script folder doesnt automatically adjust. And nothing else. I try to do it manually - nothing updates. Same with Live version folder and Log.txt location.
Everything is just broken.
I cant see any tamplates, any scripts - everything is just gone.
Trash and reinstall CSS? Nothing.
So now. After trying everything. Even my old script is gone from Ableton and I just want to cry.
Please. Please. Please. Help me.
Topic Category:
Comments
Ok. So an update.
I found out how to do a clean re-install, and now it seems I'm back at square 1 (which is far better). My old fighter twister script is now working.
However. I cant get any new editing, any changes to any script (either new or old scripts) to work. At all. Super frustrating.
I get no errors in the log or anything.
Another update. Its all so strange.
So now. After trying and troubleshooting...
I tried to get something working, by assigning a button on my fighter twister to "play". This didnt work, as per my previous post. So I removed the mapping and carried on. After a while, I noticed that suddenly it worked. But without a mapping!
And still, anything I try to do to my launch control seems to not work. It seems like all the buttons is seen as note values by ableton, no matter how i map it in CSS.
And again, the scripts are right there, and I get no error messages. Am I going crazy?
Ok - panic is decreasing - things are turning around.
It seems...
1) Just starting a new project (cmd + n) does not update the script in Live 11. Have to restart entirely.
2) There seem to be alot of problems with midi monitoring in CSS. As soon as it is engaged, it spikes the CPU and crashes. Or it gets really jittery and listens to all sorts of weird stuff.
But things are looking up!
/A
Hi! I’m just on my phone at the moment and don’t really know much, but one thing that struck me. Did you make sure that the correct script is selected in ableton and with the right midi ports?
I noticed that if I mess up a script and update it, it gets removed from the list and after fixing the script I have to go there and set it back.
Sorry if this is too basic but thought it’s worth a mention. Sounds like a crappy situation and I hope you get it in order!
…ah I missed your last post before I posted mine. Good stuff!
About the first point, I noticed this to I constantly have to restart Live but I assumed it was a windows thing. Never used it with live 10 only 11.
Hi guys,
To do a complete reinstall of CSS, as well as deleting the CSS Application, also delete the 'control surface studio' which you will find in the home directory of your operating system. This folder contains all settings, script json files and controller template json files.
A script can disappear from the Ableton preferences menu if it contains malformed code.
You can check the log in css for errors or directly in the log.txt file for your version of Ableton live.
We are investigating the issue with midi monitor causing a spike, I advise to only turn it on when you need to input midi data and then turn it off again.
Ableton 11 needs to be restarted in order to see changes, 10 does not.
This isn't anything to do with our script/application. Due to this, I recommend building scripts in 10 and porting them to 11 when ready.