• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Studio One asks to save a song when no changes were made?

M

Mark111

New member
Hello all. I am a long time Studio One user, since the beginning actually with a Firestation, then a Firestudio Tube, and now with a RME Fireface 802. Studio One is fantastic, easy to use, and most importantly super stable.
I realize that first time posters are always "suspect" so yes, I did a search of "save behavior" before posting this question/comment and didn't find anything relevant to my question.

I have noticed that if you open a song in Studio One (current on v6) and then immediately save it Studio One will ask if you want to save the file, which is kind of a time waster, especially if you have been shuffling around to say 8 or 10 songs and did save each one after the last move.

Gemini AI is telling me for some reason there is a "dirty flag" indicating a save is required due to something like a rounding error in a plugin (perhaps a value of 0.000001 changed to 0.00002) changing upon opening.

This behavior is most annoying when working in the mastering module because if you do perform the save on the otherwise unchanged song file then the next time you open the mastering module for that project it will demand a re-rerender of each song file, which can be a long process, especially when you have computationally intensive plugins, like the Relab 176 compressor all over the songs in question.

Anyway, is there a way to prevent this behavior unless something on the GUI was actually changed?

Thanks or having a look!

Mark
 
Mark111 said:
Anyway, is there a way to prevent this behavior unless something on the GUI was actually changed?
Click to expand...

My best guess (and it is a guess!) is there's something in the song that changes, like when you open the file a gate that was closed when you saved the file defaults to being open when when you open the file.

As to the mastering page, you don't have to re-render the file in order to make changes on the master file if you haven't made changes in the song. The mastering and song pages are linked, but independent. Eventually it's a good idea to re-render the file, but you can even save out a digital release or whatever from the master page without re-rendering.
 
Thanks for the reply. Yes, obviously something is changing when the song file is open that is signaling Studio One it should be saved. The strange thing is if I look at the "save" dialog before saving it's greyed out, meaning "nothing changed here!" Yes when you close the file it asks if you want to save.

I am thinking, and this is also a guess, that the Studio One designers are very paranoid about people losing their work and they would rather err on the side of saving too often rather than not having someone save a file they should have. I can understand that but perhaps there would be a way to turn this behavior off unless something has been physically changed in the GUI as a preferences setting?

Oh well, at the end of the day it's a minor annoyance in an otherwise rock solid and fantastic program. I have to say Studio One combined with the RME drivers are an unbelievably reliable and solid combination. I mean like a crash or freeze every couple years... maybe? I can't even remember the last time I had a problem honestly.
 
When you see the asterisk next to the title name at top, a change has occurred. For example, adjust the time scale along the top. You haven't effectively changed the song, but Studio One now adjusts to that newly changed scaled or relocated view.
Another possibility might be a modulation wheel on a synth is being read. Something you wouldn't anticipate is a change, but it is.
Don't worry about it as there's no way to change this behavior unless you some how note the actual issue. Not revealing enough info, but a pain? Yes, I guess.
 
Welcome to the forum!

Mark111 said:
Anyway, is there a way to prevent this behavior unless something on the GUI was actually changed?
Click to expand...
It really depends on your plug-ins. Some plug-ins randomly report parameter changes to the host (Studio One) which sets the dirty flag. Some already do this right after loading. This can be both instrument or effect plug-ins.

So what you can do is make a backup copy of that song, check which plug-ins are in the song, remove them one by one, save, open the song again and see if it still happens. As soon as the faulty plug-ins are completely removed from the song, the behavior you reported shouldn't occur anymore.
 
Thank you for taking the time to reply. Since this behavior can be replicated by simply opening and then immediatly closing a song file, there is obviously something going on in the background causing the behavior, plugins or whatever. It doesn't really matter because there currently is no workaround and it not the end of the world to click no when being prompted to save. I was only asking here because even after having used this application from its inception I'm still learning and thought there might have been a preference something like "Do not prompt to save if user changes have been made." With an explanation of course of why the word "user" needs to be there.

Seems like the Presonus feature request website is dead?
 
Mark111 said:
I'm getting

400 Bad Request​

Click to expand...
Clear your cookies. They have changed their authentication and cookie structure sometime in the past few months.

Aside: The last time I submitted to that site, my input was deleted. Do you have to be a Pro+ user to actually submit Feature Requests?
 
I suppose I have the opposite perspective . . . 🙃

After working on computers for over half a century, I trust nothing and save everything at least every five minutes, if not more frequently.

Many times, I want to save the current Studio One ".song"; but "Save" is grayed, hence I cannot do a save, even if nothing appears to have changed.

So, I tweak something, like showing or hiding a Graphic User Interface (GUI) item or adjusting a channel volume slider from 0dB to another value and back to 0dB, which then enables the "Save" menu item.

Something so simple as showing or hiding the "Edit", "Mix", or "Browse" window also works nicely.

I copy the current song to a USB flash drive every 10 or so minutes, mostly in case the local electric service stops working or there is a nearby lightning strike, including the local electric service folks occasionally "toggling" the electric service for a second or two while working on a nearby electric line or perhaps just to let everyone know they have ultimate power over power.

Sometimes, the electric power goes "out" for just a second, which is enough to cause the computer to shutdown.

GOOD TIMES
 
Last edited:
Surf.Whammy said:
I suppose I have the opposite perspective . . . 🙃

After working on computers for over half a century, I trust nothing and save everything at least every five minutes, if not more frequently.

Many times, I want to save the current Studio One ".song"; but "Save" is grayed, hence I cannot do a save, even if nothing appears to have changed.

So, I tweak something, like showing or hiding a Graphic User Interface (GUI) item or adjusting a channel volume slider from 0dB to another value and then back to 0dB, which then enables the "Save" menu item.

Something so simple as showing or hiding the "Edit" window also works nicely.

I also copy the current song to a USB flash drive every few minutes, mostly in case the local electric service stops working or there is a nearby lightning strike, including the local electric service folks occasionally "toggling" the electric service for a second or two while working on a nearby electric line or perhaps just to let everyone know they have ultimate power over power.

Sometimes, the electric power goes "out" for just a second, which is enough to cause the computer to shutdown.

GOOD TIMES
Click to expand...
I'm same mostly, but when working on Projects this can be a major time waster.
 
You must log in or register to reply here.
Back
Top