I see the same here on cubase and it does not annoy me but confuses me in to thinking about if a changed anything to the project and indeed need to save it. It will ask even if I do: save the project, then export audio mixdown without changing anything in the export settings (I never add a mixdown to the pool) and the quit. Then it asks to save.
I always do an incremental save (ctrl alt S), so the do you want to save question is not to useful anyway.
1 Like
I think you can look at it from a different perspective. Basically someone has to figure out a way to decide which actions should not trigger this behavior, and once that’s done it has to all be documented.
I get your point, if the program is in the same one state, practically, after you have toggled something on/off or off/on from our perspective ‘what is there to save?’. From the program’s perspective however perhaps a flag is set somewhere that there has been a change and it happened during your first action - the first on or off - and then that flag remained set. So the programmers would have to come up with some table or something that lowers that flag if the same action happens again.
But then think of a “circle” of actions and not just two of them. You select something, you open a window, you locate on the timeline, you deselect that thing, you close that window, you go back to the previous location on the timeline… in order for the program to know it’s the same state as before it would need to remember each state along all actions to realize that when you close the program it is in a place you were earlier and everything after was “undone”. At least that’s how it looks to me without having coffee yet, and it seems unwieldly from a programming standpoint. We’d just end up with a bunch of saves in the background.
So the short version that I’m getting at is that it’s probably safer to just have the software throw up that flag as soon as anything happens and leave it at that.
Lastly: IF there were exceptions to the behavior we have now we would need a list of every actinon that does not trigger the “save” question. Because if we don’t know that it is any action that triggers it we’ll need to know exactly what doesn’t so we don’t lose something we wanted to save. Obviously we could always save when we do something we want to keep, but sometimes people forget. I think it could be problematic.
2 Likes
You keep argueing this, now with an added strange take on the validity of the knowledge of forum participants on the basis of their employment status, but you fail to test the issue methodically as has been pointed out here more than once. A dev has asked you for a screenshot twice and you haven’t provided nor responded. Some people asked you stuff and you gave them half-answers.
Do you want to solve your problem or do you want to just complain and act superior?
If it is the latter, fine by me, I’ll gladly leave you be. But if you want to dig deeper, try to solve your issue and leave a constructive topic for others to find, you can start by:
- testing if the prompt happens if you just open and close the same session;
- testing if this happens on all your sessions or just some;
- testing if there is one or a few plugins that you use that can be triggering the prompt, due to an ever-changing internal state.
I’m sure after this there would be more stuff you can try, but these steps would remove a lot of variables already.
1 Like
Why is the onus on the end user to provide a screen capture?
It is so common these days, to up-front ask for this just because it is easy these days with devices, so unless it is necessary; I do not subscribe since there is no issue, other than there needing to be a review as has been nicely pointed out in the previous reply.
Saying that though, I get your original point, that more is likely better than less, because plenty of times I have been caught out hitting the “x” close button for the program, thinking that I am in an editor but I am not, which shows SB have been making great strides in relation to allowing multiple interfaces for editing but I am questioning what is frivolous, lazy programming versus what might genuinely be reviewed as part of continuous improvement, which I doubt would be a foreign concept to a “professional”, so-called or otherwise
It is not an onus. He found behaviour that, although for him is anomalous, for other users is expected and even desireable. How else do you expect a developer should persue this issue?
The screenshot is so the developer can see the export configurations and tell if there is anything there to explain the issue, or if it is a bug, or whatever.
Or are you suggesting that the developer should start testing all the possible setups trying to find something that is not even a bug, although it maybe a slight annoyance for some?
EDIT: Oh, I just realized that you are the OP. I replied via email and your name was displayed instead of your username. You have a serious case of “selective hearing”, don’t you? I’m done. Good luck!
This might be the most non-debatable topic I’ve ever seen on this forum…If you are opening a project to do a quick export, or checking on something while making no changes, just close and click don’t save…As someone else said it takes half a second, and you already know you are not saving the project. Calling out “forum staff” and using the word “amateurs” over such a basic function, all while people are actually trying to hear you out / help…yikes 
4 Likes
Can you block people on here? 