(10-08-2014 17:56)simoncn Wrote: [ -> ]Thanks for the offer to upload a file, but there is no point uploading a file that doesn't produce an error message.
I still haven't quite gotten it firmly in my head that restart and rescan are no longer identical. I guess I did a restart after installing the update. A rescan shows the same old errors in the log. I uploaded one of the files -- look for 'wave error.zip'.
(11-08-2014 00:00)magister Wrote: [ -> ] (10-08-2014 17:56)simoncn Wrote: [ -> ]Thanks for the offer to upload a file, but there is no point uploading a file that doesn't produce an error message.
I still haven't quite gotten it firmly in my head that restart and rescan are no longer identical. I guess I did a restart after installing the update. A rescan shows the same old errors in the log. I uploaded one of the files -- look for 'wave error.zip'.
Thanks very much!
This file violates the WAV specification because it contains an "id3" chunk (used for tag data) that contains an odd number of bytes and doesn't include a pad byte at the end of the chunk. According to the WAV specification, all chunks with an odd number of bytes must include a pad byte with value zero at the end of the chunk.
(11-08-2014 07:33)simoncn Wrote: [ -> ]This file violates the WAV specification because it contains an "id3" chunk (used for tag data) that contains an odd number of bytes and doesn't include a pad byte at the end of the chunk. According to the WAV specification, all chunks with an odd number of bytes must include a pad byte with value zero at the end of the chunk.
If this formatting error applies to the last chunk in the file, MinimServer could detect the error and ignore it. If the error applies to any other chunk, there isn't a simple and reliable way to detect the error and recover from it. The next MinimServer update will include code to detect and ignore this error if it applies to the last chunk in the file.
(11-08-2014 07:33)simoncn Wrote: [ -> ]This file violates the WAV specification because it contains an "id3" chunk (used for tag data) that contains an odd number of bytes and doesn't include a pad byte at the end of the chunk. According to the WAV specification, all chunks with an odd number of bytes must include a pad byte with value zero at the end of the chunk.
Interesting Simon. Could this sort of violation cause a audible noise at the end of a track with a certain combination of network bridge and DAC ? What is the best way to check for this "non-conformity" ?
(11-08-2014 11:11)NWTStuff Wrote: [ -> ]Interesting Simon. Could this sort of violation cause a audible noise at the end of a track with a certain combination of network bridge and DAC ? What is the best way to check for this "non-conformity" ?
This error shouldn't cause any audible problem because the error isn't in the audio chunk of the file. A length error in the audio chunk might cause an audible problem.
MinimServer does quite a lot of checking when it scans the library but it isn't guaranteed to catch every format error. It's possible that some audio converters or editors might do this checking.
(09-08-2014 17:50)Rwjr44 Wrote: [ -> ]I used JRiver for 95% of the ripped CDs and am slowly redoing the remain 5% which were done using Windows Media Player a good number are downloads (HDTracks, etc). The main problem is that these don't occur for an entire album sometimes only one track.
Thanks for uploading the sample file. This file has a "data" chunk and an "id3" chunk. The form size is 8 bytes smaller than the combined sizes of these two chunks.
You might be able to fix this by using dBpoweramp to do a WAV to WAV batch conversion of the faulty files.
(11-08-2014 21:28)simoncn Wrote: [ -> ] (09-08-2014 17:50)Rwjr44 Wrote: [ -> ]I used JRiver for 95% of the ripped CDs and am slowly redoing the remain 5% which were done using Windows Media Player a good number are downloads (HDTracks, etc). The main problem is that these don't occur for an entire album sometimes only one track.
Thanks for uploading the sample file. This file has a "data" chunk and an "id3" chunk. The form size is 8 bytes smaller than the combined sizes of these two chunks.
You might be able to fix this by using dBpoweramp to do a WAV to WAV batch conversion of the faulty files.
Thanks for the information. I am testing to see if the GoodSync may be the problem when moving from PC to Synology. I don't have time to spend on this (over 2000 PCM albums almost all of which have at least one problem file and all HiRes PCM downloads have this problem) so it is on the backburner. Synology's MediaServer works fine, so I'll use it.
Thanks for the effort and don't work too hard. :-)
rwjr44
(12-08-2014 13:48)Rwjr44 Wrote: [ -> ]Thanks for the information. I am testing to see if the GoodSync may be the problem when moving from PC to Synology. I don't have time to spend on this (over 2000 PCM albums almost all of which have at least one problem file and all HiRes PCM downloads have this problem) so it is on the backburner. Synology's MediaServer works fine, so I'll use it.
Thanks for the effort and don't work too hard. :-)
rwjr44
I would be very surprised if GoodSync is modifying the contents of a file. The problem is more likely to be caused by the source from which you obtained the files. Did the files contain ID3v2 tags when you downloaded them or have you added these yourself?
(12-08-2014 20:23)simoncn Wrote: [ -> ] (12-08-2014 13:48)Rwjr44 Wrote: [ -> ]Thanks for the information. I am testing to see if the GoodSync may be the problem when moving from PC to Synology. I don't have time to spend on this (over 2000 PCM albums almost all of which have at least one problem file and all HiRes PCM downloads have this problem) so it is on the backburner. Synology's MediaServer works fine, so I'll use it.
Thanks for the effort and don't work too hard. :-)
rwjr44
I would be very surprised if GoodSync is modifying the contents of a file. The problem is more likely to be caused by the source from which you obtained the files. Did the files contain ID3v2 tags when you downloaded them or have you added these yourself?
I ripped most using JRiver on my PC and I downloaded the HiRes PCM files from HDTracks. I ripped my SACDs and there were no errors from MinimServer issued for DSF files.
Thanks again.
(12-08-2014 21:23)Rwjr44 Wrote: [ -> ]I ripped most using JRiver on my PC and I downloaded the HiRes PCM files from HDTracks. I ripped my SACDs and there were no errors from MinimServer issued for DSF files.
Thanks again.
This isn't the first time I have come across a form size problem with files downloaded from HDTracks (see
this post). I will try contacting HDTracks to see if they have any interest in fixing this problem.
Could you upload to my FTP server a problem file that you ripped with JRiver so that I can see if this has the same format problem as the HDTracks downloads? Thanks very much for your help with this!