Originally Posted by AudioTrack
Originally Posted by jpettit
Sorry this should be just thrown out and the standard save as windows dialog should be used.
This solves many other problems with this approach.
After exploring how this works, I don't think that a 'Save as' standard Windows dialog can be used. I don't think that the schemes are saved as external files, but rather, they are stored within another configuration file.

Regardless, a populated list of existing scheme names is still required.
No, they are stored in the Data subdirectory and a subdirectory strangely called called Schemes.
The reason the MS standard file save needs to be used is there is no update command.
Because there’s no true Update command, the software forces you to use ‘Save As.’
You have to remember the exact name you used before, type it in manually, and only then get an overwrite prompt.
Ninety percent of the time you’re just trying to update an existing file.
They are aware that this workflow is awkward and I believe they will make it a standard save where you can see your files and what you named them previously.

Studio One (latest version), Win 11 23H2 , i9 -10940X 3.3 GHz, 32GB Mem, a 4K 40" monitor, PreSonus Studio Live III Console as interface/controller. secondarily test on Reaper, Cakewalk, and S1 on Surface Pro 3 Win 10 (latest versions).