File Management Tips

From Audacity Wiki

[edit] Project files and folders

[edit] What is an Audacity project?

Saving an Audacity project lets you save unfinished work and re-open it later in Audacity exactly as it was, with all edits and recorded/imported tracks preserved. This is a different process from using one of the Export commands in the File Menu. Export creates an audio file like WAV or MP3. Use Export whenever you want to hear your work in media players or to burn CDs, because no other programs can open Audacity project files.

There is no need to save a project. If you don't, the necessary audio data is stored in the temporary folder specified in the Directories tab of Preferences until exiting the program. At that point, Audacity offers the choice of saving a project or not.

Some benefits of saving a project:

• No need to re-import or re-record files
• Fast loading, even of multiple long tracks
• Audio data always preserved in lossless quality. This is useful if you have already exported to a lossy audio format like MP3 but decide to edit the file further. Editing and re-exporting the project saves the additional quality loss of re-editing the exported MP3.

When you save an Audacity project, it creates two items inside the folder you specified for the project:

• a _data folder bearing the name of the project, containing its audio data (in the form of many 1 MB-sized uncompressed .au files).
• an .aup project file bearing the same project name, which is merely a text file that references the _data folder.

To reopen a saved Audacity project, click File > Open and open the saved .aup file (not the .au files in the _data folder).

In the event of there being no saved .aup file (for example, because of a crash or power outage), see our crash recovery page.

Although you can share Audacity projects with people on other computers, it's necessary to send the other user both the .aup file and the _data folder, and the _data folder must contain a full copy of any imported files that the project contains. As the _data folder can become very large, it's often better to export a compressed file like MP3 and send that instead.

Audacity projects should not be used for long-term storage of audio. When you are completely satisfied with your exported file(s) and are certain you won't need to export further files from the project, delete the .aup file. the .aup.bak backup file (if there is one), and the _data folder, to save disc space.

[edit] Moving and renaming project files and folders

As the .aup file references the _data folder, both must be kept together inside the same folder in which you created the project. If you want to move either the .aup file or the _data folder, you must move both to the same new location.

For the same reasons, you should not rename the _data folder, even if you leave it in the same folder it was created in. If you want to rename an existing project, the safest way is to do it in Audacity, which creates a new .aup file and matching _data folder with your chosen name:

1. Click File > Save Project As...
2. In the "Save Project As:" dialogue, enter the new name for the project in the "File name" box. Audacity will offer you the current name of the .aup file, so overwrite it with your new chosen name.
3. Click the "Save" button.

To avoid confusion between the differently named versions of the same project, delete the previous .aup file and .aup.bak file (if any), together with the previous _data folder. The only legitimate reason for keeping the original project file and folder would be if you wanted to retain a snapshot of your project at a particular point in time before making further edits in the renamed project. If you do this, we recommend giving the renamed project the same name, but differentiating it by including a version number in the name.

Note that if you absolutely know what you are doing, you *can* rename the .aup file to another name, as long as you keep the original name of the _data folder, but this is not recommended. If you do want to rename the Project manually and have the _data folder carry the revised Project name, then you have to edit the .aup file in a text editor to reflect the new name of the _data folder. Again, this is not recommended unless you know exactly what you are doing. To change the name of the _data folder in the .aup file, look for the second line near the top of the file that starts

and change the text inside the quotes. For example, if you renamed your .aup file to newname.aup, the start of the second line of the .aup file should be changed to:

[edit] Avoiding loss of project audio due to missing dependent file

1.2.x and 1.3.0/1.3.1 (Beta) versions of Audacity.

By default, Audacity imports uncompressed files such as WAV or AIFF by reading them directly from the file. This is normal practice with media editors and both speeds up the import considerably and avoids the rapid consumption of disc space that copying the file would involve. However, this means that you need to keep the imported WAV or AIFF file available for Audacity to use in the exact file path it existed in when you imported it.

Therefore the project will have either no sound, or sound only in places, if you do any of these:

• move the WAV or AIFF file to another location
• delete it
• rename it
• disconnect the removable source it resides on
• open the project on another computer without copying the dependent WAV or AIFF to the same path on that computer

This is true even though the waveform is visible on the screen, because the waveform is only a representation of the audio made when it was first imported. Any regions that do have sound will be those edited while the original audio file was still in place.

To correct this situation, open the .aup Project file in a text editor such as Notepad. The file(s) originally used to read data into the project are marked in the .aup file as "aliasfile". Use the text editor's "Find" function to search for "aliasfile" (without quotes), and note the full path to these files that is stated in the .aup file e.g. aliasfile='C:\My Music\Music22.wav'

Restoring the files noted as aliasfiles to the exact path noted in the .aup file, will restore full sound to the project.

To avoid this problem in future when importing uncompressed files, either retain the original audio file (in its correct location) or set Audacity to make a copy of the file, which will then be stored in the Project's _data folder when the Project is saved. Set Audacity to make a copy of the imported file by going to the Preferences > File Formats tab > "when importing uncompressed audio...." section and check the radio button "make a copy of the file before editing (safer)".

Note: this issue does not arise if importing compressed data such as an MP3 or OGG file, as Audacity automatically makes a copy upon import.

1.3.2 and later Beta versions of Audacity

In Beta versions 1.3.2 onwards, Audacity will by default show a dialogue every time a saved project depends on other audio files. This provides the option to copy dependent files into the project to make it self-contained. The dialogue also gives options to always copy data into the Project, never do so, or always ask what to do. These three options can also be accessed at Preferences > File Formats tab exactly as in 1.2.x. Note: This tab is called "Import / Export" in Audacity 1.3.5 and later.

[edit] File and folder errors

[edit] Directory write-protected or disk full error when writing WAV/AIFF

This tip applies to 1.2.x and 1.3.0/1.3.1 versions of Audacity.

You will receive the above error if you both:

• when importing uncompressed audio data such as a WAV or AIFF file, use Audacity's default behaviour of reading the data directly from the original file, and
• export your Project's audio data to the same file name and directory as the file you imported

The problem occurs because Audacity cannot delete the original file in order to overwrite it when it is already reading it. (This issue does not arise if importing a compressed audio file such as an MP3 file, because in the case of compressed audio Audacity automatically makes a copy upon import.)

To avoid this problem in 1.2.6, either

• save the exported WAV or AIFF to another file name or another directory, or
• set Audacity to make a copy of the imported file at Preferences > File Formats tab > "when importing uncompressed audio...." section: check the radio button "make a copy of the file before editing (safer)". Exit and restart Audacity to have the change take effect.

In 1.3.2 and later Beta versions of Audacity, this problem is handled differently, and the steps needed in 1.2.6 are not needed. If Audacity is set to make a copy of the original file, you can overwrite the original file just as in 1.2.6. If Audacity is set to read directly from the original file, it will rename the original file by appending "-old1" to its file name, allowing you to export the edited audio as the original filename. Once you are happy with the newly exported file, delete the original file with the "-old1" suffix.

[edit] Error importing file with spaces in filename from right-click context menu

This error occurs on Windows with all versions of Audacity, when creating a custom right-click Explorer context menu item for a particular file type, using the "Folder Options" applet in the Windows Control Panel. Custom context menus can be useful, for example they provide a way to you edit WAV files with Audacity but leave the default double-click action to play the file with Windows Media Player. The error gives multiple warnings that files cannot be opened for each word of the file name. Note this error does not occur when using the Windows built-in "Open With" context menu item. To correct this problem in pre-Vista versions of Windows:

1. Click Windows Start button > (Settings) > Control Panel > Folder Options.
2. Click on the File Types tab.
3. Navigate to the file extension for your context menu item, e.g. WAV, and click "Advanced"
4. In the "Actions" window, select your right-click menu command and click "Edit"
5. In "Application used to perform action", enclose the %1 after the path inside quotes, for example:
   "C:\Program Files\Audacity 13 Beta\audacity.exe" "%1"
6. Click OK, OK and Close.

Vista lacks any direct way to either create or edit custom context menu items, so to create such you will need a third party application. You can try File Type Doctor from Creative Element Power Tools  (shareware) or Fast Explorer  (freeware - but to edit any existing context menu such as those added by other programs, you have to delete them then recreate them).

As an alternative workaround to stop Audacity trying to open each word of a file as a separate file, for each file you want to open from your context menu, replace the spaces in the filename with an underscore e.g.

C:\Multimedia\audio_files\very_beautiful_melodies.wav

There is also another way to open a file without having to launch Audacity first and use its "Import Audio" command. This is to drag the file onto the Audacity icon (for example, on your desktop or in your Program_Files folder).

[edit] Error opening multiple files from right-click context menu

Using 1.2.x versions of Audacity under Windows, you cannot right-click and open multiple files using a custom context menu, or right-click and open any files once Audacity is already running; this will give an "Audacity already running" error. To open multiple files from right-click, or open them from right-click when Audacity is already running, use the current Beta version of Audacity.