Modules Preferences

From Audacity Development Manual
Revision as of 10:27, 29 January 2015 by PeterSampson (talk | contribs) (P1 downgraded to P2 Placeholder - Modules turned off for 2.1.0)
Jump to: navigation, search

Gale 03Oct13: P1 Update this page.

  • Peter 13Jan15: It's looking like, if I read Vaughan's RM email comments correctly that Modules will not be in 2.1.0.
  • Peter 29Jan15: ToDo-2 Placeholder - Modules turned off for 2.1.0

Preferencias de módulo

Devices PreferencesPlayback PreferencesRecording PreferencesQuality PreferencesInterface PreferencesTracks PreferencesImport/Export PreferencesExtended Import PreferencesProjects PreferencesLibraries PreferencesSpectrograms PreferencesDirectories PreferencesWarnings PreferencesEffects PreferencesKeyboard PreferencesMouse PreferencesModules Preferences dialog
Click on any of the other Preferences sections in the above image to go directly to that Preferences page.

Enable these Modules (if present), next time Audacity is started

Advice All the following modules are considered experimental.
  • None of these modules are shipped with Audacity releases. To use them you must compile the module and compile Audacity on the same day.
  • Expect to find some issues if you do use any modules.
  • If depending on these experimental modules, consider both stability and potential security risks.
  • mod-script-pipe: This is a GUI plugin 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.

Audacity and command-line window running a script


  • mod-nyq-bench: Nyquist Workbench is a graphical editor for writing Nyquist plugins and scripts. Plugins can be run directly from the editor. Nyquist Workbench is highly recommended (though not essential) for anyone interested in writing Nyquist plugins for Audacity.
Nyquist Workbench with notch.ny plugin loaded in Script window.
    Current features include:
    • Full support for Generate, Process and Analyze effects
    • Auto load last file
    • Built-in output/debug screen
    • Parentheses matching.
    Nyquist Workbench must be compiled from the latest Audacity SVN Development Code. Compiling instructions for the Workbench are here. Alternatively, Nyquist code snippets can be tested at Effect > Nyquist Prompt....


  • mod-track-panel: This is the start of an experiment that will ultimately provide a more flexible panel for the audio, label, MIDI and note tracks. It allows us to safely experiment with new additions to these core features and is currently only of value to developers. To use mod-track-panel, you must compile it from the latest Audacity SVN Development Code.