Bugzilla – Bug 2469
if trying to play unsupported files (WMA, OGG, etc), gracefully fall back to legacy wma decoding method
Last modified: 2009-09-08 09:31:50 UTC
for backstory, see bug #2368 and bug #2127
Sending to Richard. Please retarget if you don't think it's possible for 6.5 Thanks
Recent firmwares already return STMn (decoder not supported) for WMA and OGG files that the firmware cannot support. The slimserver and squeezenetwork need updating to support this status code. Who should own this?
Richard to add file using an unsupported codec and reassign to dan.
Dan, I cannot find any test cases for this at the moment but the following files will return the error: - ogg files with more than 2 channels - wma voice files that use speech and music superframes (I have not yet found an wma encoder that creates this type of stream) - wma lossless or other unknown wma file types I know I did originally test this by allowing slimserver to send wma lossless files to the firmware. I don't know if it is worth implementing support for this in slimserver 6.5, but logging failed streams in squeezenetwork would be useful to see if any of the mixed wma voice streams are in the wild. It might be worth checking with Kevin if support get any questions about failed WMA streams anymore? If new types of files are found that the firmware can not support I will update this bug report with the file types, and we can review the situation.
Squeezebox2/3 fw 60 / Transport fw 9 will in addition return STMn for ogg tracks with very large codebooks. See bug #3969 for an example track.
Andy's change 9488 now has STMn reporting an error.
See also Bug 4497
This bug is being closed since it was resolved for a version which is now released! Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html If you are still seeing this bug, please re-open it and we will consider it for a future release.
Dean, why was this bug closed? As far as I can tell this was not completely implemented.
This was a bug reported back in version 5.1.1, if it's still an issue, please open a new bug with specific details for the current software.