Quiet, annoying, when all you have done is open a project, only to immediately render an audio file.
The Project functionality, I believe should be more akin to something like WaveLab, in this regard, so users aren’t asked to do something unnecessarily.
Hi,
What do you mean by rendering audio files? Do you mean Render in Place? Or do you mean Export Audio Mixdown?
Can’t really understand what is the behaviour you’re referring to. Do you mean when creating a new empty project file? Nuendo asking for a location to save it?
I think what they are seeing is:
Hi,
What do you mean by export project, please? Do you mean Export Audio Mixdown?
Could you attach a screenshot of the setting?
I too am confused about the words used.
Hi Martin,
I mean:
For some reason, just because I have initiated a render function via Audio Export, the program(s) assume(s) I have done something that requires a save, this is the behaviour I would like to see changed, to be more like how WaveLab handles projects.
Cheers
As far as I know, the Export Audio Mixdown settings are saved in the project file. Might explain why it asks you to save upon utilizing that window in any way.
Can we get some screenshots?
I’ve never seen this.
If I do an Export Audio, it’s going to ask for a location where the file should be saved.
If this is what @emotive is referring to then I don’t see how it can be avoided. The exported file has to go somewhere, no?
Also have you chosen to import the audio file after exporting? That would create an audio file in the pool and prompt a save.
Please, see my post . We don’t need less saving, we need more saving.
I’m not changing any settings, just File > Export >Audio Mixdown so no changing of the path, filename or any paramaters related to the file being exported.
In relation to inadvertently closing a project, it has happened to me that when editing Tempo in the project page, that for a moment I think I am in the tempo editor but alas I am not and the project closes but other than that I don’t believe changing this situation would really help with data loss.
Hi,
How is it set up on your side? Could you attach a screenshot, please?
Oh, thinking more about it, most of my projects always ask if I want to save before closing, no matter if I made a any changes or if I just saved.
That is because some plugins are always changing internal states, so there are always changes going on to be saved.
I haven’t really pinpointed to a specific plugin, I believe a lot of them do the same thing.
Maybe thats the case with your project? Have you tried just opening and closing, without exporting, to see what happens?
This. If there’s any change of state at all, even highlighting a track or moving a window half an inch, you will be prompted to save the project.
However, @emotive has still not confirmed the problem they’re complaining about. They have not actually stated that the project save dialog is the issue. Everyone has just assumed that.
I am just removing a file from the queue, and then re-adding it since marker positions may have changed, unless that isn’t an issue.
If this is the last problem Nuendo has to solve or can be better at, then we live in paradise. Just click on don’t save. Takes you half a second.
If nothing has changed in relation to project data, then why is a save necessary?
Did you try what Henrique asked - to just open and close the project without doing anything?
For me there’s always the question if I want to save if I have changed something. And if I do something like move windows around or close plugins I’m usually asked, and it also includes exports where audio is added to the pool regardless of whether it ends up on a track.
I think this topic, needs debate, simply because how it is, is how it has been, arguably for too long.
What constitutes as a valid action, triggering a save I am not sure but if you can add/remove renders; what is so important when the options in the Export dialog don’t change from render to render in any case.
I would not be surprised, if there are professionals, out there who this behaviour annoys as well but who do not have time to come to this forum and argue it out with what are arguably amateurs or just forum staff who may not interact with the software so deeply.