Professional Documents
Culture Documents
Spaces - MhmBVzGzh8SctWQ6jPR PDF Export
Spaces - MhmBVzGzh8SctWQ6jPR PDF Export
Audacity Support
How-Tos and Tutorials for Audacity
Audacity Support still is in a very early stage and under heavy development.
Do check out Contributing to Audacity if you want to add or change some pages.
Installing FFMPEG
Editing audio
Audacity Basics
Downloading & installing Audacity
Audacity is an easy-to-use, multi-track audio editor and recorder for Windows, macOS, GNU/Linux and other
operating systems. This page will guide you through the download & installation process.
Windows
The Microsoft Store app will open. Click Install to install Audacity.
When Windows asks you if the installer may make changes to the system, click Yes.
Audacity is now installed. You can start Audacity from the start menu.
Downloading from the Internet
Head to the download page: https://www.audacityteam.org/download/windows/
It will automatically download the latest version of Audacity after 5 seconds.
If prompted, click Run or Save.
If you clicked Save, head to your downloads, locate the Audacity installer and double-click it.
In Windows 11 it is possible that you get a warning about Audacity being a non
Microsoft-verified app. Click Install anyway.
Windows 11 warning when running Audacity installer
When Windows asks you if the installer may make changes to the system, click Yes.
Select the language to use during the installation and click OK.
In the Information page you will links to learn more about Audacity and its license. Click
Next to proceed.
Information page - Links to learn more about Audacity and its license
In the Select Destination Location page you can select a different folder to install Audacity
using the Browse... button or simply use the recommended destination. Click Next to
continue.
In the Select Additional Tasks page you can choose that the installer adds a shortcut to
Audacity in your Desktop.
If you have installed Audacity previously you will have the option to Reset Preferences.
Select if you want to create a shortcut to open Audacity
Please take some time to know how to get community support through the Audacity Forum
and how to make suggestions or report bugs.
Linux
Note: If you have trouble opening the AppImage, try installing libfuse2. Exact steps
for various distributions can be found at
https://github.com/AppImage/AppImageKit/wiki/FUSE
Installing FFMPEG
FFmpeg allows you import/export additional audio file formats into/from Audacity
Due to patent restrictions, FFMPEG cannot be distributed with Audacity itself. However, FFMPEG is
required to import and export a variety of audio formats, including M4A and WMA.
Note: In previous versions of Audacity, LAME was required to export MP3 files. It is now included
with Audacity by default on Windows and macOS. Make sure you are using the latest version of
Audacity if you're getting any LAME errors.
Windows
Recommended installer
1. Download the FFmpeg installer from a third party site, for example
https://lame.buanzo.org/#lamewindl
For Audacity 3.2.0 download the FFmpeg_for_Audacity_3.2_on_Windows.zip file.
The ZIP file contains both 32-bit and 64-bit versions of the FFmpeg installer. Use the
x86_64.exe installer for 64-bit versions of Audacity or if you are using the 32-bit version
of Audacity, choose the x86.exe installer.
For previous versions like Audacity 3.1.x download the installer FFmpeg v2.2.2
INSTALLER (.EXE) from https://lame.buanzo.org/ffmpeg64audacity.php. If you are using
a 32-bit version of Audacity 3.1.x download the installer ffmpeg-win-2.2.2.exe from
https://lame.buanzo.org/#lamewindl
Audacity should now automatically detect FFMPEG and allow you to use it.
Other FFMPEG builds
If you prefer a manual installation of FFMPEG you can download a ZIP file from a different
source:
https://github.com/BtbN/FFmpeg-Builds/releases
https://www.gyan.dev/ffmpeg/builds/#release-builds
Note:
Audacity 3.1 and later supports avformat-55.dll, avformat-57.dll and avformat-
58.dll. Audacity 3.2 and later supports also avformat-59.dll. You can check which
dll is in which FFMPEG release here.
Make sure you download full FFMPEG copies, not just the avformat-*.dll's
individually. Further, make sure to download or build the shared versions as only
those contain .dll's.
Manual installation
Video guide
If you have installed FFMPEG from a different source, or installed it in a different location, you'll
need to tell Audacity where to find it. To do this:
1. Go to Edit > Preferences > Libraries
2
2.
Click on the Locate... button.
5. Once you've found it, click Open, then OK, then OK again to close the preferences.
macOS
Caution: If you're using an Apple Silicon ("M1", "M2") system, make sure that your
FFMPEG and Audacity architectures match:
arm64 (Apple Silicon) Audacity needs arm64 FFMPEG,
x86_64 (intel, also known as x64 and amd64) Audacity needs x86_64 FFMPEG.
Recommended installer
This is a universal binary installer. It automatically matches your system architecture.
1. Download FFMPEG (FFmpeg_for_Audacity_3.2_on_macOS.pkg) from
https://lame.buanzo.org/#lameosx64bitdl
Homebrew
One way to install an FFMPEG version that matches your system architecture is using
homebrew. To install homebrew, you first need xcode. You can install it through the
Terminal.app by typing in:
xcode-select --install
When XCode is installed, the following command downloads and runs the homebrew installer:
And once you have Homebrew, the following command installs FFMPEG:
Audacity should now automatically detect the installation after a restart. If not, follow the steps of
a manual installation.
Note:
Audacity 3.1 and later supports avformat 55, 57 and 58. Audacity 3.2 and later
supports also avformat 59. On mac, the avformat files usually are called
ffmpeg.5*.64bit.dylib
Make sure to download or build the shared versions (with .dylib's) as only those
can be used by Audacity.
Manual installation
If you have installed FFMPEG from a different source, or installed it in a different location, you'll
need to tell Audacity where to find it. To do this:
On Linux, you generally can install FFMPEG as well as LAME through the package manager.
You can use the following command in your Terminal/Console to install it:
Once you have installed FFMPEG and LAME, restart Audacity. It will automatically try to detect
them.
Manual installation
If your FFMPEG or LAME installation didn't get detected, you'll need to tell Audacity where to
find it. To do this:
5. Once you've found it, click Open, then OK and OK again to close the preferences.
If you have a mic with a 3.5mm jack, plug it into a mic-in port.
If you have an XLR mic, plug it into an XLR-USB audio interface and the interface into the USB port.
The exact details depend on both your exact computer model and your microphone model. Please see their
respective manuals or support pages for further information. You may need adapters if your computer is
missing appropriate ports.
Note: Many Laptops and Notebooks feature built-in microphones. While they may be good
enough to record your voice to an intelligible standard, the recordings they produce tend to be
somewhat unpleasant to listen to.
Use the Audio Setup toolbar to select the microphone you want to record
You may see some unexpected devices here (for example, webcams), as well as virtual devices (software
pretending to be a microphone). Choose the entry that matches the microphone you actually want to use.
You can also use the Audio Setup toolbar to select whether you'll be recording in Mono or Stereo.
The Audio Setup toolbar also displays the number of recording channels available from your microphone
Note: Most microphones are in Mono, and Mono is generally the best choice for recordings. Only
use Stereo if you do need directionality.
Then try to speak in a normal volume. In general, the volume should remain in the green zone throughout (in
general, between -18 and -12 dB is best).
Caution: If your input volume is too low (below -42 dB) or too high (frequently in the red area),
your audio quality will likely suffer. See this page for how to fix this:
Setting recording levels and playback levels
Next, make a test recording. To start recording your voice in Audacity, simply press the red record button.
Transport toolbar: the record button is the second from the right
When you have made the recording, listen back to it. If everything went well, you should now hear your
voice clearly and you should now be able to continue with the next steps.
Common problems
If you run into trouble with any of these steps, you may find the solution here:
Next Steps
Once you've made your recording, make sure to save your work. This applies regardless of whether you
intend on editing it later or not. Saving and exporting projects
If you want to edit your recording afterwards: Editing audio
The recording and playback levels can be set using the sliders in the Recording and Playback meter
toolbars:
Recording meter toolbar and Playback meter toolbar with level sliders
The slider with the microphone icon sets the recording volume on a system level. If the operating system
is prohibiting this action, this slider will be inactive.
The Recording Level slider will change the level of your recording device on a system level
The slider with the speaker icon sets the playback volume relative to the system volume. It does not
affect the volume of exported files, use the gain sliders on each track to edit those.
Best practice: Before starting to record, click on the microphone icon and select Start
Monitoring to activate the recording level meter.
If it enters the yellow or red area (-9 dB to 0 dB) when testing with a normal volume, lower the
recording level to prevent clipping and distortions in the real recording.
Use the recording level slider to reduce the level when it is too high
If you selected 1 (Mono) Recording Channel on the Audio Setup > Recording Channels the
meter will only display the level on the Left channel
Monitoring 1 (Mono) Recording Channel level
Windows
1. Use the Audio Setup toolbar to select Windows WASAPI as the Host and then select the
output you want to use (the device you're using to listen) as the input. It will be marked with a
(loopback) after it's name.
When using the (default) MME device, you may find a virtual microphone called
Stereo Mix, What you hear or similar in it. This also will record your desktop audio.
Selecting Stereo Mix as an alternative to record desktop audio
macOS
https://github.com/mattingalls/Soundflower/releases/
Linux
When using PulseAudio (default for Ubuntu, Linux Mint, and others):
1. Install PulseAudio Volume Control (pavucontrol). This should be in your repository already.
2. Use the Audio Setup toolbar to select ALSA as the audio host and select pulse as the
recording device.
If your system uses Pulse by default, the pulse device may be called default.
3. Enable the recording meter by selecting Start Monitoring.
6. Launch the application that you wish to record and begin playback.
7. In the "Recording" tab of PulseAudio Volume Control, drag the volume sliders so that the
recording level in Audacity's Recording Meter is to left of 0 dB (-6 dB is a good level to aim
for).
DON'T use software playthrough when recording desktop audio. Make sure it's off in the menu:
Transport > Transport Options > Software playthrough (on/off) - The checkmark next to it must
be turned off. You can turn off overdub here as well.
3. Record
Hit the record button to record your desktop audio.
Editing audio
This page is an introduction tutorial to editing in Audacity. It covers how to import files, making cuts,
rearranging clips, and applying effects!
Importing a file
To start editing, you need some sort of sound to edit. You can either record some sound, or import an
existing sound file (for example, an MP3 or WAV) by dragging & dropping it into the project window. You can
also import files via the File > Import menus.
Note: To import proprietary file formats such as M4A or WMA, you need to install FFMPEG first.
Once you have that, you will see a waveform of your sound:
This waveform is a visual representation of the song. The larger the blue "blob" is, the louder the section.
Lines standing alone ("spikes") indicate sudden and short loud sections such as clicks, snaps, claps and
drum hits. With a bit of practice, you can use the waveform to quickly find your way around an audio file.
Hint: You can zoom in using the Zoom+ icon, or by Ctrl+Scroll ( Cmd+Scroll ) to
precisely adjust the beginning and end of the selection.
You can click + drag on the clip handle bar to move a clip around.
Splitting up clips
To split a clip into two independent clips,
1
1.
ClickTo
Tip: into the waveform
make where you zoom
precise adjustments, want toinsplit
first.the clip.
2. Right-click > Split Clip ( Ctrl+I / Cmd+I )
Note: If you select some audio instead, it will create a clip out of the selection.
To trim a clip,
click + drag on
the upper third of
the sides.
Then click and drag the edge to trim the clip to it's desired length.
Note: Trimming is a non-destructive operation. You can un-trim a clip at any time. If you have
created your clip by splitting up a larger clip, you can even un-trim the current clip until it's at the
length of the old clip.
Applying Effects
Audacity supports a wide range of effects and effect plugins. These effects can be used for
Noise reduction & removal and more, and while each effect does different things, they all generally can
be applied in the following way:
3. Select the effect you want to use. Typically, a window like this will open:
4. Tweak the effect to your liking. You can click the Preview button to hear a short sample before applying
it to the whole selection.
Saving projects
You can save projects using the File > Save Project menu. A saved project (.aup3) has the most information
about your project available, but can only be opened in Audacity. There are three options available, each
useful for a different use case:
Save Project ( Ctrl+S / Cmd+S ) will save your current project. If you save for the first time, you may
need to specify where to save it to.
Save Project As... will save your project in a new place and continue editing on it, should you want the
original project to remain untouched.
Backup Project... will save the current state of the project in a new file, but won't switch to it.
Warning: Avoid saving active projects on external drives, USB sticks, or network storage.
Audacity requires fast, uninterrupted access to your storage when recording and editing.
Exporting audio
You can export your project into an audio file using the File > Export menu. Exported audio (.mp3, .wav,
.ogg, and more) can be opened with a wide variety of programs, and uploaded to some social media, but
may have worse quality and lose some Audacity-specific information.
In the File > Export menu, you'll see a few different options:
Note: You may need to install FFMPEG to access some of these options.
Export as MP3, Export as WAV and Export as OGG will export your project into the selected format.
Export Audio... ( Ctrl+Shift+E / Cmd+Shift+E ) will provide you options to export to more
uncommon formats, such as FLAC, M4A, AC3, WMA, AMR, MP2 and custom FFMPEG exports.
Export Selected Audio... will export only the current selection time range, instead of the entire project.
Export Multiple... ( Ctrl+Shift+L / Cmd+Shift+L ) will let you export different parts of the audio
based on either tracks or labels.
Caution: Muted tracks are not exported. What you hear when playing in Audacity is what will be
exported.
There are also two additional options which export non-audio data:
Export MIDI... will export the currently selected note track as a MIDI or Allegro file. You can only export
one note track at a time.
You can now upload your audio by pressing Continue. If you'd like to link an existing audio.com first, you
can do that by clicking Link Account.
Audacity will now prepare the track for upload and upload your audio.
Note: This may take a few minutes depending on how fast your computer is, how fast your
internet connection is, and how long your audio is.
After your audio has been uploaded, press Continue. You will be taken to the audio.com website.
On audio.com you now can either create an account to use this with, or copy the anonymous link. To share
the link,
You now can share your audio by sending this link to people.
All uploaded audio is private by default. Only people with access to the link can listen to it.
6. You may see a popup asking you whether you want to open in Audacity.
Audacity Plugins
Most plugins get automatically activated once you install them on your system.
Caution:
64-bit Audacity can only run 64-bit plugins, and 32-bit Audacity can only run 32-bit plugins.
Additionally, Apple Silicon (arm64) Audacity cannot run Intel (x86-64) plugins and vice versa.
"Instrument" versions of plugins (VSTi, LV2i) are not supported.
Windows
LADSPA: C:\Users\<username>\Appdata\Roaming\audacity\Plug-ins\
macOS
Vamp: /Library/Audio/Plug-Ins/Vamp
Nyquist: See below
Linux
Keyboard shortcuts
This page lists all commands in the Audacity menus and all pre-defined keyboard shortcuts.
The default Standard set of shortcuts is a reduced set, compared to earlier versions of Audacity, to simplify
the set of shortcuts somewhat and to provide greater flexibility for users who wish to create their own
shortcuts. There is also an extended Full set of keyboard shortcuts that can be selected from the Defaults
button on the Keyboard Preferences dialog. This Full set is the set that was available in Audacity 2.1.3 and
earlier. You can use Keyboard Preferences to change or remove existing shortcuts or to assign a shortcut to
commands that lack a default shortcut.
Shortcuts that are only in the Full set are shown like so: Ctrl + # Extra.
Shortcuts that have not been assigned, that you can assign using keyboard preferences, are shown like
so (unassigned).
Some less commonly used commands are not in the default menus but they can be accessed by menu by
enabling Show extra menus in Interface Preferences
Note: You can change all shortcuts via Preferences > Keyboard. This includes adding new
shortcuts, or removing shortcuts existing by default.
Mac users: Ctrl = ⌘ and Alt = Option. So, for example, Ctrl + Alt + K = ⌘ + Option + K.
See Audacity Selection for examples of changing track focus and selection.
PAGE UP scrolls the project rightwards and PAGE DOWN scrolls the project leftwards, equivalent to a
single click in the white area either side of the horizontal scrollbar. These shortcuts cannot be configured
in Keyboard Preferences.
There are a number of key combinations that can be used in combination with mouse clicks. These
cannot be configured. They are listed on Mouse Preferences
File Menu
The File Menu provides commands for creating, opening and saving Audacity projects and importing and
exporting audio files
Lists the full path to the twelve most recently saved or opened projects or most recently imported audio files
File: Export
For exporting audio files
File: Import
Edit Menu
The Edit Menu provides standard edit commands (Undo, Redo, Cut, Copy, Paste and Delete) plus many
other commands specific to editing audio or labels
Create or remove separate clips in the audio track. A clip inside an audio track is a separate section of that
track which has been split so that it can be manipulated somewhat independently of the other clips in the
track.
Edit: Labels
Select Menu
Select Menu has commands that enable you make selections of tracks or parts of the tracks in your project.
Select: Tracks
Tracks
Select: Region
Select: Spectral
Shift+Tab
Tab
View Menu
View Menu has commands that determine the amount of detail you see in all the tracks in the project
window. It also lets you show or hide Toolbars and some additional windows such as Undo History.
Move forward/backwards
Skip to (unassigned)
through the audio
View: Zoom
Zoom in/out on the horizontal axis. Show more detail or show a longer length of time.
View: Skip to
View: Toolbars
Toolbars can be used to determine which of the Audacity toolbars are displayed. By default all toolbars are
shown except Spectral Selection and Scrub
Transport Menu
Transport Menu commands let you play or stop, loop play, scrub play or record (including timed and sound
activated recordings).
Action Shortcut Description
Transport: Playing
These commands control playback in Audacity. You can Start, Stop or Pause playback of the audio in your
project.
Transport: Recording
These commands control recording in Audacity. You can Start, Stop or Pause recording in your project. You
can either start a recording on your existing track or an a new track.
Transport: Scrubbing
Scrubbing is the action of moving the mouse pointer right or left so as to adjust the position, speed or
direction of playback, listening to the audio at the same time - a convenient way to quickly navigate the
waveform to find a particular event of interest. Speed changes are made by rotating the mouse wheel while
scrubbing.
Transport: Cursor to
These commands let you move the cursor to the start or end of the selection, track or any adjacent Clip that
you may have
Transport: Looping
This submenu lets you manage and set various options for transport (playing and recording) in Audacity
Tracks Menu
Tracks Menu provides commands for creating and removing tracks, applying operations to selected tracks
such as mixing, resampling or converting from stereo to mono, and lets you add or edit labels.
Tracks: Mix
Tracks: Mute/Unmute
Tracks: Pan
T k Ali T k
Tracks: Align Tracks
Commands that provide an automatic way of aligning selected tracks with the cursor, the selection, or with
the start of the project.
Sorts all tracks in the project from top to bottom in the project window, by Start Time or by Name.
Generate Menu
Generate Menu lets you create audio containing tones, noise or silence.
Generate: Built-in
Generate: Nyquist
Effect Menu
Audacity includes many built-in effects and also lets you use a wide range of plug-in effects.
Effect: Built-in
A configurable stereo
reverberation effect with built-in
and user-added presets. It can
be used to add ambience (an
Reverb... (unassigned) impression of the space in whic
a sound occurs) to a mono
sound. Also use it to increase
reverberation in stereo audio
that sounds too "dry" or "close"
Effect: Nyquist
Analyze Menu
The Analyze Menu contains tools for finding out about the characteristics of your audio, or labeling key
feature.
Analyze: Nyquist
Action Shortcut Description
Tools Menu
Displays a menu with list of all your Macros. Selecting any of these Macros by clicking on it will cause that
Macro to be applied to the current project.
The Extra menu provides access to additional Commands that are not available in the normal default
Audacity menus.
Extra Transport
Extra: Tools
Extra commands to select the tool, for example time-shift, envelopes, multi-tool.
Extra: Mixer
Extra: Edit
Extra: Seek
Extra: Device
Extra: Selection
Extra: Focus
Extra: Cursor
Extra: Track
These commands were originally written for scripting Audacity, e.g via a Python script that uses mod-script-
pipe. The commands though are also present in the menu, available from macros, and available from within
Nyquist using (AUD-DO "command")
Modify an envelope by
specifying a track or channel
and a time within it. You canno
Set Envelope... (unassigned)
yet delete individual envelope
points, but can delete the whole
envelope using Delete=1.
Extra: Scriptables II
Like Scriptables I, but these ones are less commonly used from the menu.
Help Menu
The Help Menu lets you find out more about the Audacity application and how to use it. It also includes
some diagnostic tools.
Help: Diagnostics
No Menu
Best Practice: While it's possible to rescue an otherwise unusable file with noise reduction
techniques, your recording will sound best if you take steps to ensure a noise-free environment
before recording.
Noise Reduction
The Noise Reduction effect works best to remove a constant source of noise, like the hiss of fans, the hum of
fridges, or whines, whistles and buzzes.
1. Locate a section of your recording that's just your background noise, preferably a few seconds long, and
select it.
2. Go to Effects > Noise Reduction and press the "Get noise profile" button.
3. Select all the audio for which you want to reduce the noise.
4. Go to Effects > Noise Reduction again. You now can tweak the settings of the reduction to your liking.
Tip: While tuning the settings, use the "Residue" toggle to hear what sound will be removed.
5. Once you're satisfied with the result, click OK to apply it to the selected audio.
Note: If you used the Residue toggle before, make sure to switch it back to Reduce before pressing OK.
Tips:
If you set the sensitivity too low, or use a noise profile that doesn't properly represent the
noise throughout your track, you may experience artifacts (random bursts of very short
tones).
If you don't need to tweak the settings after setting the noise profile, you can press
Ctrl+R / Cmd+R to immediately apply the effect to your selection.
Noise Gate
The Noise Gate effect completely removes any sound quieter than a certain threshold while leaving sounds
louder completely unaffected. To use it
Notch Filter
The notch filter removes a hum or whistle at a specific frequency. To use it:
3. Enter the frequency you want to reduce, together with the Q-value (how many frequencies around the
main one you want it to affect - the higher the number, the less frequencies).
Tips:
The "Mains hum" of the electricity grid is 60Hz in north and middle America, and 50Hz in
most other countries.
Use Analyze > Plot Spectrum... to find the offending frequency if you're not sure where it is.
Sounds often have harmonics or overtones. They are at a multiple of the main frequency, so
for a 50Hz sound, you may need to apply the notch filter as well at 100Hz, 150Hz, and so on
to remove it fully.
Re-recording a section
Punch-in repair of recordings is an easy and fast way to fix short sections of a recording by re-recording it.
Best Practice:
Make sure that Overdubbing is turned on in Transport > Transport Options.
Make sure that your latency settings are correct.
If your audio recording broke and you immediately noticed it (for example because you misspoke your script
or had to cough), it is possible to stop the recording and immediately fix the mistake by using Punch-and-roll
recording. To use it:
5. From here on out you can continue recording as usual. If you make the same mistake again, you can
stop the recording and undo (Ctrl+Z / Cmd+Z) and try again. If you make another mistake later on, you
can do another Punch and Roll recording by repeating the steps above.
Tip: You can change the amount of pre-roll audio and crossfade in the Preferences > Recording
in the Punch and Roll recording section.
Best Practice:
Make sure that Overdubbing is turned on and Software Playthrough is turned off. Both
settings can be found in Transport > Transport Options
Always create a backup of your project before editing it. For a continuous recording, this
typically is best done by Exporting audio .
To use it:
1. Select the bad part of the recording and silence it. You can do this by clicking the Silence Audio
Selection button (found next to the undo and cut/copy/paste buttons), or by pressing Ctrl+L
( Cmd+L )
2. Select a couple of seconds of audio before and after the bad part. With overdubbing turned on,
recording will playback the recording back to you and help you match the timing.
3. Do the re-recording on a new track. To do this, Shift-click the record button or press Shift+R . It will
automatically start recording from the beginning of your selection.
Related pages
To hide the cut a bit better, a crossfade may help: Making crossfades
If your new take is slightly longer or shorter than the gap left in the original recording, you can split the
clip: Splitting up clips
You can use a similar technique to continuously fix mistakes as they occur during a recording session
using Latency Compensation
To use it:
If you have rapid soft clicks (such as the crackling of Vinyl), using Noise Reduction may
work better.
Audio Editing
Using realtime effects
Audacity 3.2 and onwards supports realtime effects
2. Click Add effect and choose an available effect from the list.
Note: Realtime effects always apply to an entire track. Since they're calculated realtime, they
won't change the source waveform.
You can change the effect settings by clicking on the effect's name. This will open a settings window, often
with a graphical interface which looks nothing like Audacity itself. You still can interact with the main
Audacity window while the effect settings are open.
Bypassing an effect
You can press the blue power button next to an effect (or the entire effects stack) to bypass it, causing it to be
not applied to your audio.
Tip: If you want to completely remove an effect from the stack, press the triangle next to the
effect name and select "No Effect".
Caution: When selecting several tracks at once, the Mix and Render option will mix all tracks
together.
Audio loops are a type of music that plays a few bars on repeat over and over. They can be created by
taking a sample out of pre-existing content and looping it seamlessly.
1. Enable playback looping
To enable playback looping, simply click onto the loop button (1). When you do this, you'll note the blue
looping region appear in the timeline (2). You can move the region and it's in and out point individually by
dragging it.
Tip: You can always create a new region by dragging anywhere outside the existing region
within the timeline.
When making a loop out of music, you often will be able to see repetitions in the waveform as your source
material will probably contain some loop already (for example a drummer playing the same beat throughout
the song). You can use these to roughly find good looping regions and position your looping region above it.
Notes:
If you're having trouble finding a good region with a stereo track, you may want to convert it to
mono first: Tracks > Mix > Mix Stereo to Mono
When positioning your loop region, try to aim just before the peaks. Doing that may allow you
to skip finetuning altogether.
You can adjust the looping region even when playback is on.
To make the loop seamless, you may need to zoom in some more, using Ctrl+Scroll ( Cmd+Scroll )
or the magnifying glass.
Best practice: Set your looping points at a zero crossing, where the waveform (blue line) crosses
0 (black line):
Once you have the clip, you can copy-paste it anywhere in your project.
Tip: If you want to use the clip on repeat, use Effect > Repeat.
See also:
Crossfading Clips
If you have two clips in one track you'd like to crossfade, you can use Crossfade Clips effect. To use it:
2. Select the region you'd like to apply the crossfade to. Try to select roughly the same amount of time in
both clips.
Note: Any empty space between the clips will be automatically removed and ignored in the crossfade.
1. Position the clips on the tracks so that they overlap in the range you want to crossfade:
2. Select the audio in the first clip in the overlapping region and choose Effects > Fade Out
3. Select the audio in the second clip in the overlapping region and choose Effects > Fade In
Caution: Changing speed without affecting the pitch always leads to artefacts. Avoid repeatedly
applying these effects.
To change the speed while preserving the pitch, select the audio you want to apply the effect on and go to
Effect > Change Tempo
Drag the slider or enter some numbers to change how much you want to speed up or slow down your audio.
The controls are linked, so you just need to change the value you care about, the rest will update
accordingly.
For extreme slowdowns (10x slower to thousands of times slower), you may want to use Effect >
Paulstretch instead.
Note: Paulstretch is only capable of slowing down, so the stretch factor relates to how many
times you want to slow down your audio.
The time resolution decides on whether the algorithm will focus on frequencies and pitch at the
expense of rhythm (high time resolution), or whether it will focus on rhythm at the expense of pitch
(low time resolution). Generally. 0.25 is a good compromise for most music
Unlike Change Tempo, the Change Speed effect keeps the waveform mostly intact, so you can use this
method repeatedly without any major loss in quality.
A Time Track
Then click on the blue line and drag it upwards or downwards to change the speed at that time. Every time
you click, a new control point is added, allowing you to change the speed over time
A time track with control points
Tip: By default, the range goes from 90% to 110% speed. If you want to extend that, right-click
the vertical scale (going from 90-110) and select Range... to set a new range. The new range
may be between 10% and 1000%.
To use it, drag the slider to the desired speed (between 0.01x and 3x) and then click the small play button
next to it to playback your audio at that speed. You can use the normal stop and pause controls to
stop/pause playback.
Note: If you collapse a track or make it vertically smaller, Audacity will hide the pan and volume
sliders from view. To see them again, expand the track by dragging down on it's lower edge.
By default, the icon for each track is the Audacity logo, but it can be changed if the track name contains the
following keywords:
Misc. instruments
String instruments
acoustic guitar, acoustic gtr = acoustic guitar
electric bass, bass, bs = electric bass guitar
Percussion
clap = handclaps
Caution: When rendering, all tracks are added onto each other, which may cause clipping. If this
happens, undo the mix and lower the volume for all of your tracks.
Best Practice: If you have a several stereo tracks, but don't need a stereo-effect for them (ie. any
left/right panning), consider mixing down to mono using Tracks > Mix > Mix Stereo Down to
Mono. Exporting a mono track to a lossy format (like MP3) will let you have a higher quality at the
same bitrate, or let you use a lower bitrate (and thus lower file size) at the same bitrate.
Use the Selection tool to remove unnecessary audio (mostly silence) from the start of the recording.
3. Zoom in until you can see from the start of the track to the start of the music
4. Click and drag from the start of the music to the start of the track
5. Click on Edit > Delete
Similarly, remove unwanted audio from the end of the recording and from the middle (between sides 1 and 2
of the LP or cassette).
Later in this tutorial we mention that you can use the Analyze > Label Sounds... command to
identify spaces between the songs, so when you are editing the transition between side 1 and
side 2 be sure to leave 2 or 3 seconds of silence, similar to what you would find between songs.
Save your work! Click on File > Save Project > Save Project.
1. Using the Selection tool, click near the beginning of the second song
2. Repeatedly click the Zoom In button until you can see just the first few seconds of the song
4. Click on Edit > Labels > Add Label at Selection, or use shortcut Ctrl + B
5. Type the name of the song into the label
6. Repeatedly click the Zoom Out button until you can see the start of the third song
7. Continue in this manner adding a label to mark the start of each song
Label at the start of the second song in the audio track
You can save time by using Analyze > Label Sounds... to automatically label the regions to be
exported for the songs. This method thus lets you exclude some or all of the areas between
songs.
This tool depends on correctly detecting the "silences" between tracks and this depends on
setting their parameters appropriately for your track.
If you did the original recording properly and avoided clipping, the recording is probably not at the maximum
possible volume. In order for the LP or CD to be burned at maximum volume and thus match other LPs or
CDs in your collection we need to fix this.
The default choice in this dialog is to amplify to a maximum of -1.0 dB. The maximum setting is 0 dB, but the
default setting of -1.0 dB provides a little headroom as some players can have playback problems with audio
at 0 dB.
Some consumer-level turntables, tape decks and/or amplifiers may well record stereo channels with a
stronger signal in one channel than the other, which you will probably want to correct. In that case, check the
box that says Normalize stereo channels independently.
One problem when copying records is that a loud click in one channel can cause Normalize to create an
unwanted change in the stereo balance. In that case you should consider removing the click before the
Normalize step, using Click Removal.
The final step involves creating multiple audio files from the Audacity project.
Include audio before first label should be unchecked, as there is no audio before the first
label
5. Under Name Files:
Using Label/Track Name should be checked.
9. Metadata Editor will appear for the next and the subsequent songs; as before, enter any additional
information and click "OK" for each window. When you click "OK" on the window for the last song, all the
files will export.
Backup
Backup your exported WAV or MP3 files - you do not want to lose all that valuable work and have to do it all
over again. Computer hard drives can fail, destroying all data.
Ideally use a dedicated drive (1+ TB external magnetic drives are convenient and economical), or upload to
an online (cloud) storage service to store the WAVs or MP3s. Better still is to make two copies on different
external devices and even better is to hold an online backup as well as the local copies.
You may want to create a taxonomic file structure - for example each album can be stored in its own folder
(named for the album) within a folder named for the artist (or, perhaps, composer for classical music) to make
searching and retrieval easier.
Manage Macros
Manage Macros allows you to edit, remove or rename existing Macros or add a new Macro. It also allows
you to apply Macros to you project or a set of files.
Any built-in, LADSPA, LV2, Nyquist, VST or Audio Unit (Mac) effect shown in the Effect Menu can be added
to a Macro. You can also add plug-ins in any format that are shown in the Generate or Analyze Menus
(including Vamp analysis effects), the built-in Find Clipping analyzer and a number of export commands.
Macros may be applied to either the entirety of the current project or to a selection of files using the Tools >
Macros... command.
It is possible to use Noise Reduction in Macros but see Noise Reduction Tips for how the Noise Profile is
captured.
The full list of all Macro commands, with descriptions, is available at Scripting Reference.
Accessing Macros
Select Macro
Select Macro contains a list of already defined Macros. You can define the name of a new Macro and select
which Macro is active.
The left hand box in the dialog (labeled Select Macro) contains a list of already defined Macros. Until you
add a new Macro, it only has built-in MP3 Conversion and Fade Ends Macros.
Use left-click (or use the Up or Down keyboard arrows) to select the Macro you want to work on
Edit Steps lists the sequence of commands in order of first to last (End) for the Macro selected in the Select
Macro box to left.
The Macro can include a number of common Audacity functions and effects to be executed in any order
you specify.
To create an audio file as part of the Macro process you must include an "Export" command (such as
Export as WAV).
The Export command will use the settings you used the last time you used the same command from
the File > Export > Export... menu command, or default settings if you have never used that
command from the menu.
In many cases the parameters for each command in the Macro can be specified within the Manage
Macros dialog.
You can:
Command
Move Down: Move the currently selected command down in the list
Save: This button is only active when you have made edits to a Macro. It enables you to save those
changes.
You can also edit an existing command by double-clicking it, or using the Up or Down keyboard
arrow to select it and then pressing Space. The parameter settings dialog for that command will
be displayed.
A few commands are intentionally omitted from the Macro Manager (such as Close:) because they are
unsuitable for use in Macros.
To insert a new command in a Macro, left-click or use the Up or Down keyboard arrow to select an existing
command and then press Insert. The new command will be placed above this selected command.
The Select Command dialog appears, listing all the available commands. Double-click a command
from the list to insert it in the "Command" box, as shown in the image below after inserting "Normalize".
Alternatively, use the Up or Down keyboard arrow to select the command, then press Space.
Use the Select Command dialog to choose a command to be inserted into the macro
The full list of all commands, with descriptions, is available at Scripting Reference.
Some scriptable commands are particularly useful for Macros. See these pages for details:
Extra Menu: Scriptables I - most commonly useful scriptables.
Extra Menu: Scriptables II - less commonly useful scriptables, but also including Select and Set
Track, which combine functionality of several scriptables.
If the command has editable parameters, the Edit Parameters button will be active. Clicking this button
will bring up the dialog box for the effect where you can set the parameters as if you were applying the
standalone effect.
If you have previously created user presets for an effect you can use the Use Preset to select one for use
with that effect in the Macro.
Choose OK in the effect dialog to accept the parameters you entered, or Cancel to revert to the default
parameters.
Choose OK in the Select Command dialog to add the command to the Macro.
It is strongly recommended that you set parameters for the commands that you use in a Macro.
Otherwise Audacity will use the last-used parameter setting(s) when you ran the effect(s)
manually.
Also note carefully that settings used in Macros will not affect or change the last-used parameter settings for
any effect when next run manually.
The tick boxes on the left determines whether a feature should be used. When not selected, that feature
does nothing.
The second tick box determines whether the feature is set to "on" or "off".
This shows:
Commands that call Effects, Generators, Analyzers or Tools, use the same familiar graphical interface (GUI)
as appears when they are used from the normal top level menus.
Many of the other commands provide a simple GUI comprised of checkboxes and text entry boxes. Typical
examples can be seen in the Scriptables I and Scriptables II menus.
Macros will work on pre-existing selections you make in your project prior to running the Macro. But the
selection can be over-ridden by your Macro itself as there are Macro commands available to effect
selections in the audio.
If you want to select all tracks, maintaining your current time selection, use "Select: First=0
Last=100". It will not waste time twiddling its thumbs on the tracks that are not there.
When applying a Macro to files there is no pre-existing selection so you will need to create a selection in the
Macro if your Macro requires audio to be selected to act on (and most Macros do).
There are four basic export commands available: Export as WAV, Export as MP3, Export as FLAC
and Export as Ogg.
See Macros Palette for details of naming and location of exported files.
Parameters for export formats cannot be set in Manage Macros. To configure export parameters
for the Macro, click File > Export > Export Audio... to access the Export Audio Dialog, click
Options, set the parameters, press OK then Cancel the export. An audio track must be on screen
in order to open the Export Audio Dialog.
There is also a special Export command Export2 which enables you to export to a specific target file and
format. When using Export2 you have to give the full file name (including path and filename extension).
Note carefully that the filename is not dynamically changeable when running the Macro, once set in the
Export2 parameters, so you may wish to create several Macros the Export2 each targeting different file
locations, names and filetype.
Example:
The quote marks around the file pathing are supplied by Audacity once the Export2 command has been
edited in setting up or editing the Macro
When entering the pathing data in the edit parameters dialog for the command you do not put the quote
marks for example: C:\Users\<username>\Desktop\my file.flac
Deprecated Export commands
The following two commands are now deprecated and may well be removed in future versions of Audacity.
They were part of "CleanSpeech" (which has long been removed from Audacity).
The Export as MP3 56k before and Export as MP3 56k after commands can be used respectively to
export "before" and "after" MP3 files at 56 kbps bit rate at any point in the Macro processing. This allows
you to compare the result of one or more effects, or provide files for different purposes with and without a
particular effect.
The name of the MP3 exported by the "Export as MP3 56k before" command is prefixed by
"MasterBefore_" followed by the date and time. The name of the MP3 exported by the "Export as
MP3 56k after" command is prefixed by "MasterAfter_" followed by the date and time.
Comments in Macros
Comments be added to Macros to enable you to document what is happening in the Macro.
Add a comment to your macro using the Comment command and edit its parameters to type the text of your
comment.
The buttons
Use the Shrink button to show a reduced Macros Palette dialog with a simple list of the existing Macros,
enabling you to apply the Macros but not edit them.
This smaller version is useful for presets. It stays open after applying a macro, so it is a palette of custom
functions, and you can pick another and apply that.
Using the Expand button on this reduced dialog will return you to the full Manage Macros dialog.
Apply Macro to
Apply Macro to enables you to make a Macro operate on either your current open Project or a set of
selected external Files.
See Macros Palette for details of how these two buttons operate.
If there any unsaved changes you will be asked if you want to save them or not.
Macros Examples
This error may sometimes occur for one or more commands in a Macro when updating from a previous
Audacity version. The error may also occur if users sharing Macro have different Audacity versions or
different versions of the plug-ins used in the Macro. The error will occur if:
any command in the Macro uses a different text format than that recognized by the version of Audacity in
use
any plug-ins listed in the Macro are missing, in an incorrect location or are incompatible with the version
of Audacity in use.
To resolve these errors, ensure you have compatible versions of all required plug-ins and that the plug-ins
are installed correctly. If necessary, use the Manage Macros dialog to delete the command that fails then
insert a replacement command for the same effect from the Select Command dialog.
Macros Palette
You can apply any of the existing macros using the Macros Palette. To open it you can either:
Once invoked, the Macros Palette window will remain on-screen, actively available, at all times
unless and until you dismiss it or close Audacity.
Select Macro
In the "Macro" list, left-click on a Macro (or use Up or Down keyboard arrow) to select the Macro you want
to apply.
Apply Macro to
Project
Use the Project button to apply the selected Macro to the current project.
The typical purpose of this option is effect automation - apply a sequence of effects to the project, using
effect parameters and an order of applying the effects that you have found to work well for the type of audio
you are processing. This saves time and provides consistency in your workflow.
The effects in the Macro are applied to the selected region of waveform in the selected audio tracks. Usually
the selected Macro would not include an export command so as to use the greater flexibility of the Export
Audio Dialog.
If an export command is included in the Macro, the entire project audio is exported irrespective of track or
region selection. Therefore if the project contains multiple audio tracks, they will be mixed together, unless
any of the tracks are muted on the Track Control Panel.
If the project has been Saved, then the exported files will be saved in a folder named macro-output.
The macro-output folder will be in the location specified in Directories Preferences.
If the audio in the project came from an imported file as its initial step (that is, it is a named project), the
macro-output folder will also be in the location specified in Directories Preferences.
If the project has not been saved and is un-named, the normal Export Audio dialog will appear enabling
you to choose the name and location of the exported file.
Macros will work on pre-existing selections you make in your project prior to running the Macro.
But the selection can be over-ridden by your Macro itself as there are macro commands available
to effect selections in the audio. In particular All(Select All) will select the entire project and
Select which is parameterizable (see the provided Fade Ends Macro for an example where the
first and last one seconds of the audio are selected for the fades).
Files...
The typical purpose of this option is batch processing - apply the Macro to multiple audio files so as to
apply one or more effects to them, and/or convert them to another file format. You can convert from any file
format supported by Audacity to WAV, MP3, OGG or FLAC.
Use the Files... button to apply the selected Macro to selected external audio files that are in a single
directory.
If you already have audio in the current project window, you must save and close that project using File >
Close before applying a Macro to files.
You cannot apply a Macro to multiple Audacity AUP3 project files, instead you need to use
Python scripting.
The selected Macro must include an Export step, otherwise the processed audio will not be
retained.
You cannot process multi-channel audio files (for example, 5.1 surround sound files) using Macros, even if
Import / Export Preferences has been set to "Use custom mix". Any multi-channel files you import will be
mixed down on export.
A standard File Open dialog box will appear. Choose a directory then you can select one or any number
of supported audio files in that directory, including older AUP project files (but not AUP3 project files).
You cannot select files outside that directory, and files in folders inside that directory will not be
processed.
It is convenient therefore to first put all the audio files you want to process into one folder before
applying the Macro.
After selecting the audio files you want to process, choose Open.
Each file will be imported into Audacity and processed, exported to the format you chose in the Macro,
then the processed audio will be removed so as to clear the temporary disk space that had been used.
The exported files will be saved in a folder named "macro-output" in the folder specified in the Macro
output field in Directories Preferences. The original files are not altered.
If you leave the entry for Macro output blank in Directories Preferences then Audacity will default to
creating a folder called "macro-output" in:
Windows: C:\Users\<your username>\Documents\Audacity
When a Macro is applied to files, the only option is to import and process the entire file. Thus the
entire file will be exported unless an action or effect in the Macro (such as Cut or Truncate
Silence) removes some audio.
If modifying the audio before exporting, the Select Time function may be useful to select audio
to remove or modify.
Some optional Nyquist plug-ins have parameters to trim or extend audio by a specific length
and Nyquist can do calculations too, so it may be helpful to use Nyquist plug-ins from within a
macro.
The buttons
Expand
Use the Expand to return to the full-size, full-function Manage Macros dialog.
The apply Macro buttons are also available on the Manage Macros dialog - so all Macro operations can be
made from that full dialog.
Otherwise the dialog will remain open on the screen, but allowing you to perform other Audacity functions.
Macros Examples
This page provides some examples of how the Macros feature in Audacity can be used.
Example 1: Loud MP3
A batch processing Macro to compress and normalize WAV files then convert them to MP3:
1. Insert Compressor to reduce the dynamic range of each WAV, also normalizing them to maximum
amplitude of 0 dB
Alternatively you can choose Tools > Apply Macro..., select the Loud MP3 Macro then click
Apply Macro to: Files... where you can select the files on which to run the Macro
Example 2: NR&EQ
An effects automation Macro for the current project that applies noise reduction and equalization:
4. Insert another Normalize at different settings (without offset removal, setting a final amplitude of -1 dB)
5. Click OK to close the Manage Macros window
Macro example: Noise Reduction and Equalization
When later needed in your workflow, choose Tools > Apply Macro..., select the NR&EQ Macro then click
Apply Macro to: Project to apply the Macro to the selected track(s) in the current project window.
If a Noise Profile exists, that Noise Profile will be used. It is often best to capture a suitable
Noise Profile before running a Macro.
Useful Commands
The Select command with 'Relative To=Selection' can be used to extend and contract a selection.
Command: "SelTrackStartToEnd"
Description: This command (from Select > Region > Track Start to End) Selects all audio in all selected
tracks.
Extra Macros
Spectral Magickes Wacky-Macro
This Macro takes a single mono track, and converts it to a stereo track, with one channel a spectrogram and
the other a wave.
It is one example of how to creatively abuse the Macro system, since audacity is not set up to handle mixed
views on wave tracks.
Note the use of a TrackCount of 0.5 to select just one of two channels in a stereo track.
SelectAll:
Duplicate:
Select:"Mode=Set"
SetTrack:Pan="-1"
Select:"Mode=Set" Track="1"
SetTrack:Pan="1"
Select:Mode="Set" TrackCount="2"
MixAndRender:
Select:Mode="Set" TrackCount="0.5"
SetTrack:Display="Spectrogram"
Select:"Mode=Set" TrackCount="0"
With normal project rate of 44100Hz, this selects about 126 samples centered on the cursor, and applies the
'Repair' effect to it. 'Repair' can only handle up to 128 samples.
Note: There is no reliable way of separating vocals. The methods described in the article depend
on the position of the vocal track in the stereo field.
1. Select Split Stereo to Mono from the stereo audio track dropdown menu
2. After splitting the stereo track you will end up with 2 mono tracks similar to this:
3. Invert one of the mono tracks by selecting it and then choosing Effect -> Invert
4. Play back the result.
This will remove everything panned in the center, not just vocals and returns a dual mono result
(both channels have the same audio). In some music this could mean removing instrumental parts.
Removal of the vocals can often be incomplete leaving artifacts behind; this is especially true
where there are backing vocals or where reverb (echo) has been applied as this spreads sound
sources and makes them very hard to extract from each other.
If the vocals are panned in the center of a stereo track this method can sometimes be effective by removing
what is common to both tracks (that is, the vocals), leaving behind what is different (that is, the
instrumentals).
Audacity includes the Vocal Reduction and Isolation effect which provides the Remove Vocals option that
you can use to try to remove vocals from a stereo track.
Remove Vocals option parameters
Vocal Reduction and Isolation also lets you specify the audio frequency range for vocals (by default 120 to
9000 Hz). This can help cure the common problem where center-panned bass or Hi-hat is also removed
when removing vocals.
Isolating Vocals
You can also use the Vocal Reduction and Isolation effect to attempt to isolate the vocals by choosing one of
the Isolate Vocals options from the Action dropdown menu in the dialog.
Note that the end result may not be total vocal isolation or even satisfactory isolation of the vocals; it all
depends on how the original recording was engineered.
Note: This is an experimental feature not yet part of the normal Audacity installation.
To use AI models in Audacity, you first need to download the current alpha with this feature from
https://interactiveaudiolab.github.io/project/audacity
Once you have installed this version, you can download and apply AI models via Effects → Deep Learning
Effects.
Deep Learning Effects are computationally very intensive. Depending on the model used and
your computer, it can take several minutes to hours to apply the effect to a single song. It is highly
recommended to test out whether the model is satisfactory on a short section (less than 10
seconds) before applying it to an entire track.
Audio Analysis
Spectral analysis
Audacity has several powerful spectral analysis tools: Spectrogram View per track, Plot Spectrum, as well
as support for Plugins.
Spectrogram View
Each track in Audacity can be viewed in a Spectrogram view:
To access it, click on the track menu dropdown and select Spectrogram.
The track menu also features Spectrogram settings, where you can tweak the scale, the colors, the used
algorithms and the window size.
The Track Menu dropdown
Tip: To view the waveform and the spectrogram at the same time, choose Multi-view instead.
You may notice that the spectrogram is somewhat blurry usually, where even if you have a precise
frequency, the spectrogram makes it look like a whole range of frequencies is being played. This is an
inherent mathematical tradeoff related to the window size:
Depending on what you're after, you can change the window size to fit your analysis: Smaller window sizes
benefit time resolution, larger window sizes benefit frequency resolution.
Tip: If you change the algorithm from Frequencies to Reassignment, Audacity will attempt to
sharpen both time and frequency resolution using the method of reassignment. This works best
for signals that are separable in time and frequency with respect to the analysis window.
You can change both the window size and the algorithm in the spectrogram settings found in the Track
Menu dropdown.
You can zoom vertically in Spectrogram View by right-clicking the frequency scale.
Additionally, while hovering over the frequency scale, you can
Plot Spectrum
To use Plot Spectrum,
Options
Algorithm
Spectrum (default)
Plots the fast Fourier Transform (FFT) of the data, with the FFT window size being determined by the
Size dropdown. The amplitudes are normalized such that a 0 dB sine (pure tone) will be (approximately)
0 dB on the graph.
Autocorrelation
These options measure to what extent the sound repeats itself.
This is done by taking two copies of the audio, and moving one forward by one sample. The two copies
are then multiplied together, and all the values added up. This is repeated for two samples difference
and so on, up to the number of samples in the size option. This gives a small result if the waveform is
random (for example, noise) and a large result if it is repetitive (like a musical note). By looking at the
peaks in the plot, the key frequencies present can be determined even if there is a lot of noise.
Cepstrum
The cepstrum of an audio signal is related to the spectrum, but presents the rate of change in the
different spectrum bands. It's particularly useful for properties of vocal tracks and is used, for example, in
software to identify speakers by their voice characteristics.
Function
Function offers choices like Rectangular, Hann, Hamming and others. We suggest you use the default Hann
for most situations.
Details
The fundamental principle at work here is that the way we observe our data changes what we see.
The "true spectrum" of your project would be computed over the entire project and would provide
very detailed frequency resolution but essentially no time resolution at all. In other words, this "true
spectrum" would offer an average frequency distribution over the entire project. If we select a short
interval of audio, the short-time spectrum has frequency resolution limited by the observation
window time AND the result is affected by the spectrum of the window itself. For general audio
analysis, the Rectangular window is least desirable, and the other options offer slightly different
effects
Click the Export... button to export the current view as a tab-separated value text file.
Analyzer Plugins
Audacity supports the Vamp plugin format among others. Many of them can be found in the Vamp Plugin
Pack.
Audacity Plugins
Troubleshooting
Error codes
This page lists Audacity error codes and provides some troubleshooting steps on how to fix them.
If your issue isn't listed here, or the troubleshooting steps aren't working for you, feel free to ask in
our communities:
Forum
Discord
Error code 11, error code 13, error code 101 and "Audacity failed
to read a file in C:"
These errors can occur when attempting to load a damaged .aup3 project file. Damaged project files can be
recovered as described in the following article.
This error can also occur when you are trying to record a number of channels that is not supported in the
current configuration
You can attempt to fix this issue with the following methods:
Use a different USB port and USB cable. This will resolve the issue if the fault was in the cable.
Use a different audio host. Sometimes WASAPI works when MME doesn't, sometimes it's the other
way round.
Use a different number of channels. For example, some Realtek only work when recording in Mono,
while some others only work in Stereo when recording a (loopback) stream.
This error can also occur when you are trying to record a number of channels that is not supported in the
current configuration To fix this, you can do the following:
Use a different audio host. Sometimes WASAPI works when MME doesn't, sometimes it's the other
way round.
Use a different number of channels. For example, some Realtek only work when recording in Mono,
while some others only work in Stereo when recording a (loopback) stream.
Your device is unable to playback other tracks while recording. Turning off Overdub via Transport ->
Transport Options may fix this.
You can try the Common troubleshooting steps , or attempt any of the other workarounds of this page.
Install FFMPEG. FFMPEG allows you to open most kinds of media files. Read more:
Installing FFMPEG
Check if the file you're trying to open actually is what it says on the tin. For example, some lower-
quality programs name any audio file *.mp3 , regardless of whether it actually is an MP3 file. Read
more: Can't open an MP3 file
Check if your file is an actual audio file. Some files which are used to output audio in certain programs
don't actually contain sound themselves, but are instructions for for the program to make some sounds.
Try to see if the program used to create the file has an export button. If not, you can also try recording
desktop audio while playing back the file in another program. Read more:
Recording desktop audio
Check if you have accidentally created custom import rules. In Edit -> Preferences -> Extended
Import (on macOS: Audacity -> Preferences -> Extended Import), make sure that you have not created
any custom rules. If there are any rules, you can safely delete the rules.
Import the audio as RAW. This only works on uncompressed audio. You can do so via File -> Import -
> Import raw data...
The setup program may return one of the following exit codes:
The user clicked Cancel in the wizard before the actual installation started, or chose
2
“No” on the opening “This will install…” message box.
A fatal error occurred while preparing to move to the next installation phase (for
example, from displaying the pre-installation wizard pages to the actual installation
3
process). This should never happen except under the most unusual of circumstances,
such as running out of memory or Windows resources.
The user clicked Cancel during the actual installation process, or chose Abort at an
5
Abort-Retry-Ignore box.
The Setup process was forcefully terminated by the debugger (Run | Terminate was
6
used in the Compiler IDE).
Before returning an exit code of 1, 3 or 4 an error message explaining the problem will normally be
displayed.
Future versions may return additional exit codes, so applications checking the exit code should be
programmed to handle unexpected exit codes gracefully. Any non-zero exit code indicates that Setup was
not run to completion.
Error code 11
Error code 13
Error code 101
"Audacity failed to read a file in C:" (or D:, E:, ...)
Make sure you use the latest version of Audacity. See Downloading & installing Audacity for more
information.
Sometimes, just opening the file in the latest version automatically recovers the project. If not, proceed with
the following steps:
After downloading, follow the instructions relevant to your system. Note: macOS is not supported yet.
Caution: Make sure you have plenty of space left on your computer. You will need roughly 4
times the size of your .aup3 for a successful recovery. If you have a 10GB file, you should have at
least 40GB available.
Windows
3. Move the two .exe files from the unzipped folder into AudRepair.
4. Copy your defective .aup3 project file into the AudRepair folder.
5. Rename the file to broken.aup3 .
6. Press Windows-key + R , and type cmd . A (black) cmd screen will appear.
8. Type dir and press Enter . The following three files should be listed: audacity-
project-tools.exe , broken.aup3 , and sqlite3.exe
If that file works as expected, go to File -> Save As... and save it to your usual location. The
recovery process is now over, you can continue working as normal.
If that file does not appear, or is still broken, continue with the following steps:
14. The messages " Project requires Audacity 3.0.0 ", and " Using
'sqlite3.exe' for recovery " will appear. Later the message " Executing
query #xxxx.... " will appear as the rescued file is being recreated.
Note: This process can take quite a while depending on your specific machine. There is no
status (or % completion) indicator, so you just have to be patient.
You should plan 15-30 minutes per GB, though it may be faster if you have a fast PC.
Keep an eye on available disk space.
Due to a glitch, sometimes a single character can appear when the program is done, eg
" z ". If this happens, simply press Backspace.
15. When the process completes, your should be able to open the "broken.recovered.aup3" in
Audacity.
The message "File not saved properly" will appear the first time you open the recovered
project. This is normal and you can ignore this message.
If the messages " Invalid block xxxx: Block not found ", check to see if some
audio was silenced - typically near your most recent edits. Usually these messages are
spurious.
Linux
8. Type ls and press Enter . **** The following three files should be listed: audacity-
project-tools , broken.aup3 and sqlite3
9. Make the audacity project tools and sqlite3 executable by typing chmod +x audacity-
project-tools sqlite3 and pressing Enter .
10. Type ./audacity-project-tools -drop_autosave broken.aup3 and press
Enter .
If that file works as expected, go to File -> Save As... and save it to your usual location. The
recovery process is now over, you can continue working as normal.
If that file does not appear, or is still broken, continue with the following steps:
14. Type ./audacity-project-tools -recover_db -recover_project
broken.aup3 and press Enter .
15. The messages " Project requires Audacity 3.0.0 ", and " Using 'sqlite3'
for recovery " will appear. Later the message " Executing query #xxxx.... "
will appear as the rescued file is being recreated.
Note: This process can take quite a while depending on your specific machine. There is no
status (or % completion) indicator, so you just have to be patient.
You should plan 15-30 minutes per GB, though it may be faster if you have a fast PC.
Keep an eye on available disk space.
Due to a glitch, sometimes a single character can appear when the program is done, eg
" z ". If this happens, simply press Backspace.
16. When the process completes, your should be able to open the "broken.recovered.aup3" in
Audacity.
The message "File not saved properly" will appear the first time you open the recovered
project. This is normal and you can ignore this message.
If the messages " Invalid block xxxx: Block not found ", check to see if some
audio was silenced - typically near your most recent edits. Usually these messages are
spurious.
Note:
There is no guarantee that all content will be able to be restored, or any at all.
Some additional commands for the Audacity Project Tools can be found on Github.
If a section of audio is missing, you may need to manually re-record it. See
Re-recording a section for more information.
Privacy permissions
Some operating systems may block access to the microphone for untrusted apps. You need to allow
microphone access for Audacity in order to record.
Windows
1. Open Settings
MacOS
1. On your Mac, choose Apple menu > System Preferences then click Security & Privacy in
the left-hand menu and the click the Privacy tab.
2. Click Microphone in the left-hand menu.
3. Select the checkbox next to an application (Audacity) to allow it to access the microphone.
Linux
If you have installed Audacity as a Snap or Flatpak, you may need to go to the System settings >
Application settings
Windows
1. Open the Sound control panel and select the Recording tab
After enabling your microphone use the Audacity Transport - Rescan Audio Devices option to
update the list of available devices.
MacOS
Linux
Some audio devices install a complementary application that provides options to check for firmware and
driver updates.
Windows users can try to manually update drivers using Device Manager, before looking for drivers on the
Internet. This is easiest, but may not necessarily find the latest or most appropriate drivers.
Windows 10 / Windows 11: Right click the Start button and select Device Manager
Windows 8 / Windows 7 / Windows Vista: Click Start > Control Panel then using the "Category" view,
click "Hardware and Sound", find "Devices and Printers" near the top of the screen then click on "Device
Manager" (the last item in the list underneath). "Icons" views have a direct link to Device Manager, as
does "Classic View" on Windows Vista only.
Then expand Sound, video and game controllers by clicking on the + sign, right-click over the sound
device and click Update driver.
Using Device Manager to manually update drivers for an audio device
After the update (even if more recent drivers were not found), you should right-click over the device again,
click Properties and then on the Driver tab to check the "Driver Provider". You don't want drivers from
Microsoft - in most cases these are only generic drivers, not specifically matched to your hardware. This
often leads to problems such as not being able to select the correct input, or recordings not being made
correctly. These must be replaced with drivers made by the manufacturer of your hardware, so they are
correctly matched to that hardware.
If you have now got updated non-Microsoft drivers, try them and see if your recording problem is solved.
If the controls on your device are properly set you should check the connections between the computer and
the recording device.
To solve this, make sure the device is detected by the operating system, then select Transport > Rescan
Audio Devices from the Audacity Menu Bar. The new device should appear as an option on the Recording
or Playback device selection dropdown in the Device toolbar.
You can turn Software Playthrough on and off in the Transport > Transport Options menu.
Note: you will hear what you are recording a noticeable time afterwards. This delay is called
latency. You can somewhat reduce this latency as described in Latency Compensation but it
cannot be fully removed if you're using Software Playthrough - you will need an audio interface
with realtime monitoring capabilities to completely remove latency when monitoring a recording.
If you want to listen to the input when not recording it first enable Software Playthrough and then click in
the Recording Meter Toolbar to turn on monitoring.
Software Playthrough can also be enabled In the Recording section of the Preferences window.
Check the Software playthrough of input box and click OK.
To listen to the live recording input without playthrough latency requires hardware monitoring - that is; the
input signal must be routed directly through the audio device from the input to the output rather than being
passed through software from input to output.
Enabling hardware monitoring is not possible with all audio devices. In particular it can only be achieved
when the same device is used for input and output. For example, monitoring a USB microphone through
headphones that are plugged into a different audio device will always have latency. If hardware playthrough
is not available with your hardware it may be necessary to listen to the audio source directly (acoustically)
rather than through the computer.
For some typical examples of how to set up equipment to record without playthrough latency, see this
Tutorial about Recording overdubs.
Try lowering the recording level using the Audacity Mixer Toolbar or the slider in the operating system. You
can also check to see if you can lower the volume on the input source itself (such as the tape deck, record
player or microphone). Many sound cards and USB turntables or USB tape decks have an independent
volume control for the playback signal level See Recording with USB turntables or USB cassette decks for
When recording, try to aim for a maximum peak of around –6 dB in the Recording Meter so as to prevent the
meter's red clipping warning coming on. If the meters are set to linear, the equivalent level to aim for is 0.5.
Clicking and dragging on the meter's right edge lets you expand the meter to gauge levels more easily. After
recording, you can boost the level safely using the Amplify or Normalize effects.
Help with repairing clipped recordings: If there is only a small amount of clipping (just the tops
of a few isolated peaks), Effect > Clip Fix can be applied to just the clipped sections. This will
attempt to reconstruct the missing peaks by interpolating the lost signal. In other cases where
there is mild distortion throughout a recording, using Effect > Filter Curve EQ or Effect > Graphic
EQ to reduce the higher frequencies can help to mitigate the damage. Sometimes a bass cut will
help also by making the result sound less "muddy".
The vertical red lines show where the clipping has occurred; these clipping indicators can be turned on and
off (Audacity default setting is "off") by selecting View > Show Clipping (on/off).
If the slider is disabled, check first in Device Toolbar that you are selecting the correct device. Audacity
should be able to control the recording level of most built-in sound devices subject to the device having
appropriate Sound Device Drivers.
If necessary look in the operating system mixer or in the audio interface's control panel for an input slider.
For Windows see Windows: accessing the Windows Sound controls. To locate the system mixer for Mac
and Linux see the help on our Wiki for Mac or Linux.
External recording devices such as USB turntables or tapedecks or interfaces may not have an operating
system slider, especially on Mac. For all cases where there is no system slider, try to adjust the playback
level on the recording device itself.
Latency Compensation
By default Audacity will compensate the latency present in your system by 130 milliseconds. Using this
procedure you can estimate and set the proper value for your system.
Note: Latency Compensation is only important for the following recording scenarios:
Overdubbing: recording a new audio track while listening to previously-recorded track(s).
You want what you play to be synchronized with the tracks you are listening to.
Punch and roll recording
On Windows open the Edit menu and select Preferences... or press Ctrl + P in your keyboard. On
macOS open the Audacity menu and select Preferences... or press Cmd + P
Select the preferred Interface Host: MME or Windows WASAPI should work
Select Edit > Preferences... or press Ctrl + P to open Audacity Preferences and click on Devices
At the bottom of the Audacity window you will find the Selection toolbar
Hardware Setup
To measure the latency you will need to record the audio from your playback device using your microphone.
To do this place your microphone next to your speakers/headphones
Place your microphone next to your speakers or headphones
Open the Generate menu and select the Rhythm Track... option. Set Number of Measures (bars) to 2
and set the Beat Sound to Ping (short). Click OK to generate the track.
Press Shift + R to record a new track. The rhythm track will be played back and recorded on a new
track.
Recording a new track while playing the previously generated track (Overdub)
Zoom in so you can see the clicks on the top track and its delayed version on the bottom track
Create a selection that goes from the start of one click to the next
You should see something like this:
You can read the latency directly from the second panel of numbers. In this case it is 0.184 seconds or 184
milliseconds.
Click on Edit > Preferences, click on Devices tab and enter the negative of this number in the Latency
compensation box. In this case it would be -184. Press OK to save your preferences.
Delete the second track by clicking the close box in its Track Control Panel
After the recording is finished Audacity will apply the Latency compensation by pushing the newly-recorded
track back by the Latency compensation value.
Note: If you change any of your recording or playback devices (for example, if you change from
using the line input port on your computer to using a USB audio interface) or if you use the same
device but change the Audio Host in Device Toolbar, then you will need to do this test again. The
test you just did only applies for the specific inputs and outputs and host used during the test.
Your file isn't using the MP3 codec, but instead is using a codec associated with another file
extension (for example, the Advanced Audio Codec (aac) usually is found in .m4a files, and PCM Wave
is usually found in .wav files). A true MP3 file will show MPEG Audio, Version 1, Layer 3 .
To solve this error, you can use MediaInfo to find out what the actual codec used in the file, and change
the file extension accordingly (for example rename the audio.mp3 file to audio.m4a ).
Your file is partially broken (Huffman Data Overrun). This is a bug with Audacity versions 3.1.3 and
earlier, and you can fix it by installing the latest version of Audacity.
Your file is fully broken. If it can't be opened in Audacity, or anywhere else, your file might just be
broken. This itself may have several reasons:
If you just recently downloaded it from the internet, you may want to try downloading it again - in
case there was a transmission error.
If you just created it yourself, it might be that there was a write error. If possible try saving the file
again, re-installing the app that was used to create it, or using a different app to create it.
If you had the file on your computer for a long time and it worked in the past, it might be that your
hard drive is starting to fail.
If using a wired headphone, make sure that the wire is plugged in and that the plug is clean.
Make sure that the headphones are selected in the Audio Settings output.
Note: On some devices, the internal card - usually called something among the lines of "HD Audio" are
handling both internal speakers and headphones, depending on which is plugged in. You may need to
select this option anyway even if it says "Speaker" instead of "Headphones"
If you connected the headphones after starting Audacity, you may need to go to Transport -> Rescan
Audio Devices to make them show up in the Audio Setup list.
Missing features
This page lists features which got removed from Audacity, as well as their replacements.
The Device toolbar has been replaced by the Audio Setup button in version 3.2.0. However, you can re-
enable it via View -> Toolbars -> Device Toolbar.
Zoom Tool
The Zoom Tool has been removed in version 3.2.0. All of it's functionality can be accessed via the Zoom
buttons, or via Ctrl+Scroll ( Cmd+Scroll )
Community
Contributing to Audacity
There are several ways to contribute to Audacity. All of them tremendously help out other Audacity users.
Contribute to audacity/audacity-support
GitHub
Gitbook works a bit like a wiki in that you can edit all pages freely, but unlike a wiki, it uses git's "everyone
has their own branch" principle. That is to say that the changes you make are independent of everyone
else's changes, and won't show up on the main (live) website until the branches are merged.
To some degree, this means that you can do whatever you want in your branch. That said, there's some
things which make things easier for everyone involved:
Best practice
1. Do one task per branch. Want to make a new guide on a new feature? Make a new branch.
Want to remove all instances of the oxford comma? Make another branch. You can click the
Doing so makes it easier to understand what your changes are exactly, and should one of
your changes be rejected, most of your other work won't get blocked by it.
2. Only submit complete pages. Your progress is saved automatically, so if you want to call it
for the day, simply close the page and continue the next day. If you accidentally hit "submit",
simply start editing again to convert your branch to a draft branch again.
3. Be aware of the others, to avoid duplicate work. You may connect with other editors in our
discord servers.
4. Follow the Style Guide , to give this entire site a somewhat uniform style.
When editing on Gitbook, you can edit existing pages, but you cannot create new ones. If you'd like to make
a page about a new topic, write to LWinterberg in the discord server. You also can hand in Markdown files or
Word documents to him directly to add. This restriction does not apply when Editing through GitHub ,
however, there are other technical oddities when editing through GitHub.
Trailer
(example video)
We have some requirements for which video tutorials are accepted into Audacity Support pages (see the
Style Guide Video Tutorials for more info)
Style Guide
These are the rules designed to give the entire user guide a somewhat unified style. You may apply them
with some freedom.
General
The goal of the user guide is to provide explanations on how to perform various tasks in Audacity.
Features vs tasks
Documenting features seems like the obvious thing to do: Audacity has various menus, so better have a list
of what every option in that menu does. However, this leads to the situation where some pages are
completely unfindable as a reader already needs to know where certain options are in the menu in order to
find out what the page would be called. For example, the feature containing the slider for the recording and
playback volumes is called Mixer Toolbar. But nobody except the people most intimately familiar with
Audacity know it's called that!
To combat this, try to write your guides as a way towards a goal, or a task. The above example, instead of
naming the page after the feature, name it after the task it does, so:
Setting recording levels and playback levels
Tasks aren't necessarily tied to individual features. For example, Noise reduction & removal can talk
about several tools as once as they all are means towards a common goal.
If a feature has many different modes or options that are unrelated to the task you're describing, avoid
making long lists of what all the feature can do. Focus on the task-related ones instead.
If a feature has several ways to access it, use the most accessible option. For example, for an "how to play
audio" article, simply mention the big green play button and the shortcut Space . Don't also mention
Transport > Playing > Play/Stop.
There are some exceptions to this, especially when documenting more "advanced" features like Macros
which need extensive guiding about how to operate it. Instead of a linear "go here, then here and there, and
then you're done", split them up into sub-tasks (for macros: creating macros, editing macros, etc.) and keep
these unrelated tasks on one page. Avoid breaking it down to the point where you are explaining individual
buttons (don't say "the cancel button cancels the effect without applying it")
Rule of thumb: If a feature is easy to use, but hard to find, document it like a task, ie answering
the question "how do I do x". If a feature is hard to use, document how to use the feature as a
series of sub-tasks if possible.
Target audience
Audacity's user base consists largely of casual users. As such, you can't expect the readers of your guide
to understand even fairly common audio terms (for example: compressor or loudness vs volume), unless it's
directly connected to the topic you're writing about.
For example, if you write a guide about compressing and expanding audio, you don't need to hold yourself
up on explaining what a compressor is, since the only people who'll ever end up reading that guide are
people who already know about that. However, if you were to mention a compressor on a page about
general audio editing, you would need to explain what a compressor is good for.
That said: If it's possible to describe a feature without needing to resort to lingo, use it even if it's slightly less
accurate. For example, "punch-in repair" would be the accurate term for Re-recording a section , but
also is way harder to understand and thus to find.
Scope
While there's a lot of things you can write about in relation to Audacity, keep in mind that this site is focused
on user guides (or how-to guides, or tutorials - they all have the same idea). We want to minimize work on
contributors while maximizing impact, so guides should be kept as general as possible. Only use qualifiers
such as "for podcasters" or "for musicians" if their use case shares almost no resemblance to what everyone
else would be doing anyway.
Audio-related content beyond Audacity, like: "how to build a quiet recording booth"
Reviews and recommendations of software/plugins/...
Technical documentation about the internals of Audacity.
Writing style
You can address the reader directly ("you"). You should remain impartial in the process though, so no "I" or
"my".
The overall tone should be friendly but not patronizing, and the language should have a healthy
middleground between casual and technical.
Page titles
Titles should reflect the task you're trying to teach. For example, if you're teaching how to add reverb, the title
should be "Adding reverb"
Page titles should be written in sentence case. So generally, the first is capitalized while everything else is
not, except proper nouns and acronyms ("Audacity", "FFMPEG").
Note: When the title explicitly refers to an option within Audacity itself, use the spelling found
inside Audacity. So for example, "Using the Noise Reduction effect" would have "noise
reduction" capitalized, but "Reducing noise in Audacity" would not.
Introductions
Underneath the title is a field for page descriptions. These descriptions are the first thing users see of the
article when looking at Google, or seeing an embed to it somewhere.
As such, they should give a good summary of what the page is going to be: In a few words, how will a goal
be achieved? What features will be used?
Instructions
1. Do This
2. then that
3. then a third thing
If you need to interrupt the steps for explanations, you can either do
1. Do this
2. then that (shift+enter)
Note: This is an explanation on a new line
3. then a third thing
If instructions are different depending on the operating system or other factors, you can use tabs, like this:
Windows
Windows Instructions
macOS
MacOS instructions
Linux
Linux instructions
Tabs aren't part of standard Markdown, so they probably won't show up properly if you're using github or a
local editor. They'll show up just fine on Gitbook though.
Note: Tabs are quite big blocks, visually speaking. When using them, make sure that what you're
showcasing is worth this space. For example, if you're just saying that undo is Ctrl+z on Windows
and Linux, you can just put brackets behind it for the mac instructions - "press Ctrl+z (Cmd+z)"
If a task has a main way of working, but may benefit from additional context, you can use the Expandable
block:
Further information
Note that you cannot embed other blocks inside Expandables. You are limited to Paragraphs,
Headings (h1, h2, h3), lists (bullet points, numbers, checkboxes) and code blocks. Images are
possible, but only as inline (ie inside a paragraph).
Images
You can take screenshots using the clipping tool or tools like ShareX. ShareX has the advantage that it has
built-in tools like arrows, step-by-step bubbles and labels which can help you visualize several steps at
once.
With images, there always is a tradeoff between easy maintainability, clarity and context. So crop them as
much as possible without losing important context, and use them in a way that makes updating them as
painless as possible.
Info boxes
Info: Use these for information which is useful to know, but not necessary to fulfill the task. These
boxes should be started with
Warning: Use these for information where things might go wrong and the user might get
undesired results. These boxes should be started with
Caution: or Warning: depending on which feels more appropriate in terms of urgency
Danger: Use these for super important information only, where ignoring the danger box would
lead the user to irreparable damages (lost data, broken audio, ...). These boxes should be started
with
Danger: for super important info
NEVER or DON'T if you need to go straight into the warning, where "danger" would look silly.
Success: Use these for things the reader should do. These should be started with
Best practice: or Do: for best practices
Checklist: if you want to provide a checklist
These info boxes aren't part of standard markdown, so if you're not using gitbook itself, but edit through
Github or a local editor, they will look a bit silly in your preview (but show up correctly here).
Video Tutorials
If an image is worth a thousand words, a video tutorial can be worth a million: At it's best, it can tell the entire
story the written guide would make in a way that always has all necessary context and requires no lengthy
description of where to find things.
However, video tutorials can go out-of-date incredibly quickly and then cause a lot of confusion among
viewers.
Because of this, a video tutorial must follow these rules to be added to an Audacity Support page:
The video must clearly state what version of Audacity it's referring to in the beginning.
The video must be in the language of the Audacity Support page it's meant to be embedded in. Right
now, that's English only.
The video must not contain a sponsorship read, and it is preferred to have the video completely ad-free.
The video should be licensed Creative Commons-Attribution (see YouTube help). This way, if your
video goes out of date, other people can update only the part of your video that goes out of date.
The video and the Audacity Support page it's supposed to be embedded in should match the steps they
take. If the video tutorials goes on a tangent unrelated to the initial task, the written guide may omit the
tangent and instead place the contents of the tangent in a "See also" section.
The following points are considered best practice for video tutorials:
Start with the purpose and version number and then go straight into the content: "To do XYZ in Audacity
4.2.0, first go to..."
Use a script which you follow when making your video. This will automatically eliminate the following
two points, and also get you a long way towards making subtitles.
Avoid going off-topic, eg "hey guys, and welcome back to another video! my sister's aunt's nephew
requested I make a tutorial so he can cook his eggs using Audacity to which I said..."
Go through your tutorial linearly step-by-step, and avoid jumping back to earlier sections much later in
the video. For example, if you are in Step 9 already, jumping back with a "oh yeah, I forgot to add that in
Step 3, you need to also do..." is majorly confusing.
Add subtitles to your videos. Not only do they make your tutorial more accessible to deaf people, they
also are useful to people who have trouble understanding your dialect or accent, or who want to auto-
translate the subtitles into their own language.
Use chapters on YouTube to mark major steps in your video. They work by putting the following in your
video description:
0:00 Intro
0:30
0:45 Step
Step 1.
2. Clicking here
Sliding there
1:00 Step 3. Cha-cha-cha
Any page of both support.audacityteam.org and plugins.audacityteam.org can be edited either on Gitbook
(see Writing Tutorials and User Guides for instructions) or using Markdown syntax on GitHub.
Note: Various formatting options available in Gitbook cannot be previewed on GitHub and most
local Markdown editors. Be aware of the differences between
Gitbook-hosted pages (plugins/support.audacityteam.org)
Raw Markdown.
The reverse isn't true however: All Github-flavored markdown is supported in Gitbook.
On a technical level, this will create a "fork" of the page, found on your Github
profile, with a new branch called "patch-#" in which you are editing. As long as you
are within this branch, you can do whatever you want with out stepping on anyone's
toes.
Best Practice: Frequently switch between the Code and Preview tabs in GitHub to get a general
sense of what your edit will look like.
Also, if you haven't already, now is a great time to familiarize yourself with the Style Guide .
On a technical level, this creates a commit in your "patch-#" branch. A branch can
hold as many commits as you like, so if you want to do multiple changes, you can
exit the flow after clicking "propose changes" and edit another file instead.
This brings you to a page where you can review your changes. If you are satisfied, click Create Pull
Request.
Clicking this button creates a form...
... in which you can give an overview of your changes to the team.
After you click "create pull request", it will show up on https://github.com/audacity/audacity-support/pulls and
await review by an Audacity team member.
Caution: Avoid using office suites like Microsoft Word, LibreOffice or Google Docs to edit
Markdown. They tend to use very different formatting options, which don't transfer to plain text. As
a rule of thumb, if it doesn't save in .txt or .md, it's not the right app to use as a Markdown editor.
To get started, first clone the repository, either using git clone
https://github.com/audacity/audacity-support.git by clicking the code button on
https://github.com/audacity/audacity-support and opening it in GitHub Desktop
Note: You will need to use some form of Git to make a pull request, so just downloading the ZIP
will not work.
Once it's cloned, you'll find the files of support.audacityteam.org in the main branch, and the files of
plugins.audacityteam.org in the plugins branch. Any additional branches have been split off from the
main branch to preserve documentation for previous versions of Audacity.
Further information on using git with VScode can be found in the VSCode docs.
Technical notes
Outside from the syntax requirements, there are some more technical things you need to be aware of:
The sidebar menu is handled through SUMMARY.md, not the file structure itself. If you want the page
you created to show up in the sidebar, you will need to update this file accordingly. That said: Try to
match the structure of SUMMARY.md with the folder structure.
While you technically can work directly in your fork's main/plugins branch, it is highly recommended to
make a new branch based on upstream/main or upstream/plugins instead for your changes.
This way, you can always fast-forward merge the latest changes into your fork.
When updating your fork's side-branches to the latest state of main, rebase it if possible.
Heading 1
(shows up in the outline)
Heading 2
Heading 3
Lists
Unordered
List
1. Ordered
2. List
Task
List
List with
1. sub-items
2. can have
changing list styles
...
Lists can be used anywhere, including inside other blocks. They can only include inline content and other
(nested) lists.
Hint
Caution
Danger
Success
A quote block
// a code block
code blocks <b style="some_css: 23px;" class="and other things"> also supports syntax highligh
These blocks can be used inside of Tabs. The code block can also be used in Expandables, but cannot
have other blocks inside it. The quote block and infobox can have headings, inline content and lists inside it.
supports captions
Attached file:
supports captions
Embeds
YouTube embed
Home
Audacity ®
example.md
hosted with ❤ by GitHub view raw
gist embed
Rick Astley
soundcloud embed
Embeds cannot be used inside of other blocks except the Tabs block, nor can other blocks be placed inside
them.
Tables
text 123
text 456
text 789
select-option column files column Ratings column
option a ZoomIn.png
ZoomIn.png
option c option b option a transport toolbar.png
Trim.png
Select-option and files columns appear empty in Markdown. Avoid using them.
Tables cannot be used inside other blocks except the Tabs block, nor can other blocks be placed inside
them. Inline content works inside of text columns only.
Tabs
First Tab
Second Tab
Third tab
Tabs cannot be used inside other blocks. Tabs can have most other blocks inside them, except of other tabs,
expandables, and API blocks.
Expandable content
Expandables cannot be inside other blocks. Expandables can have headings, lists, code blocks, and inline
content inside them.
Drawings
also supports captions
A Gitbook-specific drawing thing, generating SVGs. Likely useless when using Markdown.
LaTeX
f(x) = x ∗ e2piiξx
Cannot be placed inside of other blocks except the Tabs block. That said, an inline variant is available
which can go pretty much anywhere.
GET https://example.com
/example
API title
Parameters
Path
id String
Description
Query
id* String
Description
Header
id String
Description
Cookie
id String
Description
Body
id String
Description
Responses
200: OK
Description
Cannot be used inside other blocks. Can only contain plain text. Unfortunately very tailored towards web
APIs only.
TODO
Pages under this section are just stubs. Feel free to work on them. Check out the Style Guide and
Making Tutorials and User Guides for more info
ASIO in Audacity
Due to licensing restrictions Audacity cannot be distributed with built-in support for ASIO. However You can
build Audacity for your personal use and include ASIO support.
Audacity can record and playback audio on your Windows PC using one of the following three alternative
interfaces:
MME
Windows DirectSound
Windows WASAPI
ASIO (Audio Stream Input / Output) is an additional proprietary interface to record and playback audio in
Microsoft Windows. ASIO bypasses the Windows audio mixing components to provide lower latency direct
communication between computer audio software and hardware. Most audio recording interfaces
manufacturers provide a driver to support ASIO.
ASIO supports 24-bit sampling which is only otherwise available using Windows WASAPI or WDM-KS
(Windows Driver Model Kernel Streaming). 24-bit sampling allows greater dynamic range, lower
theoretical noise floor and greater resolution at lower audible volumes.
Windows DirectSound interface protocol support multi-channel recording on some sound devices, but not
the very low latencies that are possible on ASIO.
https://manual.audacityteam.org/man/asio_audio_interface.html
https://gist.github.com/SteveALee/da24c2be633340b8791066dd98eb5d0b
Synchronizing Tracks
https://alphamanual.audacityteam.org/man/Rhythm_Track
https://alphamanual.audacityteam.org/man/Sync-Locked_Track_Groups
Batch processing: Apply one or more effects to multiple audio files and export the processed audio into
a new file.
To use this select the Apply Macro to: Files... button in the Macros Palette or the Manage Macros
dialog.
For more detail on batch processing please see this page.
Effects automation: where the selected audio in the track or tracks in the current project is subjected to
the same prescribed sequence of effects, and optionally, a file exported from the entire audio.
Macros can contain Select commands to make their own selections as the Macro runs
Effect presets: where selected, commonly used, effects are stored with your preferred settings for quick
re-use.
You can manage and apply Macros using the Tools Menu:
Tools > Macros... to manage Macros: to create, edit and test them
Tools > Apply Macro > Palette... for a toolbox of Macros
Tools > Apply Macro > named Macro to apply one named Macro
Manage Macros
Use Tools > Macros... if you need to create a new Macro or to edit an existing Macro.
The left side pane displays existing macros and the right pane list the steps for the selected macro
Use the Shrink button to show a reduced Macros Palette dialog which lists the existing Macros.
This dialog is also available directly via Tools > Apply Macro > Palette...
Click Expand on the Macros Palette to return to the full Manage Macros dialog.
Apply Macro to
Both the Manage Macros dialog and the Macro Palette dialog have Apply Macro to buttons:
Commands that call Effects, Generators, Analyzers or Tools, use the same familiar graphical interface (GUI)
as appears when they are used from the normal top level menus.
Many of the other commands provide a simple GUI comprised of checkboxes and text entry boxes. Typical
examples can be seen in the Scriptables I and Scriptables II menus.
It is strongly recommended that you set parameters for the commands that you use in a Macro.
Otherwise Audacity will use the last-used parameter setting(s) when you ran the effect(s)
manually.
Also note carefully that settings used in Macros will not affect or change the last-used parameter
settings for any effect when next run manually.
Basically to paraphrase: "What happens in Macros stays in Macros".
Sharing a Macro
You can export a Macro as a TXT file using the Export button in Manage Macros and send it to another user,
or copy it to another computer for use there
You can import another user's Macro, or a copied macro of your own, into your Macros folder by using the
Import button in Manage Macros.
You can also edit Exported Macros with a text editor and Import them back in if required.
Each Macro is automatically saved as a separate text file with TXT extension in the Macros folder in
Audacity's folder for application data:
Windows: Users\<username>\AppData\Roaming\audacity\Macros
In order to see the Macros folder on Windows, macOS or GNU/Linux, you must show hidden files
and folders or type the folder location into your file manager's address bar.
Windows: In the tree on the left of Explorer, double-click "Users" then double-click your
username, then on the right, double-click the AppData or Application Data folder and
navigate through that. If necessary, show hidden files and folders on Windows or type
%appdata%\audacity\Macros or shell:appdata\audacity\Macros into the Explorer address
bar then press Enter on your keyboard.
macOS: Open Finder, use the Go menu, choose Go to Folder and type
~/Library/Application Support/audacity/Macros, or set Finder to show your User Library
folder.
Macros Examples
From https://wiki.audacityteam.org/wiki/Audiobook_Mastering
TODO
Working with Tracks
(this probably is a category on its own, but let's write it on this page for now)
If you know Audacity well, but don't want to write tutorials, you can try helping users out directly. The most
active community in this regard probably is the Audacity Forum, but you'll also find users in our Discord
community and on the audacity subreddit.
Tools
There is a tool available to recover broken projects:
GitHub - audacity/audacity-project-tools
GitHub
Translating Audacity
Translating Audacity is the best way to get involved right in Audacity's UI without having to code.
Audacity is translated into multiple languages by volunteers across the world. If you want to contribute to
translation please join the audacity-translation mailing list and read the instructions below.
Before joining the Audacity project in Transifex please subscribe to the audacity-translation
mailing list and check the status of the translation you would like to contribute to with others
members of the list.
You can find and join the Audacity project at https://explore.transifex.com/klyok/audacity/
Select the language you would like to contribute to from the dropdown.
Click Join Project (if the language is Available to join) or Request Language if the language you want
to contribute to is not available yet.
Select the language you want to translate Audacity to and click Join Project or Request Language
Once you have been approved as a translator you will receive a notification by email. After that you will see
the project in your Dashboard and you can start to contribute.
Audacity Project Dashboard in Transifex
Each language translation is stored in a PO file. For example it.po is the Italian translation and ko.po is the
Korean translation.
To download a PO file from GitHub click on the link for the .po file for your language. On the page
you come to, right-click the Raw button and then select then Save target or Save link as. Select
the location to place the PO file.
Use the wxWidgets languageinfo.cpp file as a reference to the list of translated languages.
GNU gettext
The following instructions use poEdit 3.1.1 to illustrate the process of translation
If there is no translation PO file for your language create a new one using the following steps:
Select Translation > Properties... and verify that the Character option is set to UTF-8 otherwise poEdit
will not save any translations with non-English characters.
The following instructions use poEdit 3.1.1 to illustrate the process of translation
Download the PO file for your language, for example it.po or open a previously translated PO file from
your computer.
Select File > Save to save as a PO file. Select a destination folder and type a name for the file. Click on
Save. poEdit will save a .po file plus a .mo file for use in Audacity.
Submitting a translation
To submit a translation, please send the completed .po file to the audacity-translation mailing list. A
member of Audacity Team will commit the file and send a message to the list confirming this.
1. You can get an up-to-date alpha version of Audacity, NOT suitable for production use, but good for
checking translations on, in the nightly version: https://audacityteam.org/nightly. From there, you’ll find
there are choices of builds for different platforms. Download the right one for your platform.
2. On Windows, open the “Languages” directory inside the unzipped Audacity folder, then open the
directory with the same name as your .po file.
On Mac OS X, right-click or control-click over Audacity.app > Show Package Contents then open the
relevant LPROJ directory inside the “Resources” directory.
On GNU/Linux, open the relevant “locale” directory in usr/share/ or usr/local/share.
3. If creating a new translation, create a new directory for your language using the correct language code
from the wxWidgets languageinfo.cpp file. For example, the code for Punjabi is “pa”, so on Windows,
create “Audacity\Languages\pa”.
4. Rename the saved .mo file to “Audacity.mo”, and paste it into the directory you opened or created.
5. Open Audacity and in Preferences > Interface, choose your language and click OK. You should now
see your translations.
Further information
Please read Translating Audacity for more tips on translating the Audacity source code, and to learn
how the Audacity software is translated.
wxWidgets i18n
Developing Audacity
Audacity is being developed on Github. All information necessary to contributing code can be found there,
such as building instructions or bugs to fix.
Testing the latest features
When you do find something that breaks, make sure to file a bug!
Tools
Macros
Journaling
Journaling is a feature that records all your actions and lets you replay them.
1. start Audacity in journaling mode, <<TODO: HOW??>> do a certain task, and then close Audacity again.
This will generate a journal file, which you can find in <<WHERE>>.
2. Copy the journal file to a new folder (eg: QA-tests) and name it so that you can easily find it again.
Windows
audacity.exe -j QA-tests\yourtest.txt
macOS
audacity -j QA-tests/yourtest.txt
Linux
audacity -j QA-tests/yourtest.txt
Plugins
Audacity Plugins
Alternatively, you can also make a pull request to the plugins branch on audacity support on Github.
###################################################
Name of Plugin
A short description of what the plugin is good for.
Example Domain
Download page
Details
Additional info, such as developer name, license and copyright info, a short "how to use" section
or link to the documentation page, or a screenshot of the plugin - preferably of it working withing
Audacity.
#####################################################
Note: When editing through pull requests on Github, note that Gitbook uses additional formatting
tags than available in standard-markdown, so your preview might not match what'll be shown to
users eventually.
Leo Wattenberg
(add your name here if you're editing some pages!)
License
Contents on this page are licensed under the Creative Commons - Attribution license. This does not
necessarily apply to embedded videos.
Contributors of the old Manual
manual.audacityteam.org has been made possible by a tremendous amount of effort from the following
people:
Gale Andrews
Richard Ash
David Bailes
Christian Brochec
Matt Brubeck
John Colket
James Crook
Steve Daulton
Scott Granneman
Greg Kozikowski
Leland Lucius
Dominic Mazzoni
Edgar Musgrove
Tony Oetzmann
Alexandre Prokoudine
Peter Sampson
Martyn Shaw
Vidyashankar Vella
Bill Wharrie
Leo Wattenberg
Translators: