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
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'm
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
Sender:
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/ )
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 the
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
now.
Also I
Should we use libm library in linking ( -lm) or not ?
On Linux with glibc and gcc2.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/ )
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
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)
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
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 about
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" keyword
12 matches
Mail list logo
