Replay Gain

From Hydrogenaudio Knowledgebase
Revision as of 04:42, 14 October 2010 by Mjb (talk | contribs) (→‎foobar2000 Replay Gain scanner: more clarifications after checking into it further)

Replay Gain is the name of a technique invented to achieve the same playback volume of audio files. It specifies the reference level of 83dB (with the expectation that players would add 6dB at playback time)[1] and an algorithm to measure the perceived loudness of audio data.

Replay Gain allows the loudness of each song within a collection of songs to be consistent. This is called 'Track Gain', or 'Radio Gain' in earlier parlance. It also allows the loudness of a specific sub-collection (an "album") to be consistent with the rest of the collection, while allowing the dynamics from song to song on the album to remain intact. This is called 'Album Gain', or 'Audiophile Gain' in earlier parlance. This is usually important when listening to classical music albums, because quiet tracks need to remain a certain degree quieter than the louder ones.

Replay Gain is different from peak normalization. Peak normalization merely ensures that the peak amplitude reaches a certain level. This does not ensure equal loudness. The Replay Gain technique measures the effective power of the waveform (i.e. the RMS power after applying an "equal loudness contour"), and then adjusts the amplitude of the waveform accordingly. The result is that Replay Gained waveforms are usually more uniformly amplified then peak-normalized waveforms.

Clipping

Audio is generally recorded such that the loudest sounds don't clip, but the use of Replay Gain can cause clipping if the average volume of a song is below the target level. That is, upon playback, the volume of a quiet song is increased, so the parts of the song with above-average loudness, especially in the bass frequencies, will exceed the limits of the format and will be distorted. Whether this distortion is audible depends on the sounds in question, and the listener's sensitivity.

Implementations deal with the risk of clipping in different ways. Some have a "pre-amp" feature which reduces (or boosts) the original audio's level by a certain amount before doing whatever is needed for Replay Gain. Some have a "prevent clipping" feature to reduce the amount of Replay Gain adjustment to whatever amount would keep clipping from occurring, based on peak info stored in the file's metadata (thus reducing the effectiveness of Replay Gain). Some recommend using a compressor/limiter DSP to prevent or reduce clipping, regardless of whether it was caused by Replay Gain.

Implementations

There are different Replay Gain implementations, each with its own uses and strength. Most use metadata to indicate the level of the volume change that the player should make. Some modify the audio data itself, and optionally use metadata as well. There are advantages and disadvantages to both methods.

In the metadata method, information on both types of Replay Gain (Track Gain and Album Gain) can be stored. The volume-change information can be very precise. If audio data was also changed, the metadata can contain "undo" info. Not all audio players/decoders know how to read and use Replay Gain information stored in metadata. And there's no standard for where and how Replay Gain info is stored; each implementation uses different formats and puts the info in different locations.

In the audio data method, the file's actual audio data is modified so that its natural/default playback volume is at the target level. In this scenario, only one type of Replay Gain (Track Gain or Album Gain) can be applied. If no "undo" info is saved somewhere, it may not be possible to restore the original audio data. Limitations of the audio file format may prevent precise (finely tuned) gain adjustments with this method. For example, MP3 and AAC files can only be losslessly modified in 1.5 dB steps. Depending on the audio file format, the process may also be lossy in the sense that it could irreversibly push a signal above the format's maximum amplitude (resulting in clipping) or below the minimum (resulting in silence).

MP3Gain

MP3Gain is an implementation of Replay Gain. It can be used to just analyze files & recommend changes or to also modify the gain. If modifying the gain, it always modifies the audio data. It can add somewhat precise metadata, including undo info. The gain can be modified to any target dB, or it can be changed by a specified amount. For balance correction, user-specified changes can even be made on just one channel in simple L/R stereo-mode files (not joint stereo).

AACGain

AACGain is a modified version of MP3Gain that works on both MP3 and AAC files.

  • Format: MP3, AAC (with or without MP4 container)
  • Method: Audio + Meta, or Audio only
  • Limitations: Limited to 1.5dB steps mode, may become irreversible (same caveat as for MP3Gain)
  • http://altosdesign.com/aacgain/

LAME

Musepack Replay Gain

  • Method: Header (similar to Meta data method)
  • Notes: Replay Gain values are stored in the header and Replay Gain is part of the Musepack specifications; therefore any Musepack decoder that does not support Replay Gain can be considered broken.
  • http://www.musepack.net/

VorbisGain

Note: Andavari has provided a very useful script to integrate VorbisGain, which is a CLI tool, into Windows Explorer. Please (Ogg) check this section.

FLAC / METAFLAC

WavPack / WVGAIN

Wavegain

foobar2000 Replay Gain scanner

  • Format:
    • MP3: Values written to ID3v2 (default) or APEv2 tags. A separate function can be invoked to apply the tagged Track or Album Gain to the MP3 global gain fields (as MP3Gain does, but requiring tags first), and to rewrite the tags to account for the peak change and compensate for the difference from 89 dB. The 89 dB reference level for tags isn't configurable, but the reference level applied to the global gain fields is.
    • Musepack: Values written to header.
    • (Ogg) Vorbis: Values written to Vorbis comment.
    • WavPack: Values written to APEv2 tags.
    • AAC: Values written to APEv2 tags.
    • MP4: Uses its own iTunes-compatible tagging system (though iTunes does not support Replay Gain).
    • FLAC: Values written to Vorbis comment.
    • APE: Values written to APEv2 tags.
    • Modules (MOD etc.): Optionally saved into APEv2 tags.
  • http://foobar2000.org

MediaMonkey

  • Default behaviour is non-compliant with the ReplayGain standard http://replaygain.hydrogenaudio.org/calibration.html
    • Issue: Uses a reference value of 89dB rather than standard's 83dB
    • Workaround for v3.2.2: change values to 83dB at
      • in Options | Volume Levelling, all three Target Volume Level settings
      • in Options | Portable/Audio Devices for each device, Auto-Conversion, the Level volume when synchronizing setting.
  • Format:
  • In addition to tags, all Replay Gain values are also stored in MediaMonkey's MDB database
  • Does not support Album/Audiophile Replay Gain (Added to new MediaMonkey version 3
  • Also capable of (irreversibly) changing the volume of MP3 tracks, similar to MP3Gain
  • http://www.mediamonkey.com

Winamp Replay Gain scanner

Players support

Replay Gain being present in the specs of FLAC, Musepack, and APE formats, any player that support those formats usually support Replay Gain.

The situation with MP3 is rather different, as it was not part of the MP3 specs. The APEv2 tags metadata implementation is somewhat becoming the de-facto standard.

Windows

  • foobar2000 supports Replay Gain in all possible aspects.
  • Winamp supports Replay Gain in album or track mode.
  • MediaMonkey supports track Replay Gain only
  • XMPlay recently implemented Replay Gain

...and probably others.

Linux

For MP3, use the CVS version of the xmms-mad mp3 plugin (it's not yet released as binary, furthermore not available in distribs' versions for now. Meanwhile binaries are available here: custom binaries)
And possibly others, since TagLib added support for APEv2 tags in MP3 files, players using this library (like amaroK and JuK) might support that kind of Replay Gain tags in the near future.
Requires support to be enabled (via the appropriate python bindings and libraries) for the above formats. Does not support Replay Gain values stored in APEv2 tags in MP3s. Replay Gain values are stored in RVA2 id3v2.4 frames. See the Quod Libet RVA2 / Replay Gain notes.
foobar2000-style TXXX frames in MP3s are also supported in the latest development releases.
  • MPlayer. Mplayer support for Replay Gain is codec dependent.
Codecs that are known to support Replay Gain: vorbis
Because of this, you need to prioritize the codecs that support it, or choose it individually on the command line. To add it to the command line, add an -ac [codec] option after each file that you want to choose the codec for, or at the beginning to make it apply to all files listed. To prioritize the codecs by default, list them in a line in mplayer.conf:
ac=[codec],[othercodec],vorbis,mad,

Portable devices

Rockbox supports Replay Gain (in album or track mode) for most formats, including WMA, MP1/2/3, AAC, ALAC, Musepack, Monkey's Audio, Wavpack, FLAC and Vorbis.
Note that Replay Gain is only supported when using the respective codec's native tagging format. For example: Replay Gain stored in APEv2 tags is not supported for MP3, rather ID3v2.x tags are expected.

Sandisk Sansa Fuze with firmware 1.02.26 and 2.02.26

Sandisk Sansa Clip+

The iPod features Soundcheck, which seems to produce roughly the same normalization gains as Replay Gain, but doesn't provide an Album Gain.

Hi-Fi

Slim Devices a company owned by Logitech Inc, supports Replay Gain on both of their hi-end audiophile players, known as the Transporter and the Squeezebox.

Notes

  1. ↑ However, the de facto standard has been for the reference level to simply be 89dB and for players not to add anything extra.[1]

External links

Retrieved from "https://wiki.hydrogenaud.io/index.php?title=Replay_Gain&oldid=22007"