File Corruption
I periodically have an issue with file corruption, I can work on a file for weeks no issue then suddenly “save” button seems to not respond when pressed in CSS3 UI and the file size of the json = 0kb. While annoying and caused some loss, I began a habit of backing up my json, and went along fine enough.
However, now I seem to be in a problematic space where any of my backups, when loaded into CSS3 and then I try to make arbitrary change for a save, results in that same corruption.
Are there known causes of this?
MacOS Sequoia 15.6
CSS 3.0.1
The latest file, restored from a backup: link
After opening the file, disabling a mapping, attempt save causes 0 kb size: link
I’mm not aware of any other reports of this happening in recent times.
In the Script Editor, maybe try selecting all of the Mappings (and Modes), export them to a file then import that file back into CSS and try using that in future.
Awesome!
I think I figured out more.. when I hit save usually it’s nearly instant but sometimes it takes between 8-11 seconds from clicking save to completing.. I think I was thinking it was frozen, file goes to 0kb then I shut down the app.
enhancement request, any visual way to indicate save was pressed, in processing, then completed? I’ve spent past few months thinking I’m nearly escaping corrupted files haha.
Saving is always instant for more.
Just to confirm, you’re referring to save (save to file) and not Generate script to Ableton?
One thing which might help if this ever happens to you again >
Each time you generate your script to Ableton, the latest version of the Script json and Controller Template json files are included in the generated script folder (in Ableton Live’s MIDI remote script folder).
So if you find yourself with an empty script, you could grab the last generated version from there 🙂
Correct, I’m referring to the Save to file generating the JSON.
Agreed, 90% of the time it’s near instant for me. I timed it about 8-12 seconds would periodically occur about 10%.
When that 10% occurs, I had eventually gotten into the habit/impression something was wrong, I’d close app, reopen app and JSON was now corrupted since save never finished. I had assumed 0kb file corruption was causing me to close app, not realizing me closing the app was the actual problem.
The original file is attached to OP
I have the same issue right now, and it was also from pressing save and closing CSS3 after it didn’t do anything for a long time, it has also become very buggy in the last days and often freezes.
I have a File now that i can’t restore, its huge and took months, and when trying to get it back from the ableton folder, my left half just appears to be blank.
PLS help
Guys, if you’re working with a large script/controller template. Try the following:
1. Clear the log in the bottom right panel of the script manager.
2. turn AutoTags off in the CSS settings menu
Thx i did that now, but is there a way of restoring my Script from the Midi Remote Scripts folder in Ableton? I imported it to CSS3 but i just have a blank screen. The json file in the Ableton Folder should be free of any errors
If the json file in the Ableton folder is ok, it should import back into CSS without issue.
Sign up
User registration is currently not allowed.
That fixed it! Thanks for the guidance