Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-04 Thread Frank Klemm
:: :: ISO spec says the maximum should be 8191. But as part of huffman :: decoding, you sometimes add 15 to the result, yielding values as large :: as 8206. Right now, LAME (and the ISO dist10 code) will make use of :: the full range: values up to 8206. :: :: The question is, should

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-03 Thread Youri Pepplinkhuizen
Great! Just one thing - does the fact big_values is limited to 8192 now mean a loss of quality? Imposing a maximum value of 8191 is a completely unneeded restriction which results in a (very tiny) loss of quality. I don't get this, since apparantly, it is a needed restriction. Or is it

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-03 Thread Mark Taylor
X-Authentication-Warning: geek.rcc.se: majordom set sender to [EMAIL PROTECTED] using -f From: "Youri Pepplinkhuizen" [EMAIL PROTECTED] Date: Tue, 3 Oct 2000 09:22:08 +0200 Content-Type: multipart/alternative; boundary="=_NextPart_000_0022_01C02D1B.673EA6E0" X-Priority: 3

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-03 Thread Youri Pepplinkhuizen
Hmmm, nah I don't think it should. If even the ISO source uses 8206, why change it when the Nitrane bug has already been fixed by Nullsoft? Also, how come only Nitrane is triggered by this setting? All other decoders work fine. It would seem like it, that using a value of 8191 is more of a

RE: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-03 Thread alex . broadhead
Howdy, ISO spec says the maximum should be 8191. But as part of huffman decoding, you sometimes add 15 to the result, yielding values as large as 8206. Right now, LAME (and the ISO dist10 code) will make use of the full range: values up to 8206. The question is, should LAME be modified

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-02 Thread Naoki Shibata
Naoki IIRC, bug of winamp is also triggered by FhG encoded mp3 file. This means that nitrane has more than one bug. So, changing IXMAX_VAL to 8191 doesn't solve all problems. I think we should investigate what FhG encoder does, and make lame do what FhG does. -- Naoki Shibata e-mail:

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-02 Thread Mark Taylor
X-Authentication-Warning: geek.rcc.se: majordom set sender to [EMAIL PROTECTED] using -f Date: Mon, 02 Oct 2000 18:32:58 +0900 From: Naoki Shibata [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII Sender: [EMAIL PROTECTED] Precedence: bulk Reply-To: [EMAIL PROTECTED] Mark

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-02 Thread Gabriel Bouvigne
Should we change IXMAX_VAL to 8191? pros: 1. as Rob points out, less false syncwords in the bitstream. (8206 is encoded as 0x1FFF). 2. LAME produced mp3's will no longer trigger Winamp bug. cons: 1. Winamp may not bother to fix their decoder 2. Tiny loss in quality just to pander to

Re: [MP3 ENCODER] Winamp/100hz bug: SOLVED!

2000-10-02 Thread Mark Taylor
For decoder enthusiasts: 100hz bug fixed versions of Nitrane and their upcoming Nitrane replacement are available at: http://www.sulaco.org/mp3/winamp/winamp.html Nullsoft sent me these .zip files, but I haven't tested them yet. They are probably also available somewhere on www.winamp.com.