# REPLAY GAIN\_\_\_ ALBUM/TRACK **URL:** \ **Category:** Support\ **Created:** [March 27, 2010, 2:17pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189 "2010-03-27T14:17:31Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![thorsonb](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/e9a140/32.png) [@thorsonb](https://community.mp3tag.de/u/thorsonb)\ **Post date:** [March 27, 2010, 2:17pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/1 "2010-03-27T14:17:31Z")
How can I add a column to view the fields tittled: REPLAYGAIN\_ALBUM\_GAIN REPLAYGAIN\_TRACK\_GAIN REPLAYGAIN\_TRACK\_PEAK ???... I Level the volume of my Tracks using _MediaMonkey_.. but it seems that not all my tracks get leveled.. (of the leveling isnt stored to the audio file) Or does this have to do with the mp3 files them self?? \<\< i still dont know the difference between "ID3v2.3 //ID3v1 // ID3v1 Lyrics3v2 // etc// etc//..... Could that be the issue I am having? **P.s. Im using Mp3Tag v2.44 (Aug 14, 2009 version)** ---
**Author:** ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)\ **Post date:** [March 27, 2010, 2:35pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/2 "2010-03-27T14:35:40Z")
> [@ThorsonB](#): > > ... How can I add a column to view the fields tittled: > REPLAYGAIN\_ALBUM\_GAIN > REPLAYGAIN\_TRACK\_GAIN > REPLAYGAIN\_TRACK\_PEAK ... From my view - in this case - a simple way to add some columns to Mp3tag listview is: Use an editor and fill in the needed sections manually into the Mp3tag columns.ini file. [#57] width=69 numeric=1 name=AlbumGain value=%REPLAYGAIN\_ALBUM\_GAIN% sort=$replace(%REPLAYGAIN\_ALBUM\_GAIN%,'.',) field= enabled=1 [#58] width=71 numeric=1 name=AlbumPeak value=%REPLAYGAIN\_ALBUM\_PEAK% sort=$replace(%REPLAYGAIN\_ALBUM\_PEAK%,'.',) field= enabled=1 [#59] width=71 numeric=1 name=TrackGain value=%REPLAYGAIN\_TRACK\_GAIN% sort=$replace(%REPLAYGAIN\_TRACK\_GAIN%,'.',) field= enabled=1 [#60] width=79 numeric=1 name=TrackPeak value=%REPLAYGAIN\_TRACK\_PEAK% sort=$replace(%REPLAYGAIN\_TRACK\_PEAK%,'.',) field= enabled=1 Take care not to change any other content in the columns.ini file. Change the section numbers (see example #57..#60), so that all section numbers will be continously running numbers fitting into your personal columns.ini. The columns.ini file can be opened with Notepad using the filename: %appdata%\Mp3tag\data\columns.ini DD.20100327.1635.CET ---
**Author:** ![thorsonb](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/e9a140/32.png) [@thorsonb](https://community.mp3tag.de/u/thorsonb)\ **Post date:** [March 28, 2010, 10:28am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/3 "2010-03-28T10:28:17Z")
> [@DetlevD](#): > > From my view - in this case - a simple way to add some columns to Mp3tag listview is: > Use an editor and fill in the needed sections manually into the Mp3tag columns.ini file. > > [#57] > width=69 > numeric=1 > name=AlbumGain > value=%REPLAYGAIN\_ALBUM\_GAIN% > sort=$replace(%REPLAYGAIN\_ALBUM\_GAIN%,'.',) > field= > enabled=1 > > [#58] > width=71 > numeric=1 > name=AlbumPeak > value=%REPLAYGAIN\_ALBUM\_PEAK% > sort=$replace(%REPLAYGAIN\_ALBUM\_PEAK%,'.',) > field= > enabled=1 > > [#59] > width=71 > numeric=1 > name=TrackGain > value=%REPLAYGAIN\_TRACK\_GAIN% > sort=$replace(%REPLAYGAIN\_TRACK\_GAIN%,'.',) > field= > enabled=1 > > [#60] > width=79 > numeric=1 > name=TrackPeak > value=%REPLAYGAIN\_TRACK\_PEAK% > sort=$replace(%REPLAYGAIN\_TRACK\_PEAK%,'.',) > field= > enabled=1 > > Take care not to change any other content in the columns.ini file. > Change the section numbers (see example #57..#60), so that all section numbers will be continously running numbers fitting into your personal columns.ini. > > The columns.ini file can be opened with Notepad using the filename: > %appdata%\Mp3tag\data\columns.ini > > DD.20100327.1635.CET **Your a genius! Thanks .. lol** . ---
**Author:** ![gggirlgeek](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/3ab097/32.png) [@gggirlgeek](https://community.mp3tag.de/u/gggirlgeek)\ **Post date:** [December 25, 2010, 8:42am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/4 "2010-12-25T08:42:30Z")
+1 from me too! Please add this column as an option in Mp3tag. I see replay\_track\_gain in the extended tags but it's not in the list to add it to custom columns. Very frustrating. This field is essential to me for selecting between duplicates automatically with a very large collection. It is a much better indicator of sound quality than bitrate if you don't have time to listen to 100's of tunes. I have often found that a 168kbps file will sound better than a 320kbps file due to recording/ripping quality. The high bitrate is just an attempt to compensate for the terrible sound. VBR files also make it tricky to eliminate low bitrate files. It is not foolproof of course but it get's closer to judging whether the file was ripped from the original recorded media, or copied several times over. It is based on the likelihood that the louder file will have a greater range of sound in it, therefore less of the original data was removed for compression. The same holds true if the original recording was better. Volume normalizing level also applys to all audio formats, so no guess work between your mp3's, m4a's, and wma's. I run all of my files through Media Monkey's volume leveling when they are added to my library. The files with a replay\_track\_gain higher than +6db are usually lower in quality than the rest of my collection -- it's very noticeable. There are exceptions but it's rare. Classical music for example, doesn't seem to stick to this rule. 70's music always seems to need a great deal of volume boosting unless you can find a remastered recording. Hope this helps some folks. ---
**Author:** ![garym](https://community.mp3tag.de/user_avatar/community.mp3tag.de/garym/32/4822_2.png) [@garym](https://community.mp3tag.de/u/garym)\ **Post date:** [December 25, 2010, 1:17pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/5 "2010-12-25T13:17:02Z")
But you can add this with custom columns. Right click on the column heading, then choose custom columns, then click on NEW to add a column. Name it "track replaygain" and enter the following as both the value and field: %REPLAYGAIN\_TRACK\_GAIN% Then do the same and label a new column "Album replaygain" and add the following as value and field: %REPLAYGAIN\_ALBUM\_GAIN% I've done this and these columns now always show up when I use mp3tag. ---
**Author:** ![gggirlgeek](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/g/3ab097/32.png) [@gggirlgeek](https://community.mp3tag.de/u/gggirlgeek)\ **Post date:** [January 31, 2011, 5:35am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/6 "2011-01-31T05:35:47Z")
OK, thanks for the reply. I have copied this to my notes and will try it when I am less busy. Thanks again. ---
**Author:** ![Freddy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://community.mp3tag.de/u/Freddy)\ **Post date:** [July 15, 2022, 11:56am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/7 "2022-07-15T11:56:41Z")
> [@garym](#): > > But you can add this with custom columns. Right click on the column heading, then choose custom columns, then click on NEW to add a column. Name it "track replaygain" and enter the following as both the value and field: > %REPLAYGAIN\_TRACK\_GAIN% > > Then do the same and label a new column "Album replaygain" and add the following as value and field: > > %REPLAYGAIN\_ALBUM\_GAIN% > > I've done this and these columns now always show up when I use mp3tag. ...and to make the column sort correctly, tick the "Numeric" box and put the following string in the "Sort by" field: $regexp($cutRight(%REPLAYGAIN\_TRACK\_GAIN%,3),\.,) This is designed for gain text which looks like "[+|-]nn.nn dB", so the " dB" gets removed and then the decimal point is removed. By experiment, I discovered MP3Tag can sort integers with leading signs, but not decimals. Update: as per subsequent posts, this simpler expression works: $regexp(%REPLAYGAIN\_TRACK\_GAIN%,\.,) NB: in order to post a backslash, I had to escape the backslash with a backslash. Bear that in mind if copy-and-paste produces a double backslash (there should only be one). ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [July 15, 2022, 12:01pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/8 "2022-07-15T12:01:52Z")
> [@Freddy](#): > > $regexp($cutRight(%REPLAYGAIN\_ALBUM\_GAIN%,3),.,)... so the " dB" gets removed and then the decimal point is removed $num(%REPLAYGAIN\_ALBUM\_GAIN%,2) would probably achive the same. ---
**Author:** ![Freddy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://community.mp3tag.de/u/Freddy)\ **Post date:** [July 15, 2022, 12:33pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/9 "2022-07-15T12:33:29Z")
> [@ohrenkino](#): > > $num(%REPLAYGAIN\_ALBUM\_GAIN%,2) would probably achive the same. It doesn't. However, there is no need to remove the suffix text. This works: $regexp(%REPLAYGAIN\_TRACK\_GAIN%,\.,) ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [July 15, 2022, 12:37pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/10 "2022-07-15T12:37:07Z")
$num(12.45 db,2) -\> 12 $num(-12.45 db,2) -\>-12 $num("12,45 db",2) -\> 12 What was it that you needed? The complete number without the decimal indicator? ---
**Author:** ![Freddy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://community.mp3tag.de/u/Freddy)\ **Post date:** [July 15, 2022, 12:40pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/11 "2022-07-15T12:40:10Z")
No. If you ignore the numerics after the decimal point, the dB values are no longer sorted, only binned in integer values. And there is a leading sign. However, there is no need to remove the suffix text. This works: $regexp(%REPLAYGAIN\_TRACK\_GAIN%,\.,) ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [July 15, 2022, 12:48pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/12 "2022-07-15T12:48:46Z")
If you remove the dot and sort numerically, then 9.94 and 99.4 will end up close to each other. As you replace the string constant dot with nothing, a plain $replace() is enough, the result will still be not as accurate. If you don't do anything and leave 9.94 and 99.4 as they are and then sort with "numeric" enabled, both values are separated again. ---
**Author:** ![Freddy](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/3d9bf3/32.png) [@Freddy](https://community.mp3tag.de/u/Freddy)\ **Post date:** [July 15, 2022, 12:51pm UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/13 "2022-07-15T12:51:24Z")
The dB values obtained from the Replay Gain scanner in Foobar2000 always have two decimal places, so that is not an issue (at least, not for me). Otherwise a correct sort would require additional string processing to ensure a constant number of decimal places. The range of values in my library are "-13.51 dB" to "+4.63 dB", always with a sign and always with two decimal places. Removing the DP results in a correct numeric sort. ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [July 10, 2023, 6:50am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/16 "2023-07-10T06:50:23Z")
A post was split to a new topic: [Purpose and meaning of Replaygain values](https://community.mp3tag.de/t/purpose-and-meaning-of-replaygain-values/61505) ---
**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\ **Post date:** [July 10, 2023, 7:39am UTC](https://community.mp3tag.de/t/replay-gain-album-track/10189/17 "2023-07-10T07:39:15Z")