Hi - I'm (still) trying to understand how volume levelling works.
I'm using MediaMonkey Gold v5 to catalogue and play my music - all in MP3 format. I've run 'Analyze Volume' on my entire catalogue and all my files now have Track Volume and Album Volume values in MM5.
As an experiment, I took three tracks with wildly different track volumes and made copies of them, then opened the copies in MP3tag and removed the values shown in the REPLAYGAIN_TRACK_GAIN, REPLAYGAIN_ALBUM_GAIN, and REPLAYGAIN_TRACK_PEAK tags. I then imported these back into MM5 - but the 'Track Volume' and 'Album Volume' columns in MM5 still show the old values, which I thought I'd removed in MP3tag.
So why is MM still showing the old values? Have I dleted the wrong values in MP3Tage? Or does MM5 keep a record of them somewhere else as well - I thought these values were only applied to tags.
Thanks
Check your file if it has APE tags and whether you read them in Ctrl-OTags>Mpeg
I can't see any - but do I have to set up specific columns or fields in order to do so?
Thanks
You could select a single file, open the extended tags dialogue and have a look at the dialogue title.
In the default configuration a Tag column is fairly far to the right.
If you want to create one, use
Value: %_tag_read%[ (%_tag%)]
or filter for files straightaway:
%_tag% HAS APE
Which way did you do it exactly?
Mediamonkey has a database. Did you delete this database and then reimport your testfiles?
No but I deleted the tracks from the database.
And no, there are no extended or APE tags.
It is not quite clear to me if you solved the problem.
No, not solved - but thanks.
I'm trying to get MM5 and Mp3Tag 'volume' tags aligned so that changes in Mp3Tag are reflected in MM5.
Could you supply one of the files that still shows the volume information even though you deleted that data?
My way of reasoning:
First make sure that the file is clean,
then see what MM makes of it.
If info can still be seen in MM -> MM problem, which may be solved by deleting the data base.
Hi, thanks for your patience. The track 'I's a Muggin' has been analysed by MM5 and the original is attached. I made a copy of the file, changed the artist and title fields so that MM5 wouldn't know it was the same, then opened it in MP3Tag and removed the REPLAYGAIN_TRACK_GAIN, REPLAYGAIN_ALBUM_GAIN, and REPLAYGAIN_TRACK_PEAK tags. I then added that track to the MM5 library - and it is shown with the volume tag information intact.
Both files and screenshots in the attched zip.
Examples.zip (411.4 KB)
Thank you for your efforts.
I checked both files with MP3tag, a hex editor and MP3diags.
The original file has the gain tag fields, the (copy) does not.
Also, the files seem to be ok as no unknown streams or other broken stuff is reported.
So you would have to check with MM.
Try to look at one of the test files when it has a really new file name so that the file appears to be a new file and see how that behaves.
OK - thanks so much for your help. I'll take it up with MM 
I'd like to add 2 things:
MM writes the RGAD-Tag which is not supported by Mp3Tag. You can see that there is this tag if you define a column in Mp3tag with the value %_id3v2_unknown_frames%. So when you delete gain-tags you see in the extended tag view of Mp3tag this tag will be left because Mp3tag does not show it.
The RGAD tag can be deleted in Mp3tag with cut-tag -> paste-tag.
Most people use lame to encode Mp3tags. Lame writes gain values to his header (not in Id3v2-tags) als long as you don't tell Lame to do not during encoding.
If MM sees this lame values and it writes anything to the files it will take these lame-gain-values and write them to the file as Id3v2 tags.
Thank you! That solved it.
I use DbPoweramp to rip my CDs, but I can't see anything in the settings about RGAD. Are you saying that as long as I use Lame the RGAD values will be written automatically, and there's nothing I can do about that?
Also, does MM use the existing RGAD values when analyzing volume, or does it do its own calculations?
Many thanks again!
These are 2 completely different things I put together in the answer because both can cause user-confusion with replaygain-tags.
Responsible for RGAD-frames is MM, not lame. Lame does not write RGAD-frames.
Lame simply writes some replay-infos to its header as long as you don't encode with the option "--noreplaygain". Lame is used by a lot of software for mp3-encoding and as far as I know these don't care about setting this disable-option.
These lame-header replaygain-infos have nothing to do with RGAD, but they can be the cause for replaygain-values combined with MM.
https://www.mediamonkey.com/forum/viewtopic.php?p=473604#p473604