Incorrect Track Lengths

Answered

Stephen Agar

• February 15, 2022 16:09

I have an unusual problem.

My library is all WAV files - but I have ID3v2.3 tags on all the files.

Everything works fine - save that BluOS attributes random incorrect track lengths to every track  (usually very short e.g. 0.07 seconds instead of 3.24) - even though the information in the tag is correct. Every other application I use reads the track length correctly.

Any ideas?

 

0

• Official comment

  

  Tony W.

  Product Support Manager

  • February 15, 2022 16:30

  The lack of elapsed time being shown is because your local WAV files are not encoded correctly. WAV is not a proper hi-fi format and a de jure standard (meaning no official standard). BluOS actually uses three different standards to try and review and decode WAV files as a result. Why many have abandoned it for proper FLAC encoding.
• 

  Stephen Agar

  • February 15, 2022 17:19

  Well, with over 65,000 files encoded from my Naim hi-fi, I wouldn't relish ripping them all again. Maybe I should try batch file conversion?

  Strange that every other App I use reports the times correctly - and they are embedded in the ID3v2.3 tag as well - I would have thought BluOS would just read the tag rather than trying to look at the WAV file and guess?

  0

Please sign in to leave a comment.