Modules Preferences
![]() |
Audacity does not currently ship any pre-built modules, though some experimental modules are available in the source code. |
- Accessed by: (on a Mac )
- Modules Preferences.
Optional Modules
![]() |
The following module is considered experimental.
|
mod-script-pipe
This is a GUI plug-in that allows Audacity to be driven from an external Perl script, or using any scripting language that supports named pipes. To use mod-script-pipe, you must compile it from the latest SVN Development Code.Commands are sent to Audacity over a named pipe. A sample Perl script is included in the latest Audacity development code.
Any program that can open a pipe to that module could control Audacity. This has potentially serious security implications. For example another program could control Audacity, and potentially could exploit some other bug in Audacity or in mod-script-pipe to crash it. Hackers working out how to control a machine remotely often start by working out how to crash it remotely and work up from there. For security reasons it would be totally inappropriate to use scripting with audacity on a webserver to provide audio processing.
For more details on how to use scripting, see Scripting.
![]() |
Information about other experimental modules may be found on the Modules page. |
Loading modules into Audacity
To use an experimental module such as Nyquist Workbench:
- Add a "modules" folder to the Audacity installation folder
- Add the file such as mod-nyq-bench.dll (Windows) or mod-nyq-bench.so (Mac) to the Modules folder, restart Audacity and open Modules Preferences
- You should see that file is marked as "New":
- Click the dropdown menu for the item, change it to "Enabled", press then restart Audacity.
When you restart Audacity, you should now see an additional "Nyquist Workbench" entry in the Tools Menu (or whatever feature the module enables).