Error: unexpected end of file in WAV

[simoncn]

(21-12-2014 23:25)glevethan Wrote:  "It looks like the COMM size value was encoded using the ID3v2.4 format encoding rules instead of the ID3v2.3 format encoding rules. (The ID3v2 tag in this file is an ID3v2.3 tag.) If the COMM size field in the file is decoded according to the ID3v2.4 rules, this produces the correct value of 211"

Metadatics has an option to choose the standard used to write WAV tags. I changed it from ID3v2.4 to IDSv2.3 (as you said the tag in the file is a v2.3 version). Still no luck

You are better off staying with the default of writing ID3v2.4 tags. The ID3v2.3 specification has some problems with how multiple values are handled. These problems are fixed in ID3v2.4.

The problem that I described earlier is caused by the Qobuz file containing an improper mixture of ID3v2.3 and ID3v2.4. If Metadatics is writing a correct ID3v2.4 tag, this will work with MinimServer.