🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

If CSS Is Running Slow: Read Comment #4 in Here!

Submitted by plux on Sun, 11/05/2023 - 18:25
Control Surface Studio User

I am a brand new user (purchased today), been looking for something like this for years to make all of my mapping dreams come true!
I work in AV with Audio DSP's all the time so I'm quite familiar with how builing logic systems like this works.

I seem to be having an issue with performance.. the app is VERY sluggish and I have to constantly wait before I do anything, in this instance I'm adding / configuring mappings.

I can't get very far with the mappings, after a while the program seems to have had enough and present me with a full white screen. The only way to get rid of the white screen is to restart CSS and reenter my password.. which usually means I've lost my progress. It happens every 5-10 minutes.

System info attached - perhaps theres a visualc++ or python module needed that's causing issues?

upload files: 
Topic Category: 

15 Responses


Control Surface Studio User

Update: I downloaded to my Desktop PC running windows 10 and the app works phenomenal! I will use that to develop scripts until I hear back from support.


Control Surface Studio User

Further update, I ran into the exact same issue on my other PC. please help!

Control Surface Studio User

One last update -clearing my log.txt file fixes the issue. Thanks to support for clearing that up!

Forum Admin

Hi all,

Just to confirm what has already been said here,

If CSS is running slow for you, this is usually because the log.txt file has become large.
As CSS constantly monitors the contents of the log.txt file, the bigger it is, the more resource intensive it is for CSS to monitor.

If you experience this issue:
Click the clear button in the bottom right section of the Script Editor screen (see attached image - clear log)
Open the log.txt file directly, delete its contents and click save.

If you click the clear button and everything is still hanging...
you may need to free the App up to complete the clearing of the file.
click the 'save' button at the top of your script, then click 'close'. (see attached image - save and close).
Closing the script manager effectively stops CSS from monitoring the log.txt file.
You can then re-enter your script.

Control Surface Studio User

Ive just purchased and im instantly having the same issue, let me know if it happens again to you.

Im on a mac studio m2 max, 12 core 32gb ram.

Logs are only 9mb, the interface is extremely slow like 1-2 second response when i'm in the scripting area trying link scripts to the interface.

Controller area seems to have no noticeable delay although ive only tried a super basic mapping 4 pads and faders

Forum Admin

Did you clear your log? 9mb is a lot.

Control Surface Studio User

Thanks JohnC! Had the same issue but clearing the log resolves it- cheers.

Forum Admin

It's strange that this issue has suddenly become so popular, CSS has always been monitoring the log and this has rarely been an issue...
It's almost like a recent update of Ableton Live is dumping more stuff into the log.

Control Surface Studio User

happening to me too.

Forum Admin

And did you clear your log?

Control Surface Studio User

Same problem here (macOS 12.7.2, macbook pro 2016, live 11.3.13). At this stage I also see still incoming MIDI data although the controllers are physically disconnected. Clearing the log often doesn't work - CSS doesn't respond and the CSS helper task goes up to 100-150 % cpu load.

Control Surface Studio User

Updating to 2.8 (Macbook Pro M2/OSX 12.6.8, Ableton Live 11.3.21, Icon Platform M+) was painful experience. After 2 hours of blood, sweat and tears, fearing everything I had accomplished in version 2.7 (in a very time consuming way) was gone, I reverted to the old software via Time Machine and it's a true relief knowing I at least got back to the pre-update state.

1) CSS didn't remember my password even tho I checked the "remember me" box, which became a big annoyance further down the line since I had to restart CSS countless times as it was extremly slow and crashed quite often (as already discussed here).

2) A lot of changes have been made to the design – from my point of view most of them for no obvious reason. I found it very hard to reorientate, especially since CSS is not the kind of program I use every day – rather once, and if everything worked out never open again.

3) after updating I just got an error that some .json file was corrupt and couldn't be importet, realizing everything was gone. Trying to import controllers and scripts manually produced numerous errors: modes were not linked to the corresponding controllers anymore, mappings were not linked to modes anymore. Everything was basically a complete mess close to having to do it all over again anyway.

4) trying to then manually link all mappings to a mode resulted in CSS crashing sooner or later. Saves didn't work.

5) when importing a controller some knobs/buttons were missing

After 2 more hours of digging in I think I found what might have caused the problem: there was an accidental blank space before one mode's name. That didn't cause a problem in 2.7, but does so in 2.8. I guess that caused the whole script to go bonkers from there on.

Initially I just hoped to solve a problem I couldn't get a hold on in 2.7 by updating to 2.8. But doing so got me into such a spiral of problems that my current mappings feel so prescious that I absolutely hesitate to update again – and potentially get rid of my initial problem.

Control Surface Studio User

CPU load freezing my Mac. Unable to use the app at all at this point, even when my controller is unplugged so no MIDI stream into the log.

I'm at the point where I'm just going to uninstall. Only had the app 1 or 2 weeks. Gutted as this looked like a great product on paper.

I hardly managed to add 2 mappings so it wasn't a huge template.

Any suggestions before I try one last reinstall? Thanks.

Control Surface Studio User

Did you clear the log file? If the app freezes, just go to the log location and open the log text file, delete everything and save

Control Surface Studio User

Hi, I disabled the log function in CSS and use the Terminal on macOS with: "tail -F path-to-the-log-file".
Although it's not that convenient as the built-in log at least it doesn't freeze CSS.