Threaded Mode | Linear Mode

glevethan · 21-12-2014, 17:15

(21-12-2014 08:54)simoncn Wrote:
(21-12-2014 01:13)glevethan Wrote: OK - file is being uploaded as we speak. This is the official straight from Qobuz file.
Here is what the error log generated for this file

Error: ID3v2 'COMM' frame has invalid size 339 at offset 336 in file D'Angelo/01-03-D_Angelo-The_Charade-SMR.wav (length 115700268)

As the message says, the COMM frame in the ID3v2.3 tag has an incorrect size value of 339. From looking at the contents of the file, this value should be 211.

It seems that XLD got confused by this and made a bigger mess when trying to fix it.

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.

I hope this information is useful to Qobuz in fixing their file encoding bug.

Hi Simon

Thank you for the analysis. Based on my rudimentary understanding it appears that the value for the "comment" field in the tag contains an incorrect value which was not calculated following proper tagging rules. This leads me to question how many WAV files which Qobuz sells suffer from the same issue. I also wonder if there is a way for Minimserver to be able to "deal" which errors such as these. If only a small percentage of the millions of music files which Qobuz (and other sellers) provide have similar problems this creates a nightmare for the end user. Legitimately purchased WAV files will not be loaded by Minimserver and subsequently not be displayed by the control point. I guess I can now further appreciate the many comments which indicate a preference in the way FLACS files handle tagging when compared to WAV. In fact the same purchased file downloaded in FLAC did not present any problem.

I wonder if there is a program which will analyze and correct tagging errors so Minimserver does not hiccup. I use Metadatics to tag under Mac OS however I used to run MP3Tag when I used DbPoweramp on the Mac in a Virtual Machine under VMWareFusion. Since Spoon now has a working version of his program for Mac OS I no longer have the need to run VMWare and Windows - thank god.

Best
Gregg

simoncn · (This post was last modified: 21-12-2014 18:00 by simoncn.)

(21-12-2014 17:15)glevethan Wrote: Hi Simon

Thank you for the analysis. Based on my rudimentary understanding it appears that the value for the "comment" field in the tag contains an incorrect value which was not calculated following proper tagging rules. This leads me to question how many WAV files which Qobuz sells suffer from the same issue. I also wonder if there is a way for Minimserver to be able to "deal" which errors such as these. If only a small percentage of the millions of music files which Qobuz (and other sellers) provide have similar problems this creates a nightmare for the end user. Legitimately purchased WAV files will not be loaded by Minimserver and subsequently not be displayed by the control point. I guess I can now further appreciate the many comments which indicate a preference in the way FLACS files handle tagging when compared to WAV. In fact the same purchased file downloaded in FLAC did not present any problem.

I wonder if there is a program which will analyze and correct tagging errors so Minimserver does not hiccup. I use Metadatics to tag under Mac OS however I used to run MP3Tag when I used DbPoweramp on the Mac in a Virtual Machine under VMWareFusion. Since Spoon now has a working version of his program for Mac OS I no longer have the need to run VMWare and Windows - thank god.

Best
Gregg

The file is faulty and it is the responsibility of Qobuz to fix it. This is no different from any other faulty product you might have purchased from any vendor. If you report this to Qobuz with the information I have provided, Qobuz should be able to fix the problem and provide you with a correct download.

In general, it isn't possible for MinimServer to correct errors such as these. Instead, MinimServer is telling you about the fault and rejecting the faulty file to protect MinimServer from crashing when you access the faulty file. This is not a "hiccup" but a key feature of MinimServer as described in the section "Take control of your tagging" on this page.

glevethan · 21-12-2014, 18:01

Thanks for the link to "Take control of your tagging". I agree that it is the responsibility of Qobuz ( and HDTracks etc..) to provide the customer with properly tagged files. I wonder whether it is the resellers who tag the files or rather the record labels which provide them already tagged (me thinks the later). I guess it's just par for the course today. The only reason I am even messing with the WAV version of this is to compare it to the FLAC version to see if the sound quality is any better. I guess the easiest way to accomplish this would be to simply use Minimservers on the fly transcoding option.

simoncn · 21-12-2014, 18:16

(21-12-2014 18:01)glevethan Wrote: Thanks for the link to "Take control of your tagging". I agree that it is the responsibility of Qobuz ( and HDTracks etc..) to provide the customer with properly tagged files. I wonder whether it is the resellers who tag the files or rather the record labels which provide them already tagged (me thinks the later). I guess it's just par for the course today. The only reason I am even messing with the WAV version of this is to compare it to the FLAC version to see if the sound quality is any better. I guess the easiest way to accomplish this would be to simply use Minimservers on the fly transcoding option.

It's unfortunate that you happened to choose a WAV file with faulty tagging for your test and even more unfortunate that trying to fix it with XLD created another format error. Do you have access to dBpoweramp? This usually works well for fixing format errors.

simoncn · 21-12-2014, 18:19

(21-12-2014 18:16)simoncn Wrote: Do you have access to dBpoweramp? This usually works well for fixing format errors.

I was able to fix the format error using dBpoweramp and load the file into MinimServer successfully.

glevethan · 21-12-2014, 22:59

As suggested I ran the files through DbPoweramp and converted WAV to WAV. They were fixed and loaded properly in Minimserver. The new problem is now with tagging. I ran a file through Metadatics (the tagging program most seem to use on a Mac) and tried to add cover art and change the name of the album. This generated an error and Minimserver did not load the track.

There is an option in Metadatics to strip all tag information from a file. I stripped everything and then retagged. The file still did not load.

To summarize I can now get the WAV file to load in Minimserver - I cannot fix the tag i.e. add cover art, change album name etc. Any suggestions? I really do not want to boot into windows on my other laptop and try MP3Tag (and who even knows if that will work).

Sorry for taking up your time with a minor problem. I will understand if you do not want to spend any further time on this - after all the FLAC files work without any issues so it is not like I am in a bind. Just curiosity on how to correct this problem should it arise again (as I am sure it will with other commercially purchased tracks).

Best
Gregg

glevethan · 21-12-2014, 23:25

"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

simoncn · 21-12-2014, 23:44

(21-12-2014 22:59)glevethan Wrote: As suggested I ran the files through DbPoweramp and converted WAV to WAV. They were fixed and loaded properly in Minimserver. The new problem is now with tagging. I ran a file through Metadatics (the tagging program most seem to use on a Mac) and tried to add cover art and change the name of the album. This generated an error and Minimserver did not load the track.

What is the exact error message frpom MinimServer?

simoncn · 21-12-2014, 23:51

(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.

simoncn · 22-12-2014, 00:06

(21-12-2014 22:59)glevethan Wrote: To summarize I can now get the WAV file to load in Minimserver - I cannot fix the tag i.e. add cover art, change album name etc. Any suggestions? I really do not want to boot into windows on my other laptop and try MP3Tag (and who even knows if that will work).

I think there is a good chance that running this file (as edited by Metadatics) through a dBpoweramp WAV to WAV conversion will enable it to load in MinimServer and will retain the changes that Metadatics has made.