Bugzilla – Bug 10239
Squeezebox 3 don't play MP3 48Khz
Last modified: 2012-02-27 17:33:07 UTC
Created attachment 4388 [details] Example of MP3 48Khz that SB3 cannot play Hello, When I try to play an MP3 file sampled at 48Khz, SB3 displays "Rebuffering" and don't start to play the file (I attached an MP3 48Khz file). I tried with 48Khz FLAC and in that case, all is OK. Please, can you fix this? Thank you!!! SqueezeCenter Version: 7.2.1 - 23630 @ Mon Oct 20 19:20:42 PDT 2008 - Netgear RAIDiator - EN - utf8 Perl Version: 5.8.8 sparc-linux MySQL Version: 5.0.24a-Debian_3.infrant1 Platform Architecture: sparc-linux Player firmware version: 113
Steven, can you reproduce?
I have not been able to reproduce with 7.2, 7.2.1 and the nightly of 7.3 on a ReadyNAS Duo. I did notice some performance issues playing the attached file under 7.2 and 7.2.1 but not 7.3. The performance issues I experienced with 7.2 and 7.2.1 was some rebuffering of the stream most likely attributed to the fact that the file has a bitrate of 320kbps not the fact that it is 48kHz. didbox, I suggest you try a nightly of 7.3. 7.3 has completely reworked streaming and other enhancements that improve the performance of SqueezeCenter on the ReadyNAS product. If you prefer not to install the nightly 7.3 should be released very soon.
OK, I'll try version 7.3. Please, can you help me, I don't know which build to install on my Ready NAS NV+: - SqueezeCenter-readynas_7.3~24265-sparc.bin OR - SqeezeCenter_7.3~24259-i386.bin OR - SqueezeCenter_7.3~24259-sparc.bin Thank you!
The names are being changed in preparation for the pending release of 7.3. The one I used for testing is SqueezeCenter_7.3~24259-sparc.bin but you might want to wait for the official release of 7.3 since it is so close.
Hello Steven, I installed SqueezeCenter 7.3 (nightly build SqueezeCenter_7.3~24270-sparc-readynas.bin) on my ReadyNAS NV+ (1Go of RAM) and the problem is the same: cannot play MP3 320Kbps 48Khz. So my new config is: Version: 7.3 - 24270 @ Wed Dec 10 03:11:41 PST 2008 Hostname: ReadyNAS01 Server IP Address: 192.168.1.88 Server HTTP Port Number: 9000 Operating system: Netgear RAIDiator - EN - utf8 Platform Architecture: sparc-linux Perl Version: 5.8.8 - sparc-linux MySQL Version: 5.0.24a-Debian_3.infrant1 Total Players Recognized: 1 Player Model: squeezebox3 Firmware: 120 Player IP Address: 192.168.1.82 Player MAC Address: 00:04:20:12:2e:2a
This is really odd. So when you attempt to play the 48kHz 320Mbps mp3 your player immediately displays rebuffering? The only thing I can think of trying at the moment would be to run the ReadyNAS CleanSqueezeCenter_DB add-on and walk through SqueezeCenter setup again. You can find the add-on at http://www.readynas.com/?page_id=93 I'm curious, what version of RAIDiator are you running? I don't think it should make a difference however.
Sorry, that should have been 320kbps not 320Mbps.
Hello Steven, Some information that could be useful for you: - When I try to play the attached MP3 320 Kbps 48Khz file, the behaviour is somewhat different with SC7.3: - at the level of SB3, when I press Play on the remote, nothing happens (no more display of message "Rebuffering...); - at the level of SqueezeCenter, when I clik the Play button, the file start to play for 2 to 3 seconds and then restart from the beginning; - The version of Radiator is 4.1.4 - My SB3 is connected to the ReadyNAS NV+ with cable (no use of Wifi). But I don't think that is a network performance issue because there is no problem to play a FLAC 48Khz. As requested, I'll run "CleanSqueezeCenter_DB" add-on and keep you informed. Thank you for your assistance! Didier
Hello Steven, I tell you the story: - After a run of CleanSqueezeCenter_DB, the problem remains... - So, I decided to unistall and reinstall SqueezeCenter. - After the reinstallation, impossible to start web interface of SqueezeCenter via port 9000. So, I did another run of CleanSqueezeCenter_DB. And now, all is OK even playing MP3 320Kbps 48Khz !!! Thank you for your help! Didier
Thank you so much for the report and I am glad that you were able to get it working.
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.