I understand that the focus of the product is on “what it does” rather than mass-deployment, however, i would urge the devs to allow something like the the creation of a default audacity.cfg, which lives in the same directory as the executable… and if it exists, is used as the default config for any new user profile that comes along… you already have a process to create %appdata%\audacity.cfg…
I understand i will likely be told to fuck off as well… but the reality is that the ability to create a default config would be handy for some of us.
And with that - i will pre-fuck-off in expectation of being told to fuck off.
As you already mentioned, audacity.cfg is created automatically (on the first start). It resides here_ %appdata%\audacity\audacity.cfg (not directly in %appdata%).
You should make an install script to create the cfg file with your settings - this would be much better than cluttering the program folder with configuration files.
yep, thats a per-user location… so you can place it into the default user on a new device and you will be ok - but it wont update for existing users on an existing device… and if you decide to copy in a file for existing users, you risk overwriting the users customisations.
Anyhoo… i get that people here dont get it… thats fine… it was always an extreme longshot.
You don’t have to use the per-user location. You can use a Portable Settings folder, then any user of the app gets the same config files (which has pros and cons).