How to be sure project is saved?

[dgpretzel]

Sir:

Audacity 2.3.3
Windows 7

I find it very frustrating to get those "orphan block" messages upon opening a project that I am working on. I lose a tremendous amount of time with these things.

I suspect it happens because, at the end of a session, I usually click on Save Project, and then Exit. But, I don't know how to determine how long I need to wait to have assurance that the data is saved. It's annoying enough when starting, because I usually get a "not responding" message (presumably from Windows), but, it always "comes back alive" after a minute, or so, of loading. When that happens, I know it's all OK to proceed, But, when saving before exiting, I don't know how to determine when it is safe to exit.

I would suggest adding a thermometer bar, or something similar, to inform users when it is safe to exit. Or, alternately, disable "exit" until the save is complete. IOW,make data saving like a database transaction-- it is guaranteed to be either 100% or 0% successful.

It isn't practical to check the project by listening because I record concerts, and typically have several stereo pairs and several spot mics, and I would have to listen to each track completely. My tracks are typically 2 hours long (concerts usually run that long). So, when I get these, I have to start all over.

Is there a "safe harbor" operating procedure that will let me save and exit without losing data?

Thank you.

DG

[dgpretzel]

I'm really not trying to be obnoxious... I would just like to know if there is a way to know when it is safe to exit, after clicking "Save Project".

How does one know?

Thank you.

DG

[DVDdoug]

Is there a "safe harbor" operating procedure that will let me save and exit without losing data?

I'd recommend exporting to WAV whether you make an AUP project or not.

[waxcylinder]

I'm really not trying to be obnoxious... I would just like to know if there is a way to know when it is safe to exit, after clicking "Save Project".

How does one know?

Because if you try to exit/close Audacity with an unsaved project (technically a "dirty" project) Audacity will warn you and ask if you want to save it before exiting.

This annoys some people - they find the fact that they have to click "No" a bit tiresome - but we regard it as an important safety measure to help folk avoid losing project work.

WC

[kozikowski]

I'd recommend exporting to WAV whether you make an AUP project or not.

That's how I do it. That doesn't work with muli-track shows. There is no multi-track WAV.

You can also Save a Lossless Project. That produces a regular Audacity project with additional super-high quality sound files for each track. There was a recent post from someone who did that and was able to rescue their show even though the actual Project structure failed.

The down side of Lossless is the size. They're enormous.

Koz

[dgpretzel]

"Because if you try to exit/close Audacity with an unsaved project (technically a "dirty" project) Audacity will warn you and ask if you want to save it before exiting."

This would be great, but I never experienced it. But, I have had orphaned files twice with this current project. I mean, everything is good. It loads. I do a ton of work. I click Save Project, then Exit. The next day I open the project, and have orphan files. I figured I must have Exited too soon.

This has happened twice.

In the past two years, this has happened a couple more times. No problems with any other files associated with any other programs. Just irregular problems with Audacity data.

Thank you for taking the time to respond.

Regards,

DG

[dgpretzel]

I'd recommend exporting to WAV whether you make an AUP project or not.

That's how I do it. That doesn't work with muli-track shows. There is no multi-track WAV.

You can also Save a Lossless Project. That produces a regular Audacity project with additional super-high quality sound files for each track. There was a recent post from someone who did that and was able to rescue their show even though the actual Project structure failed.

The down side of Lossless is the size. They're enormous.

Koz

Thank you for the suggestion.

I have plenty of space on the drive I am using for the Audacity projects. I will try your suggestion to use the Lossless option.

DG


P.S. I record with hardware that natively produces 32-bit float data files. I import those files directly into Audacity, and I manipulate them as 32-bit float. So, do I understand you to be saying that saving the files as lossless results in output data that is more accurate than what was input and processed? I'm not sure I understand how the output encoding (or lack thereof) can increase the accuracy over what was input and subsequently processed. Or maybe I am just not properly understanding how Audacity works. Thank you, again.

P.P.S. I love recording 32-bit float. Being freed from having to worry about clipping while recording is more convenient, and saves time. I just started recording this way a few months ago, when I bought some new gear. Before that, I recorded in 24-bit, and, of course, set levels to avoid clipping. I had occasional orphan files with those data files, too.

P.P.P.S. It might have something do to with the length of the files. I THINK I experience it more with longer concerts.

P.P.P.P.S. Is there any way to listen to the orphan files. If I could hear them, maybe I could tell whether they were debris from the "cutting room floor". If that be the case, I could ignore them and continue on without having to start over.

[steve]

The down side of Lossless is the size. They're enormous.

Compared to a mixed down audio file, yes they are enormous.
Compared to a normal Audacity project, they're usually about the same size.

Lossless copies are primarily intended for making backups. The main difference between a normal project and a "lossless copy" is that instead of the audio data being thousands of little .AU files, each track is rendered to a perfect quality (lossless) 32-bit float WAV file. https://manual.audacityteam.org/man/fil ... of_project

[kozikowski]

when I bought some new gear.

Whose name and model numbers are? This is a constant and historic problem with people doing wild, live recording.

It's generally not the digital file structure that causes problems. The analog part of the system has very strict limits and that's what usually creates distortions. The noise volume is here and overload is here. It's a relatively narrow range and they're both fixed. Doesn't matter how many bits you divide it into or their configuration.

I do know of one system that could get around this. One of my favorite show producers claimed he had a new microphone system that made two different recordings at the same time. All he had to do was get the recording volume roughly in the ballpark and the system would do the rest.

Is that what you have?

Koz

[kozikowski]

Compared to a normal Audacity project, they're usually about the same size.

I saved a project and a lossless project of the same show. The project _DATA folder was 321MB and the lossless was 635MB.

Koz