Bugzilla – Bug 16646
WAVE file tagging information is no longer read correctly
Last modified: 2011-01-21 07:33:58 UTC
Created attachment 7020 [details] Scanner Log file for the v7.5.0 software - showing that all is well Based on a library of approximately 21,000 songs (primarily in WAV format), tagged with WAV tags and ID3 tags all songs are correctly parsed by scanner.exe in Squeezebox Server v7.5.0 as can be seen in the attached scanner log "scanner (v7.5.0).log". However, upgrading to Squeezebox Server v7.5.1, the scanner is only able to recognise 90 albums (with error 33 reported "unable to read at least 10 bytes from file" for a number of files along the way) and then unexpectedly stops scanning. The results of this scan are attached as "scanner (v7.5.1).log" For reference, also tried v7.6.0 r31483 beta nightly build but this failed to scan any files, resulting in a library of 0 albums. As can be seen from the dates/times of the scans, the v7.5.1 scan was run right before the v7.5.0 scan, hence the music files/tags were not changed in between.
Created attachment 7021 [details] Scanner Log file for the v7.5.1 software - highlighting scanning errors
Robert, are you sure you never used guess tag formats? also, i have never seen a wav with id3 tags, just very limited wav tags.
Hi Mike, Thanks for the tip - but I'm definitely not using guess tags. And I'm not surprised that you haven't seen ID3 tags in WAV files with WAVE tags as I'm a software engineer and have written my own CD ripper and tagger combined that inserts these tags. It definitely does it correctly as I followed the Microsoft RIFF tagging specification (also verified by using Microsoft's RIFF walker) and was also instrumental in getting the full set supported in Squeezebox as you can see from bug entries 11789 and 11803. Also Windows 7 now includes support for WAVE tagging and all my music files appear correctly with tags decoded in Windows Explorer (how cool is that!). And of course, this has all worked perfectly upto and including Squeezebox Server v7.5.0 but something must have changed in v7.5.1 to break the scanner.