File manager context menus
- 1 Loss of audio in Project due to missing dependent file
- 2 Directory write-protected or disk full error when writing WAV/AIFF
- 3 Error importing file with spaces in filename from right-click context menu
- 4 Error opening more than one file from right-click context menu
- 5 Moving and renaming Project files and folders
Loss of audio in Project 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.
If you do any of these:
- move the file to another location
- delete it
- rename it
- do not make accessible the removable source it resides on
you will find your Project will have either no sound, or sound only in places, even though you can see the waveform on the screen. If there is sound in any of the Project, this will be only in those sections where you edited the Project while the original audio was in place. Where you did this, Audacity saved that edited data in the Project folder.If you are in this situation, simply open the .aup Project file in a text editor such as Notepad. The file(s) that you 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 noted in the .aup file e.g.
If you can restore the files noted as aliasfiles to the exact path noted in the .aup file, the Project will have full sound again.
To avoid this problem in future when importing uncompressed files, either retain the original audio file 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 File Formats tab of Preferences: "when importing uncompressed audio....", 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 by default will show a dialogue every time you save a Project if it's dependent on other audio files, and give you the option of copying them into the Project so that it's self-contained. The dialogue also gives you the option to always copy data into the Project, never do so, or always ask what to do. These three options can also be accessed on theexactly as in 1.2.x.
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 your exported .WAV or .AIFF to another file name or another directory, or
- set Audacity to make a copy of the imported file. You do this on the File Formats tab of Preferences: "when importing uncompressed audio....", check the radio button "make a copy of the file before editing (safer)". HINT: You need to exit and restart Audacity before this Preference change takes effect.
In 1.3.2 and later Beta versions of Audacity, this problem is handled differently, and you do not need to take the steps necessary in 1.2.6 as above. If you have Audacity set to make a copy of the original file, you can overwrite the original file just as in 1.2.6. If you have Audacity set to read directly from the original file, it will rename the original file by appending "-old1" to its filename, allowing you to export the edited audio as the original filename. Once you are happy with the newly exported file, simply delete the original file with the "-old1" appendage.
This error occurs on pre-Vista versions of Windows with all versions of Audacity, when you create a custom right-click Explorer context menu item for a particular file type, using the "Folder Options" applet in the Windows Control Panel. For example you might want to create a custom context menu item to edit .WAV files with Audacity, but leave the default action when you double-click a .WAV file such that it plays with Windows Media Player. The symptoms of the error are that Audacity gives multiple warnings that it cannot open files which each have a name corresponding to one 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:
- Click Windows Start button > (Settings) > Control Panel > Folder Options.
- Click on the File Types tab
- Navigate to the file extension for your context menu item e.g. WAV and click "Advanced"
- In the "Actions" window, select your right-click menu command and click "Edit"
- 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"
- Click OK, OK and Close.
Now you can right-click over the file in Explorer, click your context menu item and the file will import properly.
Unfortunately, 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 theor (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 workround 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.
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 (e.g. on your desktop or in your Program_Files folder).
Using 1.2.x versions of Audacity under Windows, you cannot right-click and open multiple files using your custom context menu, or right-click and open any files once Audacity is already running; you will simply receive an "Audacity already running" error. If you need to open multiple files from right-click, or open them from right-click when Audacity is already running, you will need to use theEven then (due to a current bug), if you import multiple files from right-click, Audacity will import each file after the first one twice.