From Audacity Development Manual
Jump to: navigation, search

The scripting module is an experimental GUI plug-in that allows Audacity to be driven from an external Perl or Python script. Commands are sent to Audacity over a named pipe. Any scripting language that supports named pipes can be used. External scripting is one of several ways to extend the functionality of Audacity.
Warning icon Scripting support is currently considered experimental and is mainly intended for use by developers for the time being.
  • Feel free to try it out, but don't be too surprised if there are problems, or if the details of commands change between versions of Audacity.
  • Currently Windows or Linux are recommended. Mac requires more work to get anything useful at all.

There is a fuller list of limitations at the foot of this page.

How to get started with scripting

Audacity can currently only be used with scripting if you compile a separate plug-in module from our Git sources called "mod-script-pipe", as well as compile Audacity itself. These need to be compiled on the same day, which helps ensure the versions match. See the Wiki Developer Guide for help. You'll also need the scripting language Python (version 3.6 or later recommended) to try out the examples. For actually writing scripts, any language that can write to and read from a named pipe should be able to use the interface. We for example have an earlier script in Perl available.

We may provide a ready-compiled mod-script-pipe at some future time. If you just want to use scripting but don't want to do the developer steps then you will need to wait for that to be released. Feel free to let us know if you would like ready-to-go scripting in Audacity, and what you would use it for.


Ensure you have the latest Git version of Audacity built, installed and working. The scripting module, "mod-script-pipe" is in Git (under lib-src), but is not built automatically.

In MSVC, open "mod-script-pipe.vcproj" and build. If all goes to plan, the DLL will be placed in the "modules" directory.

Under GCC, move into the lib-src/mod-script-pipe directory and type "make". This will build the module then copy "" to the "modules" directory in the source code tree. To have Audacity see, copy it to /usr/local/share/audacity/modules or ~/.audacity-files/modules/.

While mod-script-pipe allows a script to communicate with Audacity, it is not concerned with the actual interpretation and processing of received commands. That is done by Audacity itself, so for full scripting capabilities it is important to have a recent build of the main program as well as the scripting module.

Getting Started

  • Run Audacity
  • Go into edit->preferences->modules
    • Choose mod-script-pipe (which should show 'New') and change that to 'Enabled'.
  • Restart Audacity
  • Check that it now does show 'Enabled'.

This establishes that Audacity is finding mod-script pipe, and that the version is compatible (compiled on the same day).

This python script is then the best way of checking that the pipe is working:

After running it, you can use do("") at the python command line to try out commands. Each command name ends with a colon, and may be followed by parameters. For example:



Some documentation for the parts of Audacity that can currently be controlled via script command follows. Be aware that this is likely to change significantly until scripting has matured. Note also that commands and parameters are case-sensitive.

The command invocations should take the following form:

Command: Param1=Value1 Param2=Value2

This is followed by a line break. Then the command is executed, and any responses are written on the return pipe, on separate lines. The end of the responses is signalled by an empty line. Further commands should not be sent until all responses have been read.

Bulb icon A couple of commands are often used in testing, just to establish that something in scripting is working:
  • Help command gives help on individual commands.
  • Message command echos a message back to your script.


Returns information about the parameters accepted by a given command.


CommandName: The command on which to get help


Send Receive
Help: CommandName=Select Select
EndTime: a floating-point number (default: 0)
FirstTrack: an integer (default: 0)
LastTrack: an integer (default: 0)
Mode: one of: None, All, Range, Name (default: All)
StartTime: a floating-point number (default: 0)
TrackName: any value (default: 0)
Help finished: OK


Sends a message to the command's status target. Since command status messages are currently sent to the script (if the command was triggered by a script), this means the message is sent back to the script.


MessageString: The message to send


Send Receive
Message: MessageString=hello hello
Message finished: OK


Provides some control over the project selection. Tracks between FirstTrack and LastTrack inclusive are selected, and the time interval selected is from StartTime to EndTime. Alternatively, if TrackName is specified, then the track with that name is selected.


FirstTrack: An integer (default: 0)
LastTrack: An integer (default: 0)
TrackName: Name of a track (not required if using FirstTrack and LastTrack)
StartTime: A floating-point number (default: 0)
EndTime: A floating-point number (default: 0)
Mode: One of: None, All, Range, Name (default: All)


Send Receive
Select: Mode=Range FirstTrack=0 LastTrack=1 StartTime=3.2 EndTime=8.4 Selected track 'Audio Track 1'
Selected track 'Audio Track 2'
Select finished: OK
Select: Mode=Range FirstTrack=0 LastTrack=0 StartTime=0.1 EndTime=9.9 Selected track 'Audio Track 1'
Select finished: OK

Bulb icon A couple of the commands open the way to a lot more commands that are not listed here. You can use the select command to select audio, and then use:
  • MenuCommand - allows any single menu command to be actioned by the external script. You'll want to use the ones which don't bring up dialogs.
  • BatchCommand - allows any command used in Chains to also be used in scripting. So for example any effect can be used. Although effects create dialogs, used from batch they don't, as you can pass in the parameters you want.


This can be invoked differently from the other commands because, at the moment, all unrecognized commands are treated as batch commands. To see what these commands do and how they should be formed, please examine the Edit Chains dialog. As an example, the batch system can be used to apply an effect to some selected audio, selected by the select command.

It is also possible to explicitly call a batch command. This is illustrated with the Noise command in the examples, where in the second version it is explicitly called with 'BatchCommand:'. If BatchCommand: and a ChainName is provided, the command applies the saved batch chain of that name rather than a single command.


ChainName: If provided, applies the batch chain of that name
CommandName: Name of the batch command to execute
ParamString: Parameters for the batch command


Send Receive
ChangeTempo: Percentage=10.0 BatchCommand finished: OK
Noise Noise finished: OK
BatchCommand: CommandName=Noise BatchCommand finished: OK


Executes a 'menu command', using the system that controls the Audacity menus. This is simple but powerful, and many of the tasks that can be performed by clicking menu items or pressing shortcuts can also be triggered by a script using this command.

Bulb icon The names of commands accessed via MenuCommand are coded names that differ slightly from the text actually in the menus. For example:
  • RemoveTracks rather than 'Remove Tracks'
  • Record1stChoice rather than 'Record'.

Use the GetMenus: command to see a full list of available commands.


CommandName: Name of the menu command to execute


Send Receive
MenuCommand: CommandName=SplitDelete MenuCommand finished: OK
MenuCommand: CommandName=Play MenuCommand finished: OK
MenuCommand: CommandName=TrackMute MenuCommand finished: OK
MenuCommand: CommandName=RemoveTracks MenuCommand finished: OK
MenuCommand: CommandName=Record1stChoice MenuCommand finished: OK


With two tracks selected, running this command compares the tracks sample by sample, and counts the number of samples whose absolute difference exceeds the given threshold. The total count is returned, as well as the number of seconds of audio that these samples represent.


Threshold: Floating point number 0.0 to 1.0


Send Receive
CompareAudio: Threshold=0.1 Comparing tracks 'Audio Track 1' and 'Audio Track 2'.
Finished comparison: 764480 samples (17.335 seconds) exceeded the error threshold of 0.200000.
CompareAudio finished: OK


The screenshot command is modelled closely on the Screenshot Tools dialog and takes three parameters.


FilePath: A string representing the directory path in which the captured images should be saved.
CaptureMode: A string specifying which area of the screen should be captured.

Possible values: window, fullwindow, windowplus, fullscreen, toolbars, selectionbar, tools, control, mixer, meter, edit, device, transcription, trackpanel, ruler, tracks, firsttrack, secondtrack.

Background: Type of background to use in the shots where one is possible.

Possible values: White, Blue, None.


Send Receive
Screenshot: FilePath=/home/dan/Temp CaptureMode=fullwindow Background=None Saved /home/dan/Temp/fullwindow001.png
Screenshot finished: OK


Returns a list of all available menu commands. These are the commands that can be sent using MenuCommand.




Send Receive
GetMenus New

GetMenus finished: OK

There are also two related commands:


Prints the value of the requested preference as a response.


PrefName: String containing the name of the preference (as in audacity.cfg)


Send Receive
GetPreference: PrefName=/CsPresets/NoiseGen_Duration 30
GetPreference finished: OK


Sets the preference with the given name to the given value.

Warning icon The preference is changed in the audacity.cfg file. You may need to use the ReloadPreferences command (which does not exist yet) to see the effect.


PrefName: String containing the name of the preference (as in audacity.cfg)
PrefValue: Value of the preference


Send Receive
SetPreference: PrefName=/CsPresets/NoiseGen_Duration PrefValue=12.0 SetPreference finished: OK


Allows information about a project's tracks to be returned to the script.


TrackIndex: An integer (default: 0) identifying the track
Type: Info to get. One of:
  • Name
  • StartTime
  • EndTime
  • Pan
  • Gain
  • Mute
  • Solo
  • Selected
  • Focused
  • Linked

(default: Name)


Send Receive
GetTrackInfo: Type=Name TrackIndex=0 Audio Track
GetTrackInfo finished: OK
GetTrackInfo: Type=EndTime TrackIndex=0 24.000000
GetTrackInfo finished: OK


For setting track information - currently track name only. (Note mute/solo can be set with menu commands)

  • If you want to set a name with spaces in it, put the name in single quotes.


TrackIndex: Specifies which track to modify
Name: String to which the track name is to be set
Mute: True or False
Solo: True or False
Pan: -1.0 is left 1.0 is right
Gain: 0 to 100.0 on a log scale.
Selected: True or False
Focused: True or False


Send Receive
SetTrackInfo: TrackIndex=0 Name=Eric Mute=True SetTrackInfo finished: OK
SetTrackInfo: TrackIndex=0 Name='Baron Munchausen' Mute=True SetTrackInfo finished: OK


Returns the chosen information about the tracks in the current project.


SelectedTracks: An integer (default: 0) identifying the track
Type: Info to get. One of:
  • Name
  • NumberOfTracks
  • SelectedTracks
  • SoloTracks
  • MuteTracks
  • FocusedTrackID

(default: Name)

Name is the filename.


Send Receive
GetProjectInfo: Type=SoloTracks 001010000
GetProjectInfo: Type=FocusedTrackID 5
GetProjectInfo: Type=NumberOfTracks 9
GetProjectInfo: Type=MuteTracks 00010

The SelectedTrack, MuteTracks and SoloTracks types all return a series of 0's and 1's indicating which tracks have that property.


Allows state of one parameter type on all of a project's tracks to be set.

The TrackSet parameter represents the setting for tracks numbering left to right, starting with track 1, as in 12345...

The characters in the string represent enabling (1) disabling (0), or leaving alone (x) the parameter indicated by Type=ParamTracks for each channel.

  • '1' means that parameter is asserted in that track, for example, for MuteTracks, a 1 will mute that track.
  • '0' de-asserts it, for example for MuteTracks a 0 unmutes that track.
  • 'x' will leave the indicated track in its current state.

The string length is not required to match the number of channels in a project. If the string of 1s and 0s is shorter than the number of channels, then channels beyond the “reach” of the TrackSet string are untouched.

If the TrackSet string is longer than the number of channels in the project, then those characters in the string beyond the last track in the project are ignored.


Type: Info to set. One of:
  • SelectedTracks
  • SoloTracks
  • MuteTracks
SelectedTracks: A string of characters: {1,0,x} indicating Assert, Deassert or leave alone, respectively


Send Receive
SetProjectInfo: Type=SoloTracks TrackSet=10010xxx1 SetProjectInfo finished: OK
SetProjectInfo: Type=MuteTracks TrackSet=101000xxx SetProjectInfo finished: OK


Load audio data from a file into a track. The file type is detected from the extension, and any format understood by Audacity can be used.

  • If the filename has spaces in it, put the name inside single quotes.


Filename: Name of the file to import


Send Receive
Import: Filename=/home/dan/ArtTatum-Indiana.flac Import finished: OK


Save audio from the project into a file. The file type to export to is detected from the extension, and any format understood by Audacity can be used.


Mode: Either 'All' or 'Selection' - sets which audio is to be exported
Filename: File to export to
Channels: Number of channels to export


Send Receive
Export: Mode=All Filename=/home/dan/ArtTatum-Indiana.mp3 Channels=2 Exported to MP3 format: /home/dan/ArtTatum-Indiana.mp3
Export finished: OK


Opens an audacity project file, optionally from a supplied file name. If the Filename parameter is omitted or empty the user is prompted to choose a project to open. Note that if the current project is not empty and unsaved, a new project window is opened, which may break your script.


Filename: File name of the project to open. Default is to prompt the user to choose a file. Must include .aup file extension.
default=ask user
AddToHistory: Include opened file in File -> Recent Files? Has no effect on User prompted files; they always appear in Recent Files.


Send Receive
OpenProject: Filename=myproject.aup OpenProject finished: OK


Saves an Audacity project file, optionally to a supplied file name. If the Filename parameter is omitted or empty the user is prompted to choose a saved file. Note: trying to overwrite another existing project will result in an error message to the user.


Filename: File name of the project to save to. Default is to prompt the User to choose a file. Must include .aup file extension.
default=ask user
Compress: Save audio in compressed (OGG) format?
AddToHistory: Include opened file in File -> Recent Files? Has no effect on User prompted files; they always appear in Recent Files.


Send Receive
SaveProject: Filename=myproject.aup SaveProject finished: OK

Adding Commands to Audacity (for developers)

For a command to be callable from a script, a CommandType object for it must be added to the CommandDirectory, which is a singleton class. A CommandType has the job of creating specific Command objects, which actually do the work.

To implement a new command called Foo, it is simplest to create new classes FooCommandType and FooCommand which derive from CommandType and CommandImplementation respectively, and then override the virtual methods as appropriate. Then add an instance of FooCommandType to the CommandDirectory.

In the future, the repetitive nature of some of this code may be reduced, for example by using macros (as in wxwidgets). For more information on the workings of the command system, see the source code - in particular the files in the src/commands directory.

Known Issues & Missing Features

Warning icon Some current issues:
  • Scripting only works with one project at a time.
  • For some menu commands, the project window must have focus for the command to succeed.
  • Scripts have no control over the type and verbosity of responses they receive. (Related: it's not straightforward to get 'output' responses from commands like GetTrackInfo.)
  • Current commands could have stricter parameter validation.
  • There's no consistent way to abort or interrupt commands.
  • There are still many parts of Audacity that cannot currently be controlled from a script because commands for them have not yet been created.
  • Due to a slight problem with module management, the scripting module is not unloaded when Audacity quits. This means the script pipes are not properly deleted.
  • There may or may not be security problems relating to the use of pipes. You're advised not to use mod-script-pipe on a system with multiple simultaneous users.
  • The interface on the script side of the pipe is still quite low-level. It may be possible to generate libraries for specific scripting languages from the internal descriptions of the commands.