Quote:
Originally Posted by Justin
When you open REAPER, you can also go to "Options->Show REAPER Resource Path" to see what path it is using for your configuration state... See if it is an unexpected path?
|
C:\Users\SAM\AppData\Roaming\REAPER
Can a control surface plugin or startup actions scripts mess up the file?
Are scripts and plugins allowed to write that file? Or take a lot of time to write so a quick reaper restart can corrupt the file by leaving it mid-updated?