How to Normalize OGG Vorbis Files with VorbisGain

MP3Gain refuses .ogg files, and there is a principled reason why: the OGG Vorbis world solved the loudness problem the opposite way. Where MP3Gain bakes the adjustment into the audio frames so that any player plays the file at the right volume, VorbisGain writes the ReplayGain values into the file’s comment tags and trusts the player to apply them at playback. Nothing in the audio is ever rewritten. This guide explains how VorbisGain works, how to run it for tracks and albums, and — crucially — where its tag-based approach succeeds and where it silently does nothing.

Two philosophies: change the file, or inform the player

The contrast is worth understanding before you tag a whole library, because it decides whether you hear any difference at all. MP3Gain’s file-level approach (explained in Is MP3Gain Lossless?) modifies a gain field that decoders must read, so the leveling is universal but the file is changed — reversibly, thanks to its undo tag. VorbisGain, originally written by Gian-Carlo Pascutto, never touches the encoded audio. It performs the same ReplayGain analysis, then stores the results as ordinary Vorbis comments inside each file — fields such as REPLAYGAIN_TRACK_GAIN, REPLAYGAIN_TRACK_PEAK, and their album counterparts. A player that supports ReplayGain reads those values and adjusts its output volume on the fly; a player that doesn’t, plays the file exactly as encoded, tags notwithstanding.

Neither philosophy is wrong. Tag-based leveling is non-destructive by construction — delete the comments and the file is bit-identical to the original — and it is the same design that FLAC normalization uses. File-level leveling is the only design that works on hardware and software you don’t control. Choose per library, per destination.

Running VorbisGain

VorbisGain is a small command-line tool; its project home is on sjeng.org, and Rarewares hosts more recent compiles for Windows. The everyday usage is simple:

• Single tracks: vorbisgain *.ogg analyzes each file in the folder and writes its track gain and peak tags.
• Albums: add the album switch — vorbisgain -a *.ogg — so the files are treated as one album: album gain is computed from the whole set, preserving the intended loudness differences between tracks while leveling the album against the rest of your collection.
• Folders: the recursive switch (-r) walks subdirectories, which is how you tag an existing artist/album folder tree in one pass.
• Undoing: because nothing but comments was written, removing the ReplayGain fields with any tag editor returns the files to their original state. There is nothing to reverse-engineer.

Graphical alternatives exist: foobar2000’s ReplayGain scanner writes the identical tags to OGG files (select files, right-click, ReplayGain), and newer multi-format scanners cover Vorbis alongside FLAC and Opus. The values are the standard ones regardless of which tool writes them — what matters is the player at the other end.

Verifying the tags, and two habits worth keeping

Because VorbisGain changes nothing audible in the file itself, verify its work by reading the tags, not by listening. Any tag viewer — or foobar2000’s properties dialog — should show the REPLAYGAIN_* fields after a run; if a file lacks them, it was skipped or the run targeted the wrong folder. Two habits prevent the common disappointments. First, decide track versus album before the big run: tagging a folder file-by-file and later wishing you had album values means rescanning, not editing, because album gain is computed from the set as a whole. Second, remember that the peak value VorbisGain stores is what allows a player to refuse a gain increase that would clip; if your player offers a “prevent clipping” style option alongside ReplayGain, leave it on — a track that stays a decibel shy of the target is a better outcome than a distorted one. Finally, a note on file hygiene: since the comments are ordinary metadata, careless tag editing with tools that rewrite the whole comment block can strip ReplayGain fields without warning. If a leveled album suddenly plays unevenly after a retagging session, check the fields before blaming the player.

Where it works — and where it silently doesn’t

Support in the open-source ecosystem is strong: foobar2000, most Linux desktop players, and many Android players read Vorbis ReplayGain tags and apply them faithfully, album mode included. The weak spots are the same as for every tag-based system — car head units, minimalist hardware players, and some streaming boxes ignore the tags entirely, with no warning and no error. If your tagged OGGs “didn’t normalize” in the car, the tags are almost certainly fine; the player simply never looked at them.

For those destinations there is no lossless rescue: a file-level adjustment for Vorbis would require decoding and re-encoding with the gain applied, costing a generation of lossy quality. The pragmatic answers are to keep the master library tagged and pristine, and to export converted copies — re-encoded at a fixed level, or converted to MP3 and run through MP3Gain — for the tag-blind device. That is a deliberate trade, made on copies, with the originals intact.

One more support nuance is worth knowing before you judge the results: partial support exists. Some players read track gain but not album gain, flattening albums even though both values are present — and they are present, because VorbisGain writes the track values alongside the album ones, so track-mode players behave sensibly too. Others apply the tags but ignore the stored peak, which can let a heavily boosted quiet track clip on playback; if your player exposes a preamp or clipping-prevention setting, a decibel or two of headroom there is cheap insurance. None of this is discoverable from the files themselves — it only shows up in listening — which is why the tag-based formats reward a ten-minute test on your actual playback chain before you commit the whole library to the workflow.

One family footnote: OGG containers carrying Opus audio use a sibling system

To sum up the working rule for Vorbis libraries: tag everything with VorbisGain (or your scanner of choice), album mode for albums, and trust the method exactly as far as your playback chain honors tags. The audio files themselves will still be the same pristine encodes you started with — which, for a format chosen by people who care about open standards and sound quality, is rather the point.