Bugzilla – Bug 15251
WAV files not listing in track order, but in alphabetical order since updating to SBS 7.4.1
Last modified: 2010-03-01 17:15:06 UTC
A customer reported this issue and I verified it. I have a few sample files from the customer. The Cyndi Lauper tracks are listed in track order regardless of the server version, SC 7.3.3 or SBS 7.4.1. The tracks from R.E.M only list in track order on SC 7.3.3.
I cannot upload the files because they exceed 20 MB, so please ping me if anyone would like me to send the test files to them.
check filenames and check tags (if any). The server is unlikely to discriminate order based on what artist is involved.
(In reply to comment #2) The CDs were ripped with MicroSoft MediaPlayer in .wav format nearly two years ago then the track data added with dbpoweramp when I discovered MediaPlayer dumped the track IDs. Until version 7.4.1 I did not have a problem. The albums played in track order. After loading 7.4.1 I noticed that many of the albums are now playing in alphabetical order. I redid the track data tags on several albums using both dbpoweramp and MediaMonkey, then rescanned my library. The albums still played in alphabetical order. Since downloading dbpoweramp, that has been my primary program to rip CDs since it maintains track data IDs. Many of the albums ripped with dbpoweramp no longer play in track order, but play alphabetically. All albums show up in MediaMonkey in track order.
I have also experienced this bug. It only occurs with WAV files that have tags. Squeezebox Server correctly reads genre, album, artist and title but does not read the track number tag so every track in an album is given a track number of zero in the Squeeze database. This has to be something very simple amiss in the reading of the tags.
WAV file tagging is nothing standardized. It's unreliable at best and should be avoided if possible.
Please send me the files or copy the output of View Tags in 7.5.
Ping, can I have a sample file?
Please reopen with a sample file if you still want me to look at this bug.