OS: Windows 10 Professional.
I'm working on some video soundtracks, and have noticed some issues when working with Sound Forge mixed audio-video projects.
Project "save" command acts like "save as"
When you click the "Save" button or menu item, instead of simply saving the project, it acts like "Save As...", opening a file dialog, and forcing you to overwrite the existing project file with a confirmation dialog. This seems a bit ridiculous, as it drastically slows down the normal workflow, in which it is prudent to save often.
Render As dialog doesn't remember previous render target
When I want to render the soundtrack I'm working on, this dialog always defaults to "avi". It should remember the last file type I rendered as. Ideally, I'd like to have a "render" command that remembers this information and no longer asks me. Barring that, it would be nice if the settings were persistent and I didn't constantly have to select the type of type I want to render. This is also somewhat related to the next issue...
Render As (save as) dialog shares previous type info with Save As command.
After you Render As, say, to a wave file, the next time you click on Save (project) (which, again, incorrectly acts like Save As), it shows you a default type of a wave file. The default file type persistence should be context sensitive to the command, not shared for all uses of the dialog. That is, the last type used for Save As and for Render As shouldn't be shared between these two commands.
(Wishlist) Add support for Matroska (mkv) containers.
I'd love to hear if you have any plans addressing these issue. The first one seems particularly egregious, IMO.