Ivolume itunes
I hope this helps and that the Replay/Gain module can be fixed so that it works correctly so that there is a batch way of handling this from now on using the EBU R128 standard.I just looked at these one last time after reviewing the m4a files and it literally is as simple as making the 8 digit hex values in the 7th and 8th position all zeroes (shown in bold above).that worked for mp3 files as well. I also know from this experiment that MP3Tag IS NOT truly writing the COMMENT ITUNNORM tag as a comment which is why it did not work when I copied the COMMENT ITUNNORM field that iVolume wrote to a virgin track. I'm not sure what all the different numbers are supposed to mean but it doesn't appear to matter. Using the same hex editor, I simply made all of the hex numbers the same 0000023A and iTunes showed the correct volume when I imported the tag (note that I did this because that is how MP3Tag writes the values for m4a files and that works). So, given all of this I now know that dBPowerAmp IS NOT converting the Album Gain correctly to the hexidecimal numbers that iTunes uses. I then made the COMMENT ITUNNORM tag the same as what was written by iVolume and when I imported that file into iTunes it gave the right value. So I then took it a step further and took the original file after dBPowerAmp did it's replay/gain calculation that had not been touched at all by MP3Tag and opened it in a hex editor.
![ivolume itunes ivolume itunes](http://3.bp.blogspot.com/-mjb6Dv-5P-c/VWgUmw1ZfnI/AAAAAAAAQZk/7VSR4O52phY/s1600/SS%2B2015-05-29%2B16.25.38.jpg)
The funny thing is that if I copy the hex numbers from iVolume tag to the dBPowerAmp file using MP3Tag, the SoundCheck value that comes up in iTunes does not change. The last (6) sets of hex numbers are completely different so I don't know what is going on there. I manipulated iVolume so that it was writing the same volume as I was getting from dBPowerAmp. I did not see any further updates to this so I started experimenting again figuring it must be something in the way that dBPowerAmp and other programs are writing the tag.