Bugzilla – Bug 4867
Cannot stream the following wav tracks with 24 bits and 12K sampling rate natively.
Last modified: 2008-04-07 16:11:09 UTC
System Info: Dell Optiplex GX620, Vista SP0 ENU Steps to Reproduce: 1. On a clean ghost of Vista SP0 ENU, install SlimServer 7.0a1 of build 2007-03-27. 2. Start SlimServer and play some wav tracks of various frequencies and sampling rates. 3. Notice both mono and stereo wav tracks with 24 bits and 12K samling rate do not stream: Track A: wav, 24 bits, 12K sampling rate, mono, 440 Hz, 10 seconds, and Track B: wav, 24 bits, 12K sampling rate, stereo, 440 Hz, 10 seconds
Created attachment 1876 [details] wav, 24 bits, 12K sampling rate, mono, 440 Hz, 10 seconds
Created attachment 1877 [details] wav, 24 bits, 12K sampling rate, stereo, 440 Hz, 10 seconds
Wallace, just like bug 4866 I am able to play these without issue.
I found a minor bug in slimserver that could cause this problem. Please retest with trunk r11717 or branch 6.5 r11718.
Tried these two tracks on XP with 6.5.2 - 11726. They are still not playing. The time and progress bar show up on the SqueezeBox. However, the progress bar does not progress at all.
These file formats are rare. Pushing this bug out.
Does this format still fail?
Works with SC7 - 16286.
On SC 7.0, this bug is not there. However, on the latest nightly of SlimServer 6.5, this bug is still there. This bug was written against SlimServer 6.5.x, not against 7.0. --TESTCASE-- Testing the length of sound in C:/TestThisBuild/SlimServer_6.5_v2008-01-15.exe_TestsLogsOnVista/From_wav_24_12000_1_440_10.wav. --FAIL-- The $nExpectedLengthMin, $nExpectedLengthMax and $nLengthOfSound are 9.87, 10.13, and 0 respectively. --TESTCASE-- Testing the length of sound in C:/TestThisBuild/SlimServer_6.5_v2008-01-15.exe_TestsLogsOnVista/From_wav_24_12000_2_440_10.wav. --FAIL-- The $nExpectedLengthMin, $nExpectedLengthMax and $nLengthOfSound are 9.87, 10.13, and 0 respectively. By the way, how important is SlimServer 6.5.X these days? If it is obsolete, then this bug can be closed based on results of 7.0. However, if this release is still available to users, then this bug should be kept open. Reopening for now.
See comment #9. With the official release of SC7, in which this bug is not present, I think it best to close this bug as works for me.