Excellent work. I hope spoon can take a look at this and fix things on the dbpa side.
Excellent work. I hope spoon can take a look at this and fix things on the dbpa side.
Just to be safe, I checked over what dBPa does with m4a files as well and that is not working quite right either. For this particular track, the calculated album gain is +2.33
dBPa ITUNNORM = 00000248 00000248 000005B4 000005B4 00024CA8 00024CA8 00007FFF 00007FFF 00024CA8 00024CA8 (imports to iTunes as -1.0 dB)
iVolume ITUNNORM = 00000252 00000252 000005CC 000005CC 00024CA8 00024CA8 00000000 00000000 00024CA8 00024CA8 (imports to iTunes as +2.3 dB)
I added bold to the parts of the field hex values that matter. If I change the dBPa bold values to be 00000000 00000000 as they are in the iVolume field, then the iTunes track imports correctly.
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. This seems like it would be an easy global change to the way dBPa is writing these values...
Now fixed in latest beta:
https://forum.dbpoweramp.com/showthr...7-Windows-Beta
Spoon
www.dbpoweramp.com
If you install R17 beta it replaces the DSP which is used by the utility codec, fixing it also.
Spoon
www.dbpoweramp.com
I have tested it out several times now and it appears to work correctly. Thanks for getting this updated so quickly Spoon...
Copyright © illustrate 2024, All rights reserved