Right now when you hit Save it prompts you for a file name. This is effectively "Save As" in most software products.

Save should quickly and easily save the current preset without prompting for a file name. Especially if you have a lot of presets unless you are really careful you can accidentally pick the wrong one and over write your preset the way it is now.

Every event I run, gets its own vMix project file. Even if there are 2 days with same preset, both get a file with the running date. If the day ends, I save the preset and set it as Read Only. No accidental overwrites ever.

But do I agree with the FR? Yes.

+1

I agree with doggy, for example we have a preset as a template for a routine production, and sometimes we need to add custom inputs due to the circumstances (might be a video or audio files), we don't want the operator to mess with the original template. So the "Save As" button is the saviour.

Annoying that this is still wrong in version 27!

Save should overwrite the current project. Then exiting should NOT prompt to save again unless concrete changes have been made (to inputs/settings).

Currently exiting after saving is still prompting to save, this has many times caused people remotely accessing to save and choose the wrong project name.

But in addition to this, if you do make a change and the do LOAD it then doesn't prompt to you to save the change you made.

In all respects this counterintuitive to the way other applications handle Save and Save-as. VMIX should behave like say Notepad, save saves to current loaded location, save-as prompts for new name, close or load should know if a change has been made (other than some internal play position or timer) and prompt to save changes. This did used to work!

Please fix this in this version, and version 25 and 26 as we can't afford to buy updates for two dozen different machines. I think in version 24 behaviour was as expected.