Bugzilla – Bug 3332
Audio plays back at 44.1 KHz with 48Khz FLAC's when decompressing at server
Last modified: 2009-09-08 09:31:58 UTC
When SlimServer is set to convert FLAC's on the server side, sending uncompressed WAV data to the SqueezeBox, 48KHz FLAC's will play back at 44.1KHz
This is reproducible on my test system here, and so it should be fixed. However, in the interest of customer service, I should point out that if you're using a squeezebox2 or 3, there's no reason to uncompress flac to wav for streaming, since those units have built-in flac decode capability. :)
Anton, is this with a Squeezebox1 or 2/3?
This seems to happen with aac files on linux doing the faad/lame route. I've tried the setup with the switches for raw pcm and for wav. 44.1 m4a files work just fine for me. This happens for me with a slimp3 as well as a http stream. The slimp3 I have set for 320kbps and the http stream for 128kbps. The playback is 'slow' sounding. I can understand why, as the lame process would have no real way of identifying the source stream as 48 khz for the transcode. Would a wrapper script help? My current method from convert.conf is: mov mp3 * * [faad] -w -f 2 $FILE$ | [lame] -x --resample 44100 --silent -q $QUALITY$ -b $BITRATE$ -r - - I put up a forum message at http://forums.slimdevices.com/showthread.php?t=25007 about this. I verified this with 6.2.1 and 6.3.0.
Alan if you have a slimdevices address or another address you'd prefer me to use, just let me know.
Anton, please could you attach one of the sample troublesome files to this bug report. I have been unable to reproduce it with the files I have.
Now running with a few days old nightly from SC7, seems to be oke now. So I guess this can be closed. can anyone else confirm this please?
Is this still looking good? If so, I'll close this bug.
Assuming that this is fixed, in the absence of further feedback to the contrary.
This bug appears to have been fixed in the latest release! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look. Make sure to include the version number of the software you are seeing the error with.