Bugzilla – Bug 10731
WAV convert to LAME (MP3) fails
Last modified: 2009-10-05 14:27:09 UTC
when WAV is forced to transcode to LAME > MP3 noise is heard as out put. Happens on all players Lame 3.96.1 installed on XP / Vista
This fixes it. Please make sure to test on a PPC Mac as well. And test with multiple versions of LAME. Also test AIFF -> MP3 which has a similar convert line. --- convert.conf (revision 48800) +++ convert.conf (local) @@ -87,7 +87,7 @@ wav mp3 * * # IFB:{BITRATE=-B %B}D:{RESAMPLE=--resample %D} - [lame] --silent -q $QUALITY$ $RESAMPLE$ -v $BITRATE$ $FILE$ - + [lame] --silent -q $QUALITY$ $RESAMPLE$ -v $BITRATE$ $-x$ $FILE$ - aif mp3 * * # IFB:{BITRATE=-B %B}D:{RESAMPLE=--resample %D}
Change 24695.
Windows Vista 3.96.1 WAV playback is fine (with patch) 3.98.2 WAV fails to play (with - w/o patch)
Created attachment 4664 [details] 396
Created attachment 4665 [details] 398
(In reply to comment #3) > Windows Vista > 3.96.1 WAV playback is fine (with patch) Just wanted to note that this was with 16/44.1. I suspect the patch will not work with other rates. Alan, do we not send the wav header to lame when transcoding?
This is all part of the problem addressed by bug 10026. For 7.3.2 we could resolve this removing the 'I' from the capabilities line and probably also the $-x$ from the transcoder (again). We would need to remember to put back the 'I' when the fix for 10026 is applied.
I don't see why this is a major bug, or even why it would be open for 7.3.2. Move it back if you disagree...
Fixed with the changes in bug 10026 and change 25457.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.