Your shopping cart is empty.
Hi,
CSS stopped working when i tried to switch to ableton 10. I can select the Ableton live location, but when selecting the Midi Remote Script Folder nothing happens..
I can also no longer switch back to Ableton 11
Please advise!
Kind regards,
Jeroen
Comments
Hi Jeroen,
It sounds like the log.txt file in Ableton Live 10 is affecting the performance of CSS and may need emptying.
Try clearing the log (open the log menu at the top and click clear)
Or navigate to the actual log.txt file in finder/explorer, open the log.txt file, delete contents, then save the file.
Oh and make sure you're deleting the correct Live version log.txt file i.e.
/Users/USERNAME/Library/Preferences/Ableton/>>>>>Live 10.1.42<<<<
Hi John,
Still not working..
I removed Ableton 10 completely. Then tried emptying and saving the log.txt from Ableton 11, not working.
Then I removed the log.txt, but still not working. Then I removed an reinstalled Ableton 11, but still nothing..
Again I can select the Ableton Live Location, but when i select the Midi Remote Script Folder the location in CSS stays empty. I can browse and select all Folder locations, but all stay empty in CSS. (screenshot added)
Where is CSS retaining the settings?
How can it be that CSS gets messed up by reconfiguring the folder paths..?
How can I reset the config settings of CSS? (regedit?)
I have a fairly good understanding of Windows, Applications, Registry etc, but I am at a loss here..
Kind regards,
Jeroen
Hi,
I forgot to mention that when starting CSS the program does not state at Settings, that the Ableton Live location, Live Version and Log.txt are not set / not found
Hope someone can point me in the right direction..
Hi Again,
I have found the solution! :-)
The CSS settings seem to be stored at the following location \ File (Windows):
C:\Users\(USERNAME)\Control Surface Studio\settings\settings.json
When i removed the file (settings.json) CSS worked again!
I knew it should be a simple solution..
Cheers!
Hi digi,
Sorry I just saw your messages and was about to suggest deleting the settings.json file.
Glad to see you figured it out yourself! :)