this fixed and will fully support any
free format bitrate produced by LAME... with the exception of MPEG 2.5
streams.
On that subject, where can I get "official" documentation for the so-called
MPEG 2.5 format?
Cheers,
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing l
.
Cheers,
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
in increments of 1.5 dB.
There is apparently no quality loss associated with this change as long as the
signal is not amplified so much as to cause clipping.
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
:: I think for Layer I it's 384.
::
MPEG-1 Layer I is 384 samples. MPEG-1 Layer II and III is 1152 samples.
Values are halved for LSF.
The number of samples is only halved for Layer III LSF (576). Layer I and
Layer II are always 384 and 1152 samples, respectively.
--
Rob Leslie
[EMAIL
to an URL?
This would ease some explainations.
I wouldn't send them directly to this list, but I don't mind if you send them
to me personally. Or you can use a URL.
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
output to a file (e.g. WAV).
RL Are there any decoders I missed that could be added?
please check
http://privatewww.essex.ac.uk/~djmrob/mp3decoders/intro.html
Thanks, I'll check David's list more thoroughly and see if there are more I
can add.
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER
/compliance.php3
I'd also appreciate feedback. Are the results easy to understand? Is there any
information that could be added to supplement the results? Are there any other
relevant links to related information?
Are there any decoders I missed that could be added?
Many thanks.
--
Rob Leslie
[EMAIL
it's not built by default, the program is in `madtime.c'; just do:
./configure
make madtime
An obvious improvement would be to implement directory traversals. Currently
all files must be listed on the command line.
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http
and
variable bitrate streams equally well. (While this makes it very accurate, it
also makes it slower than a quick calculation based on file size.)
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
://www.mars.org/home/rob/proj/mpeg/
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
David writes:
What are the differences between 1.0 and 1.1 ?
Basically, v1.1 introduced a track field.
This page sums it up pretty well:
http://www.id3.org/id3v1.html
--
Rob Leslie
[EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
bsolute value should be constrained by linbits alone, and not 2^linbits + 15.
At least one argument I can think of in favor of the limit, other than the
assertion in the standard, is to help prevent creating false sync words. It
can also serve as minimal error detection.
More thoughts?
-
value in this range is constrained to 8191."
A decoder implementation relying on this statement therefore might not be
prepared to handle a quantized absolute value greater than 8191.
Should LAME be changed to accommodate? Or is the statement in the standard
misleading?
--
Rob Leslie
[EMAIL
13 matches
Mail list logo