Macros

From Audacity Development Manual
Revision as of 15:37, 6 February 2013 by PeterSampson (talk | contribs) (added temporary H2 to simplify editing)
Jump to: navigation, search
Peter 23Jan13 Nomenclature: I created this page with the title "Chains - for batch processing" - in an email Gale suggested ths similar "Chains (for batch processing). My original choice was the simpler "Chains" - Gale commented that "Chains of effects are advanced terminology ... this I think is the very reason the page was called Batch Processing in the first place" and "Is it not also true that many of the Forum questions about our Chains feature are expressed using "batch" terminology?"
  • Peter 6Feb13 Possible page titles (note this page is designed to repace the current Batch Processing page):
    1. Chains with a tagline on the front page link: "for batch processing")
    2. Chains with a tagline on the front page link: "for batch processing and macros")
    3. Chains of effects with a tagline on the front page link: "for batch processing")
    4. Chains of effects with a tagline on the front page link: "for batch processing and macros")
    5. Chains - for batch processing
    6. Chains - for batch processing and macros
    7. Chains (for batch processing)
    8. Chains (for batch processing and macros)
    9. Chains of effects - for batch processing
    10. Chains of effects - for batch processing and macros
    11. Chains of effects (for batch processing)
    12. Chains of effects (for batch processing and macros)
    • Question: are search engines more likely to pick up on "batch processing" if we embed that in the page title rather than just carry it in the page and on the front page tagline?

FrenchFlagSmall.png Procesamiento en lotes Stapelverarbeitung

Intro - temporary H2 to simplify editing

Batch processing in Audacity is effected by processing a Chain of effects in preset order, either on tracks in the active Audacity project window or on a number of imported audio files. This can save time and repetitive effort. Chains are often used to batch process a group of audio files with the same sequence of effects or functions. Examples of typical usage:

  • Compressing the dynamic range of a number of WAV files, then converting them to MP3
  • Noise removing, bass boosting then normalizing a track or tracks in a project
Peter 28Jan13: ToDo-2 I'm going to change the above intro note to provide better information on the two (related) uses of chains> batch processing on files and macros on projects. I need to do some more thinking about it.

How to use Chains

In order to use batch processing it is necessary first to set up a Chain of effects using the Edit Chains command. A "Chain" is a sequence of automated commands similar to a "macro". Once the Chain has been set up you can then use the Apply Chain command to implement it.

Edit Chains

Enables you to either edit, remove or rename existing Chains, or add a new Chain. The Chain can include a number of common Audacity functions and effects to be executed in any order you specify. In many cases, the parameters for each command in the Chain can be specified within the Edit Chains window. Any built-in or Nyquist effect shown in the Effect Menu can be added to a chain, along with an Export command to save an audio file.

Edit Chains dialog box
Accessed by: File > Edit Chains...


Apply Chain

Enables you to select a Chain and apply it to either the entirety of the current project, to a single audio file or to a group of specially selected audio files.

Apply Chain dialog box
Accessed by: File > Apply Chain...