Hey - I was trying to use the save as default project settings from the project settings dialog, it does not seem to work. When I use that dialog, settings are not loaded on next new project. However, if I save it differently - from the file>save project template and overwrite default file template it works. Can anyone reproduce this? Is the button on the project settings broken? Thanks

So I can't try it on another computer - can someone please confirm that the project settings (save as default) is or is not working? I know that this used to work. Do I need more details? When I try to use this button, it does not remember my settings, like file type and bit depth on default template.

"Save as default project" works, but not for all project settings. Not sure if bug or by design, but I never use(d) this button since finding out project template stores all the data anyway. e

You know that you need to open an empty project to see the new defaults, right? (Otherwise it loads the last settings saved with the current project of course.) Other than that, that usually means REAPER can't write to REAPER.ini (due to a permission problem) and shouldn't save any changes in Preferences either unless you run REAPER as administrator.

Ok - when I open a new project - doesn't it loads the default template? How would I know if it has trouble writing to the ini file if there is no dialog telling me there is a problem when I press that save button? What loads when new project, empty or default? Where is empty? Is it something I set somewhere in preferences and I did not see that? Which settings from this dialog are remembered? File type? Media locations?

If you set REAPER to load a project template on startup in Preferences, it will load the template and you need to save the template after changing the Project Settings, not the Project Settings defaults (projects override the defaults with their own Project Settings). Hence the defaults saved with that button are only loading with an empty project.

Ok - I understand now. Empty. Not default, which seems weird to me. Shouldn't default be the default project that loads? The button works - not a bug.

maybe you got it already... what Ollie is trying to explain is: you create a default project that is whatever and save that as the default template, and set reaper to load that on start up... then the FIRST thing you NEED to do is a 'save as' to a diff name and location, such as MY NEXT PROJECT... otherwise you will be overwriting the 'blank' template... you see?

Thanks Hopi - I think I "get" it now. Although - someone new might not, BTW I am far from new. That doesn't mean I'm not stupid... Doesn't the common use of default for computer programs normally mean that opens first without intervention. I realize this is my own prejudice and expectation on convention. I can't tell you how mad I was when Word/Excel(I use it at work) changed their menus - omg. enter rant... I get proficient at the structure of the program and how it works... I open the new version and EVERYTHING has moved... UGH!!!!!! I used to be able to do things quickly, now I have to learn a whole new place... sheesh! I must be getting old or something. If it ain't broke don't fix it - unless it makes something more efficient. Then of course they don't contact ME for my input on efficiency. AND they make it more resource intensive. Whew.... end of rant. Sorry about that. I still think default should be default (the old idea of default).

So my problem is I defined a default project and saved a template called default.whatever the template extension is. I assumed - incorrectly, that the button would write to that template. Oops.