12/24/2023 0 Comments Ivolume not working songSo 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. 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. I would also be very interested in feedback on this issue from garym, as I believe he creates his mp3 library with RG values in a similar manner. Hopefully, Spoon and/or PeterP can shed more light on this issue. So, I suspect you have highlighted a problem, although it is my suspicion that the problem possibly exists with changes made in iTunes releases after, in the way that those releases handle imported mp3 files with SoundCheck values. I would add, that I am unable to determine the iTunes release versions I had installed on the dates I have specified, although I tend to keep iTunes updated regularly. However, all Songs imported after show incorrect Volume values, similar to the issue you have posted here. I sorted all Songs in iTunes by Date Added and noticed that all Songs I imported into iTunes before show correct Volume values. The ReplayGain tags in these files are created using the dBpoweramp ReplayGain DSP setting set to Track, Album & iTunes Album Normalization.Īfter reading this thread, I decided to have a quick look at the Volume values in my Songs in iTunes. I'm stumped and hoping that someone can comment on why this is happening. The really confusing thing is that iVolume appears to be writing to the same field. As you can see from these two examples, there is no setting I could do that would provide a happy medium for these (2) albums. I had another that iVolume added +2.5 dB (caused clipping) when Replay/Gain reduced -0.3 dB. ![]() I have one album that iVolume was adding a crazy +15 dB (caused clipping) but Replay/Gain would only add +8dB. I know some will say it is the same thing but I assure you that it's not. ![]() I tried using iVolume in the past with album gain and default 90 dB setting but it does not seem to work nearly as well as Replay/Gain. all of the others that have not (tried about 30 other files). I also can't really find any difference in the file that worked vs. I also managed to get a single MP3 file to work with foobar2000 but have not been able to get any others. However, as far as I can tell it appears to be writing the fields the same as dBPowerAmp so I don't understand why one works and not another. ![]() I managed to get AAC files to work with foobar2000 v1.4.8 but still can't get MP3 files to work. Is it possible to get this bug in the Replay Gain utility fixed? I was hoping to batch convert my entire song library of 25,000+ to save me a ton of time and effort and now that does not look like that will work. Now I created an action within MP3Tag to write the ITUNNORM value based on the album gain value. ITunes says the volume = -1.0 dB (ie when I import this track it is doing the sound check analysis) For an example track, I get the values below from the dBPowerAmp utility: The Replay Gain Utility says that it can write the iTunes tag but the volume values are not showing correctly in iTunes. I am trying to use the Replay Gain utility to normalize my music in iTunes (files are lossy aac in a.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |