[MP3 ENCODER] bitrate_index question; prev. was Layer II VBR

1999-12-13 Thread Patrick De Smet
In another thread (new detail question below): On Fri, 10 Dec 1999, Gabriel Bouvigne wrote: > Layer II VBR is ISO compliant. However, players are not required to support > it (unlike layer III players). Sorry, I was wrong; the above is indeed true; the standard says; "In order to provide the sm

[MP3 ENCODER] Lame at low bitrates

1999-12-13 Thread Robert Hegemann
Here are some thoughts about Lame at constant low bitrates: * at low bitrates we have low samplerates (MPEG2) But the ATH formula we implemented is tuned for 44.1 khz sample frequency (due to the high frequencies, MUS420 Project). Maybe the ATH formula need

[MP3 ENCODER] Status of noise quantization

1999-12-13 Thread Stapp, Acy
Has this stabilized? Do I need to redo the assembly for it? -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

RE: [MP3 ENCODER] Status of noise quantization

1999-12-13 Thread Mathew Hendry
> From: Stapp, Acy [mailto:[EMAIL PROTECTED]] > > Has this stabilized? Hasn't changed for at least a few days. ;) > Do I need to redo the assembly for it? Don't think so. I removed the -0.5s from the asm quantize_xrpow, you might want to check that version for "optimality". -- Mat. -- MP3 ENC

RE: [MP3 ENCODER] filter options

1999-12-13 Thread Robert Hegemann
Ross wrote: > That's great! I've been waiting for these settings. Can someone please > compile a Win32 version. Maybe a new beta version should be released? > > Ross. Hi Ross, I have no Windows, so I can't help you with a Win32 version. But I want to start a collection, that could become som

[MP3 ENCODER] Status of noise quantization

1999-12-13 Thread Takehiro Tominaga
> "M" == Mathew Hendry <[EMAIL PROTECTED]> writes: >> From: Stapp, Acy [mailto:[EMAIL PROTECTED]] >> >> Has this stabilized? M> Hasn't changed for at least a few days. ;) Wait a moment ! I don't think so > "S" == Segher Boessenkool <[EMAIL PROTECTED]> writes:

Re: [MP3 ENCODER] Status of noise quantization

1999-12-13 Thread Mark Taylor
I dont think we should make this change. Preserving the amplitude (and thus the actual shape of the wave form) seems more important than the energy. Also, using fabs(i^8/3 -x^2) is an unusual definition of noise that I have never seen in any of the technical papers. Mark > > >> hmm, I

Re: [MP3 ENCODER] filter options

1999-12-13 Thread Mark Taylor
> X-Authentication-Warning: cs.csoft.net: $s=geek.rcc.se doesn't match >$[EMAIL PROTECTED] > X-Authentication-Warning: geek.rcc.se: majordom set sender to >[EMAIL PROTECTED] using -f > From: Robert Hegemann <[EMAIL PROTECTED]> > Date: Sun, 12 Dec 1999 23:21:56 +0100 > Content-Type: text/plain >

[MP3 ENCODER] Using libm or not

1999-12-13 Thread Piter B.
Hey ! Should we use libm library in linking ( -lm) or not ? There is no difference in CBR in quality (only speed). In VBR there is difference in byte by byte comparing, and libm is about 13% slower. Regards Piotr Borowski -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Re: [MP3 ENCODER] Status of noise quantization

1999-12-13 Thread Greg Maxwell
On Mon, 13 Dec 1999, Mark Taylor wrote: > I dont think we should make this change. Preserving the amplitude > (and thus the actual shape of the wave form) seems more important than > the energy. Also, using fabs(i^8/3 -x^2) is an unusual definition of > noise that I have never seen in any of th

Re: [MP3 ENCODER] LAME M/S thresholds

1999-12-13 Thread Mark Taylor
> >That's right. therefore in FAAC you will see this: > >if ((nb[0][b] <= 1.58*nb[1][b])||(nb[1][b] <= 1.58*nb[0][b])) > >and in LAME: > >if ((ratio[0][b] >= 1.58*ratio[1][b])||(ratio[1][b] >= 1.58*ratio[0][b])) > > > >Or the other way around, I don't have access to my source code where I am > n

Re: [MP3 ENCODER] Using libm or not

1999-12-13 Thread Monty
> Should we use libm library in linking ( -lm) or not ? On Linux with glibc and gcc>2.7, all the calls you'd be making to libm actually become ASM macros. Linking with libm is still required. Monty -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

[MP3 ENCODER] lame 3.58beta

1999-12-13 Thread Mark Taylor
lame3.58beta is on the web site. This is also tag 'lame3_58beta' in the CVS repository, since CVS does not allow a '.' to be in the tag name. It is just a tag, not a branch. My (limited) understanding of CVS makes me think the beta releases do not warrent being a branch, but the 'official'

RE: [MP3 ENCODER] filter options

1999-12-13 Thread Ross Levis
Hi Robert. Hopefully someone else can help with the Win32 compile - please :) I think Marks suggestion of using a width option may be less confusing and easier to use. As far as radio is concerned, the 2 main presets would be something like this: 1. Music/commercials: FM50 - 15000 hz

[MP3 ENCODER] profiling

1999-12-13 Thread michael cheng
Hi all, I'm sure I've asked this before, but i've got a terrible memory (and I'm having troubles getting my mail folders out of my backups): How do I make absolutely sure that a function appears in the gprof profile. It isn't declared implicitly inline, but the optimizer (-O9) in

Re: [MP3 ENCODER] profiling

1999-12-13 Thread Monty
> How do I make absolutely sure that a function appears in the gprof profile. > It isn't declared implicitly inline, > but the optimizer (-O9) inlines lots of things. Is there a keyword to prevent > it? -fno-inline. It's all in the info file (and unlike most stuff in info, this is easy to

Re: Re: [MP3 ENCODER] profiling

1999-12-13 Thread michael cheng
> -fno-inline. It's all in the info file (and unlike most stuff in info, this is > easy to find :-). But I want *everything else* inlined (if possible), except this one function. later mike -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Re: [MP3 ENCODER] filter options

1999-12-13 Thread Robert Hegemann
Mark wrote: > I would suggest changing to a more sox like settings, where you specify > the lowpass frequency, and then a width or rolloff parameter. > lowpass_l and lowpass_h seems a little confusing. What about: > > --lowpass > --lowpass_width > > And then there could be a default width of

Re: Re: [MP3 ENCODER] profiling

1999-12-13 Thread Mathew Hendry
> From: "michael cheng" <[EMAIL PROTECTED]> > > > -fno-inline. It's all in the info file (and unlike most stuff in info, this > is > > easy to find :-). > But I want *everything else* inlined (if possible), except this one function. I don't know of any neat way around this (there's no "noinline"

RE: [MP3 ENCODER] filter options

1999-12-13 Thread Ross Levis
Robert, Presets: Is the -b setting removed when -v is selected? Should! If you are interested, I've just analysed some voice-only files here and found most energy is between 100hz and 12000hz. Cheers, Ross. Robert Hegemann wrote: > Thank you Ross for the info about radio frequencies. > Coding

RE: [MP3 ENCODER] filter options

1999-12-13 Thread DeRobertis
At 5:28 PM +0100 on 12/13/99, Robert Hegemann wrote: > CD 2 - 2 hz, stereo: > --lowpass_h 2 > --resample 44.1 > -m s -b 192 I thaught a CD could have up to 22KHz? -- MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )