[digidigi]

XBMC only respects ReplayGain information in files if the tags within those files are stored in lower case.

So... this:replaygain_track_gain
instead of this: REPLAYGAIN_TRACK_GAIN

The issue here is, many apps that process MP3s write the info in upper case. The standard/spec also suggests that the tags be upper case: http://wiki.hydrogenaudio.org/index.php?...cification

This can be recreated by copying an mp3 and having ReplayGain calculated (with foobar, or MusicBee, for example) on it. Then play it back in XBMC and compare it with the opriginal. Both will sound the same. Edit the file in a hex editor and change the case of the tags from upper to lower case, and then compare the files.... The volume will now be adjusted correctly.

Is it possible to get XBMC to honor metadata written in upper case?

[un1versal]

This sounds like a bug in this case, and in such case you need way more than just this post.

See http://forum.xbmc.org/showthread.php?tid=34655 thats mainly for Linux but you get an idea waht info is more or less required for any sort of report.

[scott967]

This sounds like a bug in this case, and in such case you need way more than just this post.

See http://forum.xbmc.org/showthread.php?tid=34655 thats mainly for Linux but you get an idea waht info is more or less required for any sort of report.

Looking at TagLoaderTagLib.cpp it appears for some reason lower case is used in ID3v2 and ASF tags, but upper case in xiph (flac) and APE tags. There aren't any requirements referenced, so don't know where/how that was determined. I suspect that the foobar requirements for replaygain probably are as authoritative as anything. Meanwhile, MP3tag is a good tool to convert the tags if that is acceptable to OP. Note: you should see in a debug log that the tags weren't understood by the parser.

scott s.
.

[digidigi]

Thanks, Scott, I found the same thing.

If anyone is interested, there's a discussion of the ReplayGain methods, and how I discovered the original issue over on the MusicBee forums.

I need to figure out the intricacies of capturing/finding log files and I will then make a bug report for this.

I suppose I could register as a developer and make the fix myself, but I am guessing that's quite a process... I'll have to look into it anyways

[Martijn]

perhaps create a trac ticket on http://trac.xbmc.org so they can look at if it needs to be case sensitive or not.
make sure you have tested it with Gotham nightly version

[jmarshall]

Your wish, yada, yada:

https://github.com/xbmc/xbmc/pull/4253

[digidigi]

Thanks so much! I will look for the fix in an upcoming release. Cheers!

[protomucca]

Hi All, is this issue solved? I'm having the same problem with Kodi 17.0 RC1. Thanks
Daniele

[DaveBlake]

Yes this specific issue was fixed back in 2014, so clearly you are not having the same problem with 17.0 RC1

Rather than ressurecting old threads, please create a new thread and explain with as much information as possible the issue that you are experiencing.