Audacity Forum

I just realized that it was both DVDdoug and jademan who specifically used the term structure ("...the structure straight", etc.) when discussing this issue of backing up Audacity projects. My apologies for the mix up.

And steve And DVDdoug.

4DanQuestt wrote: ↑

Fri Feb 12, 2021 7:59 pm

I do have one question though about the project's data file throughout this process of backing everything up: Does the project's data file actually become modified or changed in any way when I make changes or additions to the project? I would think that it would have to, but, unlike the project's aup file (which, as shown by the new/most recent date associated with it, is modified each time I make changes to the project), this does not appear to be the case. In other words, is the project's data file being modified by Audacity each time I make changes to the project and save it (despite the fact that the only date shown for the project's data file remains unchanged from the day I BEGAN the project? Unless you or someone else tells me that the data file is not modified from the first day/session of a project, I will continue to assume that I need to copy and paste BOTH the aup AND data files together

4DanQuestt,

Please read the following, again. All of it! And don't forget to read the contents of the link! All of it! Thank you. Key words being data files. Note that there is a difference between one data file and hundreds of tiny data files that are contained in a directory tree under a single data folder.

Danger, Will Robinson!

Be sure that you understand the structure of and audacity project. It consists of hundreds of small six-second "wav" files, a file directory structure, and an aup file that contains instructions on where to locate these files and exactly how they are stitched together to create your project.

If you copy only the .aup file and think that is making a backup of the project, you are going to be in for a rude awakening! See here for the Audacity Project structure: https://manual.audacityteam.org/man/aud ... jects.html

Note also as DVDdoug and steve mention that the next release of Audacity will provide a solution to this issue.

I hope this helps!

4DanQuestt wrote: ↑

Thu Feb 11, 2021 4:11 am

am I correct in my understanding that it will be OK for me to copy and paste the project's AUP file into my music folder AS LONG AS I copy and paste the project's data file along with it EACH TIME I back up the project?

Yes, but ensure that Audacity is closed before you do that.

What I generally do when working on important projects:

1. Create a new, empty folder before I start.

2. Save the project into that folder.

Now when I want to copy the project to another location, I copy the "outer" folder (created in step 1) as that contains everything that the project needs.

If copying over a network, I make a ZIP copy of that outer folder (including all of its contents) and copy the ZIP archive. This has the benefit that the project is consolidated into a single file, so ensures that the copy is 100% successful, or fails. For extra peace of mind, a checksum can be used to validate the copy after it has been moved, though in practice, if a ZIP file can be opened without an error message then you can be pretty sure that it's OK.

4DanQuestt wrote: ↑

Fri Feb 12, 2021 7:59 pm

Does the project's data file actually become modified or changed in any way when I make changes or additions to the project?

It's not a "data file", it's a "data folder" (a directory).

The ".aup" is a file. The audio data is in a folder.

There is one AUP (Audacity project file) and one data folder for each project. In the data folder there may be hundreds or thousands of small pieces of audio data (typically about 1 MB each). These small pieces of audio data are called "block files" (or "blockfiles").

When you modify a track (for example, by applying an effect), Audacity creates new blockfiles. The old blockfiles are retained so that you can "Undo" the last step. Audacity has an unlimited number of undo steps, which means that projects can grow very large while you are working on a project.

When the Audacity project is closed, Audacity will clean up and delete all of the old blockfiles that are no longer required by the project. "Undo" is no longer available after the project has been closed.

A full and detailed explanation of how to manage Audacity projects is here: https://manual.audacityteam.org/man/aud ... jects.html
Although rather long, it is well worth reading.

Thank you all for clarifying certain points for me. Now that it's the weekend and I have sufficient time, I will read all of the sections of the Audacity manual that relate to this process. In regard to the concern over avoiding backing up a project when either a file is open or Audacity is running, I always make sure that everything is closed and off before I begin copying and pasting. Once again, many thanks for all the support!