From 1b247dffff8e549d9d2b544fac687fd9b9dadcb2 Mon Sep 17 00:00:00 2001 From: Yann Leprince Date: Tue, 2 Jan 2018 12:34:34 +0100 Subject: [PATCH] Document new options to the replaygain sub-command --- docs/plugins/replaygain.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/plugins/replaygain.rst b/docs/plugins/replaygain.rst index 838a2ea2b..44246ed50 100644 --- a/docs/plugins/replaygain.rst +++ b/docs/plugins/replaygain.rst @@ -140,11 +140,15 @@ By default, the plugin will analyze all items an albums as they are implemented. However, you can also manually analyze files that are already in your library. Use the ``beet replaygain`` command:: - $ beet replaygain [-a] [QUERY] + $ beet replaygain [-Waf] [QUERY] The ``-a`` flag analyzes whole albums instead of individual tracks. Provide a query (see :doc:`/reference/query`) to indicate which items or albums to -analyze. +analyze. Files that already have ReplayGain values are skipped unless ``-f`` is +supplied. Use ``-w`` (write tags) or ``-W`` (don't write tags) to control +whether ReplayGain tags are written into the music files, or stored in the +beets database only (the default is to use :ref:`the importer's configuration +`). ReplayGain analysis is not fast, so you may want to disable it during import. Use the ``auto`` config option to control this::