C can't cast from type A to type B. There is only the possibility to
cast every shit to type B. And this is dangerous.
So you write a
int ifreq;
double dfreq;
ifreq = (int) ( dfreq );
and now dfreq changes the type to 'struct bla*'.
C converts this without batting an
On Mon, 4 Sep 2000, Frank Klemm wrote:
:: :: I run gcc 2.95.(3) and SAS/C (the latter is usually much more helpful on
:: :: warnings, and still much more forgiving on "errors")...
:: Can you add g++ for testing?
:: Or also some other C++ compiler?
G++ 2.95.2 has the
-md is not documented.
What is it ? Does anyone made a dual channel mode?
Regards,
--
Gabriel Bouvigne - France
[EMAIL PROTECTED]
icq: 12138873
MP3' Tech: www.mp3-tech.org
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
perhaps it is time for someone who fully
understands all the options/switches to settle down and write a
comprehensive 'Help' file for Lame, - I doubt many who use Lame with a
front-end or ripping utility bother to read the 'Usage' file that
accompanies the exe file and I don't think users
I've improved the correlation calculator a little bit, so not only the
correlation of the pure signal is calculated, but also the correlation of
the (in time) differentiated signal.
Normally the correlation of differentiated signal is a little bit lower
than
the of the original signal. But
:: Hi Everyone,
::
:: I haven't been keeping up with things for the last week, because
:: my wife and I just had our first baby :-) (baby's requisite website:
:: www.wildpuppy.com/baby)
::
:: Anyway, now LAME CVS fails all my test cases. This is normal since
:: small changes in just
Not a biggie, but the --help and --longhelp displays the line:
RECOMMENDED : lame -h input.mp3 output.wav
shouldn't that be:
RECOMMENDED : lame -h input.wav output.mp3
Chris Wise
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Hello,
If I've well undertood what the VBR quality setting means (-V x), it is the allowed
number of bands where distortion (in the psycho-model sense) occurs .
I'd like now to take the problem from the other side: in CBR, is there a way to have
statistics about the number of distorded bands
Frank Klemm wrote:
::
:: programmers don't document, you know ;-)
:: OK, your point is clear and I'll try to add more comments
:: (hopefully useful remarks..)
::
:: * Don't use single 'short' variables to save storage.
:: Short variables are especially on Pentium Class Computer
Pierre Hugonnet schrieb am Mon, 04 Sep 2000:
Hello,
If I've well undertood what the VBR quality setting means (-V x), it is the allowed
number of bands where distortion (in the psycho-model sense) occurs .
hmm, this was the meaning of -V in the very first beginning
of LAME's VBR code.
We are expecting our second in November. From my experience, I suspect we will
be hearing less from you in the next few months. You will most likely be
sleeping in your spare time!
Cheers,
Ross.
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
From: Frank Klemm [mailto:[EMAIL PROTECTED]]
Good C Code should be compilable with (nearly) all C(89/95/99)
Agreed. (Although there is some perfectly good C89/95 code that is broken by
changes in C99 - see endless arguments in news:comp.std.c)
and C++ compilers.
Good C code compilable as
Robert Hegemann wrote:
hmm, this was the meaning of -V in the very first beginning
of LAME's VBR code.
Actually you influence the absolute threshold of hearing aka ATH
and the masking thresholds computed by GPSYCHO. VBR tries to
avoid distorted bands, but sometimes, when there are not
What do you think sounds uglier:
20 distorted bands, each 0.1 dB
or
1 distorted band by 2 dB
???
I would say that 20 distorted bands at 0.1dB is preferable, and assume that this is
the choice of lame's algorithms. Is this assumption wrong ?
Depends. If it is maximum
David Balazic ([EMAIL PROTECTED]) wrote:
IIRC the "int" type is the fastest on all ( most ) compilers.
I.E. :
On 16 bit systems is int16
On 32 bit systems it is int32
On 64 bit systems ( alpha ) it is int64 ( unless tweaked to 32 bit for
bugward compatibility )
Actually, "int" is 32 bits
Pierre Hugonnet schrieb am Mon, 04 Sep 2000:
Robert Hegemann wrote:
hmm, this was the meaning of -V in the very first beginning
of LAME's VBR code.
Actually you influence the absolute threshold of hearing aka ATH
and the masking thresholds computed by GPSYCHO. VBR tries to
avoid
would it be possible to encode an mp3 at ABR 320 using frames larger
than 320 kbps?
e.g. 440kbps , 560kbps
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
I want to implement a normalizing routine in one of
my programs, can anybody recommend one? It would be for 16 bit CD
audio.
Would simply multiplying by a constant factor and
rounding be good enough or would the rounding errors cause some
problems
sorry for the offtopic
Francois
MoiN
On Tue, Sep 05, 2000 at 01:03:14AM +0100, Estrunfus Maleficus wrote:
would it be possible to encode an mp3 at ABR 320 using frames larger
than 320 kbps?
e.g. 440kbps , 560kbps
There are no audio frames larger than 320kbps in MPEG standard.
The only way to create larger frames is to use
On www.r3mix.net, the following command line is recommended as the best
option (size, speed, quality-wise):
-V1 -h -mj -b128 -q1
I was looking over the documentation that came with the zip file of LAME
3.86b, and I couldn't find any mention of the "- q" command.
Can someone here explain? Does
20 matches
Mail list logo
