by kemenyadi » Wed Feb 07, 2018 1:55 pm
What/how I am tagging: I select multiple tracks (in an album/artist, etc) and empty the album artist field (this may be and is probably irrelevant).
As the tagging process goes through all the albums of an artist, it doesn't necessarily bloat every single file/album. Only certain albums end up bloated. I have not found any indication as to which files/albums are 'tagged' differently, and why. Certain albums are recursively bloated. Eg: I have files that are 9000kbit instead of a standard ~1000kbit 44.1/16 ape file. They remain playable, and I can manually fix these files by re-encoding them but I can't keep up with all the files being bloated in the library. The bloat is just compressible data, a bloated file compressed in a rar/7z archive is very similar in size to the original file.
To further complicate things the increased bitrate/filesize does not show up in MM!
I have PMed you two with samples.
What/how I am tagging: I select multiple tracks (in an album/artist, etc) and empty the album artist field (this may be and is probably irrelevant).
As the tagging process goes through all the albums of an artist, it doesn't necessarily bloat every single file/album. Only certain albums end up bloated. I have not found any indication as to which files/albums are 'tagged' differently, and why. Certain albums are [b]recursively bloated[/b]. Eg: I have files that are 9000kbit instead of a standard ~1000kbit 44.1/16 ape file. They remain playable, and I can manually fix these files by re-encoding them but I can't keep up with all the files being bloated in the library. The bloat is just compressible data, a bloated file compressed in a rar/7z archive is very similar in size to the original file.
To further complicate things the increased bitrate/filesize does not show up in MM!
I have PMed you two with samples.
