Mark Powell schrieb am Mit, 04 Okt 2000:
On Wed, 4 Oct 2000, Naoki Shibata wrote:
I found a bug in the long block pre-echo control code.
This code should be fixed like this.
if (gfc-blocktype_old[gfp-mode == MPG_MD_JOINT_STEREO ? 0 : chn] == SHORT_TYPE )
Naoki,
Did this
Sigbjørn Skjæret schrieb am Mit, 04 Okt 2000:
Just thought I'd say my thoughts on the different parameter setting function
proposals we've had so far...
Individual functions for each parameter:
Pros:
- None. ;)
:-) compiler provides type check
:-) direct check for
Mark Powell schrieb am Mon, 02 Okt 2000:
On Fri, 29 Sep 2000, Robert Hegemann wrote:
does someone know any sample where a VBR encoded MP3 with -q1
gives a better sounding MP3 compared to a same sized VBR with -q2 ?
From your recent postings I'm detecting that you think -q1 can only
Mark Taylor schrieb am Son, 01 Okt 2000:
I think the mp3 encoding library should do what it is
supposed to do, encode pcm samples into mp3 frames.
BTW, Robert and everyone, how should we treat with mpglib and lame_mp3_XX
routines in frontend/get_audio.c and amiga_mpega.c ?
I
Naoki Shibata schrieb am Sam, 30 Sep 2000:
Youri Would it be possible to use some other switch, like --cwlimit, to achieve
Youri good quality with --nspsytune on all tonalities? If so, what settings would
Youri have to be used for it? (i.e. how should I interpret --cwlimit?)
It is a
Mark Taylor schrieb am Sam, 30 Sep 2000:
OK, I think and plan to do so, too. My plan is to add 2 functions to the API,
named "lame_init_vbrtag" and "lame_finish_vbrtag".
1 int lame_init_vbrtag(int guessed_framenumber)
- for the initialization(malloc buffers and make gfp-vbrtag =
Mark Powell schrieb am Sam, 30 Sep 2000:
On Sat, 30 Sep 2000, Robert Hegemann wrote:
One complication: a vbr tag and id3v2 tag! If there is also a id3v2
tag, it will be written into the bitstream first, so
lame_finish_vbrtag() will have to return a file offset
where the vbr tag
Ross Levis schrieb am Fre, 29 Sep 2000:
I think Roberts code should be included and implemented with a switch so
us "non-compilers" can test it.
look at Dmitry's site, there it is for Windows users.
http://www.chat.ru/~dkutsanov/~index.htm
The latest alpha
Joshua Bahnsen schrieb am Fre, 29 Sep 2000:
There is only a problem with the Intel compiler if you compile on Win 95/98. If you
actually use Win NT/2000 as your OS, binaries compiled with the Intel compiler run
just fine on NT/2000 and ME/95/98. If you want an example, I've posted binaries
Yog Sothoth schrieb am Fre, 29 Sep 2000:
hi -- This is my first post to the list. I've been
helping myself to the cvs source code for a few months now and this is a
subject I have done some experimentation with.
the only drawback I've found when using --nspsytune in vbr mode is that
Hi all,
does someone know any sample where a VBR encoded MP3 with -q1
gives a better sounding MP3 compared to a same sized VBR with -q2 ?
Ciao Robert
PS: for VBR -q2 equals -h and is the default if you leave out -qx, -h or -f
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Mark Powell schrieb am Don, 28 Sep 2000:
On Wed, 27 Sep 2000, Robert Hegemann wrote:
At least your 3.87 MMX version seems to be compiled with the
Makefile.MSVC I checked in, with RH_AMP and RH_VALIDATE_MS
enabled. Dmitry, is that right?
BTW Robert, are you recommending
Mark Powell schrieb am Don, 28 Sep 2000:
On Wed, 27 Sep 2000, Robert Hegemann wrote:
On my Linux Box with a Pentium 166 MMX the MMX and non-MMX
version produce bit identical results.
How did you get the Linux version to assemble the MMX code? I've had no
luck with GNU
Gabriel Bouvigne schrieb am Don, 28 Sep 2000:
At least your 3.87 MMX version seems to be compiled with the
Makefile.MSVC I checked in, with RH_AMP and RH_VALIDATE_MS
enabled. Dmitry, is that right?
Should they be considered as default switches? In this case, why aren't they
defined in
Gabriel Bouvigne schrieb am Don, 28 Sep 2000:
If the mmx version of choose table is used for the compilation, what will
happen on a non-mmx cpu?
it will crash, and it does so on my old P100.
Ciao Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Mathew Hendry schrieb am Don, 28 Sep 2000:
From: Mathew Hendry
varargs.h is pre-ANSI and non-standard - use stdarg.h for
the standard stuff. Should be
va_start(ap)
Oops! I mean
va_start(ap, lastarg)
where ap is your va_list and lastarg is the last non-variadic
Mark Powell schrieb am Don, 28 Sep 2000:
Wow the speed up is real sweet. What are the other .nas files in the
i386 directory for? Specifically the fftsse.nas. Seems interesting if SSE
can speed up some aspect of the encode. From the timestamps on these files
it seems they are an abandoned
Mark Powell schrieb am Don, 28 Sep 2000:
Hmm, you may dig in the Gogo sources. If I remember right
they allowed to turn on optimizations with something like
--use-mmx. This could be a way to do it in LAME too.
Surely Gabriel was referring to the MMX code always being present
Dmitry schrieb am Don, 28 Sep 2000:
Hello Gabriel,
Thursday, September 28, 2000, 12:08:23 PM, you wrote:
On my Linux Box with a Pentium 166 MMX the MMX and non-MMX
version produce bit identical results.
GB I compiled both releases (with and without mmx) with VC6, and the mp3 output
Mark Powell schrieb am Don, 28 Sep 2000:
Intel provide some code to do this at:
ftp://download.intel.nl/support/processors/procid/cpuinfo.zip
There's then the additional detection of Cyrix, AMD etc. which may cause
complications. AMD have a similar 32 bit features value which also
Mark Powell schrieb am Don, 28 Sep 2000:
I'm guessing that it's this that makes you happy with the velvet sound?
RH_AMP stuff is what was previously known as RH_NOISE_CALC
RH_VALIDATE_MS avoids to switch from LR to MS when
the perceptual entropy indicates a need for
Mark Powell schrieb am Don, 28 Sep 2000:
He also thinks -q1 could be unsafe. Is that unsafe just in v3.87 or has it
always been so, Robert?
Well, if we considered it always safe, we had made it default.
Combined with some -V0 or -V1 it seems to be OK.
If you compare
Dmitry schrieb am Don, 28 Sep 2000:
but what version i have to upload???
from project file or from makefile???
with 'Robert's alternate code' enable or disable???
Well, officially the one with 'Robert's alternate code'
commented out. Sorry for the confusion.
Ciao
Mark Taylor schrieb am Don, 28 Sep 2000:
I hope to add something soon which has it precompute the exact amount
needed. Does anyone have code which computes the lcd (largest
common denominator) of two ints? I think the number of windows needed
is given by:
Mark Taylor schrieb am Die, 26 Sep 2000:
I think we have to keep the old interface, since several applications
use it. So lame_global_flags will still have to be instantiated by the
calling program and exposed to the calling program. I dont think this
is incompatiable with a shared library?
Frank Klemm schrieb am Mit, 27 Sep 2000:
To avoid endless debates about the interface without clearifying the basic
concept I do introduce all possible methods I know (for C) with explaining
all pro and cons I know. I hope this is the best I can do.
Mark Taylor schrieb am Die, 26 Sep 2000:
Hi all,
I now have free format working in my decoder, MAD. If anyone would like to try
it -- get version 0.11.4b or later:
ftp://ftp.mars.org/pub/mpeg/
Thanks Rob, great!
So far it seems to work with any free format bitrate
Mark Powell schrieb am Die, 26 Sep 2000:
On Tue, 26 Sep 2000, Ross Levis wrote:
Mark Powell wrote:
FYI My PIII 583MHz (not Coppermine) provides ~1.5x normal speed.
On Win98 the new VBR encodes at ~1.1x on my AMD K62-428. CBR is a bit faster.
K62 is known for slow FPU so I would
Sigbjørn Skjæret schrieb am Die, 26 Sep 2000:
Why do we need float at this point ??
Because several of the parsed arguments are floats?
ie. frequencies could be passed in Hertz as ints,
was just something to think about now while we
change the API anyway
Should
Hi Alex!
1) M/S stereo require both channels to switch block types simultaneously -
why/how doesn't intensity? (I run intensity using long only for now.) The
ISO decoder takes the block type for decoding the intensity position info
from the left channel, which essentially requires both
Joshua Bahnsen schrieb am Mon, 25 Sep 2000:
I'm using the configure generated Makefile that I've changed to suit my
needs.
Does it work using Makefile.DJGPP ?
The configure generated Makefile does not work for
me because of the conditional assingment ?= which
I think we can make a very simple library setup stuff:
proposal:
int lame_open();
// allocates internal structures
int lame_set_param( int handle, LameParameter Parameter, int Value );
// assigns Lame's parameter a value
int lame_init_params( int
Sigbjørn Skjæret schrieb am Mon, 25 Sep 2000:
[...]
This way there is no need to parse any strings, we don't pass
any pointers, the setup routine would just be a big switch/case.
This is basically the way TagItems work when passed on stack, in fact, that
combined with another identical
Hi Gaby
Why can we read in the litterature that humans got 25 CB but mp3 uses only
22?
let us try to get it in order:
bark scale is used by the spreading function
Bark 0 : 0-100 Hz, Bark 24: 15.5 - 20.4 kHz
masking is calculated for convolution bands
Gabriel Bouvigne schrieb am Son, 24 Sep 2000:
So the highest subbands don't have any scalefactor? I know that Brandebourg
said that there is no proof that 16kHz really contribute to the hearing of
the music, and then it could be intentionnal, but could it be a "bug" or
mistake in the mp3
Hi Joshua
If defined, what does ALLOW_MIXED do?
josh
well, actually nothing, as mixed blocks are not supported
by LAME. You may try Takehiro's snapshot, I think he has
implemented mixed blocks in it.
Ciao Robert
--
MP3 ENCODER mailing list (
Steve Lhomme schrieb am Sam, 23 Sep 2000:
Is RH_AMP the same as RH_NOISE_CALC ?
Yes, Steve.
Ciao Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Hi Takehiro,
I don't understand your patch to inc_scalefac_scale().
Why did you turn the scalefactor band adjustment off
for short blocks, but turning on scalefac_scale?
Wouldn't that result in a multiplication by 2 for
the short block scalefactors?
Ciao Robert
--
MP3 ENCODER mailing list (
Youri Pepplinkhuizen schrieb am Mit, 20 Sep 2000:
Hi,
I got some suggestions for LAME. They're not too complicated (probably are
to implement, though), so here goes:
- LAME VBR doesn't encode the LSB (Least Significant Bit) correctly (as
described on
Hi Gaby!
I'm sorry to bother you, but what is this option? I've never seen it
before
--raise-smr x with 0.0 = x = 1.0
the signal to mask ratio (SMR) for every subband / group of
subbands is the basic output of every psychoacoustic model
for Layer
Mark Taylor schrieb am Don, 21 Sep 2000:
I like "frontend". And also a "libmp3lame" directory for the library.
Moving all this code into subdirectories will be disruptive:
all the different makefiles and MSVC project files need
to be updated. We will also need a ./configure/make system
Takehiro Tominaga schrieb am Mit, 20 Sep 2000:
"R" == Robert Hegemann [EMAIL PROTECTED] writes:
R I'm using GNU Make version 3.77, does above work for other Make
R versions?
Yes, it does not work on 3.77. so I upgraded it 3.78.1 and it works fine.
---
[EMAIL PROTECT
Mark Powell schrieb am Mit, 20 Sep 2000:
On Wed, 20 Sep 2000, Robert Hegemann wrote:
Takehiro Tominaga schrieb am Mit, 20 Sep 2000:
"R" == Robert Hegemann [EMAIL PROTECTED] writes:
R I'm using GNU Make version 3.77, does above work for other Make
R versions?
Takehiro Tominaga schrieb am Mit, 20 Sep 2000:
I want to make "example" or "frontend" directory and move lame.c and gtk*,
brhist.c and so on into it.
Any Ideas ?
I think Mark is thinking about something similar.
Why not mimic Vorbis and make a tools folder
for the example programs and move
Mark Powell schrieb am Mit, 20 Sep 2000:
The "?=" operator was introduced on 1998-03-02 in v3.76.90 of GNU make.
v3.77 handles this operator perfectly well. I've just tested it on machine
with v3.77.
--
# make --version
GNU Make version 3.77, by Richard Stallman and Roland McGrath.
Gabriel Bouvigne schrieb am Die, 19 Sep 2000:
Am I the only one thinking that there is a problem?
No, I just modified the --athlower switch so that it will
not modify the ATH for sfb21.
Ciao Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
The configure generated Makefile will not recognize
my Linux system, I have to change
UNAME ?= $(shell uname)
ARCH ?= $(shell uname -m)
into
UNAME = $(shell uname)
ARCH = $(shell uname -m)
I'm using GNU Make version 3.77, does above work
for other Make
Sigbjørn Skjæret schrieb am Mon, 18 Sep 2000:
The fix is to do what Frank suggests: go to a data-encapsulted
type interface, where every parameter must be set via
a function. We would need to write about 100 functions
along the lines of: lame_set_input_samplerate().
A much better (and
Frank Klemm schrieb am Mon, 18 Sep 2000:
::The whole sfb21 thingy is a kludge, we should extend psymodel.c
::to calculate maskings for that band too.
::
:: the ATH is so large in that band, I would be afraid that
:: any computed maskings would always be ATH, and thus
::
Frank Klemm schrieb am Mon, 18 Sep 2000:
::
:: 1)one type is long double, the other will be casted to long double
:: 2)one type is double, the other will be casted to double
:: 3)one type is float, the other will be casted to float
Fully wrong.
The rest I
Frank Klemm schrieb am Mon, 18 Sep 2000:
:: Hi Frank,
::
:: ::
:: :: 1) one type is long double, the other will be casted to long double
:: :: 2) one type is double, the other will be casted to double
:: :: 3) one type is float, the other will be casted to float
::
Frank Klemm schrieb am Mon, 18 Sep 2000:
::
::
:: Frank, that's not what Gaby is talking about.
:: But if you are talking about the spreading function, there
:: are more parameters than loudness:
:: - frequency
:: - tonality
:: - temporal effects
:: - difference tones reducing
Takehiro Tominaga schrieb am Die, 19 Sep 2000:
Wow! great, Florian!
M All the various options (GTK, libsndfile, VBR historgram, mpeg
M decoding) are available through ./configure options. see
M INSTALL for details. By default it will try to install
M everything, if
Piter B. schrieb am Son, 17 Sep 2000:
Hi!
Nobody interested in implementing some sort of psycho masking in lame...
(see attachment Dolby, Fraunhofer)
Regards
Piotr Borowski
What's your problem with LAME's psychoacoustic?
Do you think LAME has none and should have the same
Hi all,
I see a tendency that compiler warnings get casted away.
The problem is, that these castings make your compiler
happy, but there is a high potential that this only covers
BUGS. Everytime someone will cast away compiler warnings
he should back up his change with an assertion!
For
Gabriel Bouvigne schrieb am Son, 17 Sep 2000:
Well, CBR doesn't care about sfb21 distortions, VBR does
for MPEG-1. When using --noath the sfb21 still gets its
ATH value.
Ok, but how about --athlower 100 ? Will it leads to an endless loop? That
could be a problem. I think that when
Albert Faber schrieb am Son, 17 Sep 2000:
Robert,
And if you don't cast it, you will leave it up to the compiler, thus the
behavior becomes compiler specfic, will it cast the unsigned to a signed or
will it cast the signed to an unsigned value. What does happen, if you don't
cast, and assign
Mark Taylor schrieb am Son, 17 Sep 2000:
Gabriel Bouvigne schrieb am Son, 17 Sep 2000:
Well, CBR doesn't care about sfb21 distortions, VBR does
for MPEG-1. When using --noath the sfb21 still gets its
ATH value.
Ok, but how about --athlower 100 ? Will it leads to an
Albert Faber schrieb am Son, 17 Sep 2000:
Robert,
So if i have the following piece of code
int my_signed= -1;
unsigned int my_unsigned=10;
if (my_signedmy_unsigned)
printf("my_singed my_unsigned\n");
else
printf("my_singed is = my_unsigned\n");
It should print: "my_singed
Sigbjørn Skjæret schrieb am Sam, 16 Sep 2000:
While going through the all too usual bunch of suspicious warnings, I stumbled
over a few more concerning ones...
psymodel.c:
"FLOAT8 thmM = thmM;" .. I assumed this was a typo and changed it to
"FLOAT8 thmM = thmm;"
yes, sorry my typo
Mark Taylor schrieb am Mit, 13 Sep 2000:
Thanks - I'll revisit your website.
Another question :) Is there a preferred (or even mandatory)
sequence to command-line opions for Lame ? I remember how quirky
DOS could be in this respect
The only problem is if you
I just looked again into our psymodel.c and
I'm wondering since when we activated the
following code:
#if 1
/* additive masking */
enn = gfc-w1_l[sb] * eb[gfc-bu_l[sb]] + gfc-w2_l[sb] * eb[gfc-bo_l[sb]];
thmm = gfc-w1_l[sb] *thr[gfc-bu_l[sb]] + gfc-w2_l[sb] *
Roel VdB schrieb am Mon, 11 Sep 2000:
Hello Gabriel,
Monday, September 11, 2000, 5:43:55 PM, you wrote:
I am fundamentally agains crippling an encoder to fit the needs of an
inept decoder. If 320 is chosen by LAME on -V1, it is there for a
reason!
GB This point is debatable.
GB I
Frank Klemm schrieb am Son, 10 Sep 2000:
::
:: Second question: is it possible to obtain better quality then
:: "-h -ms -b256" with some vbr-mode. Maybe I am far off, but if I
:: encode with vbr and there are 320kbps-frames these parts should be
:: encoded better than in
Frank Klemm schrieb am Son, 10 Sep 2000:
CBR VBR ABR
Can use different frame sizes no yes yes
File size depends also on
complexity of sourceno yes no
Can adapted bit demand by
* different frame sizes no yes yes
* use of
Hallo Frank,
:: Als Du zu -mf und -mj den Bitverbrauch über mehrere Titel
:: verglichen hattest, so war LAME wahrscheinlich nicht mit
:: meinem extra Code RH_VALIDATE_MS übersetzt? Eigentlich
:: sollte nähmlich -mj weniger Bits verbraten als -mf.
::
Die Korrelation heranzuziehen, ist
Gabriel Bouvigne schrieb am Sam, 09 Sep 2000:
Could anyone please explain -X4 ?
The actual quantization is better than the best so far
if at least one of five constraints is fullfilled.
Here is what Greg Maxwell (inventor of -X4) wrote 15. Dec 1999:
-X4 resulted from testing, overthinking
Mark Taylor schrieb am Mit, 06 Sep 2000:
LAME CVS:
I spent quite a lot of time in the last two days trying to validate
the current version of LAME from CVS. I've concluded that this is not
possible. There are many minor output changes that I did manage to
account for (like someone
Mark Taylor schrieb am Mit, 06 Sep 2000:
So as promised, but delayed, LAME CVS mainline is reverted back
to as it was Aug 31. The previous version is in the 'pfk1'
branch. If you want it, you need to do:
cvs update -r pfk1
That branch has a lot of nice code improvements, and I hope
Mark Taylor schrieb am Mit, 06 Sep 2000:
sorry, that is now fixed. you may need to redo cvs update -r pfk1
Mark
Thanks Mark, I could check in now.
Ciao Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
[EMAIL PROTECTED] schrieb am Die, 05 Sep 2000:
Howdy Gabriel,
Am I the only one wich doesn't understand what Frank is telling?
Can anyone explain a little?
You are not alone. Once I get past his aggressively authoritative posting
style (which is a major disincentive to understanding
[EMAIL PROTECTED] schrieb am Die, 05 Sep 2000:
Howdy,
How to compile lame on a system where only a C++ compiler is
available (the
C compiler costs extra money)? Currently lame generates
nearly uncountable
errors with a C++ compiler.
I'm having a similar problem trying to compile
Frank Klemm schrieb am Mit, 06 Sep 2000:
May be the following file can be added. I use it do quick show differences
of two brances. Quick and dirty, can still be optimized. I named it MGDIFF
and it needs mgdiff.
#! /bin/bash
for i in {*,*/*,*/*/*,*/*/*/*}.{c,h}; do
file1=`pwd`/$i
Frank Klemm schrieb am Die, 05 Sep 2000:
Layer I now seems to work.
Is there a simple Layer I coder out there to test Layer I decoding?
I've never have seen a Layer I file.
Yes, get the ISO reference software dist10.tgz (ie at www.mp3-tech.org)
Ciao Robert
--
MP3 ENCODER mailing list (
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.
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
Estrunfus Maleficus schrieb am Son, 03 Sep 2000:
Mathew Hendry wrote:
From: "Scott manley" [EMAIL PROTECTED]
You should search for a prgaram called 'Shorten' this is also a lossless
compressor for Unix (free for unix
*ahem*
hello , considering that there isn't a monkeys
Frank Klemm schrieb am Fre, 01 Sep 2000:
lame/CODING_STYLE, version 0.001 ;-)
-
This is the first try of a Coding Style:
notes on some points
* Don't use tabulators (the character with the value '\t') in source code,
Frank Klemm schrieb am Fre, 01 Sep 2000:
Why a quadratic interpolation is used for upsampling instead of a sinc
interpolator?
--
Frank Klemm
I can't answer your question, but where is upsampling from 44.1 to 48 kHz
good for?
Ciao Robert
--
MP3 ENCODER mailing list (
Frank Klemm schrieb am Don, 31 Aug 2000:
:: b) LAME's filter is not much useful for highpass filtering
::
External filters are available. For integration the f*cking "signed short
int" format must be replaced by "float" or "double".
I've heared (by listening) that the lame FIR high pass
| After monday I got only two messages ( both on wednesday ) :
|
| - [MP3 ENCODER] test please ignore , from Jan Penman
| - [MP3 ENCODER] presets , by Robert Hegemann
|
| David Balazic
me too. Maybe holidays?
Hey, that sounds cool: World Wide Vacation
or a little bit sloppy
Hello everyone,
just a quick note that I've release final version 1.1.0 of RazorLame,
available from http://www.dors.de/razorlame/
For those who don't know: RazorLame is a Windows front-end for LAME.
Regards,
Holger Dors mailto:[EMAIL PROTECTED]
Nice
David Balazic schrieb am Don, 31 Aug 2000:
For VBR mode the max bitrate is set on one screen, while min bitrate
on the other. Confusing.
Also when ABR is selected, the max bitrate slider should be turned off.
Don't just blindly throw the CLI options on the screen , think too :-)
David
Frank,
what's the reason to mess up the presets?
a) with a highpass of 300 Hz you are loosing fundamental frequencies
of male voices (90-250 Hz)
FYI female: 160-500 Hz
kids : 200-800 Hz
b) LAME's filter is not much useful for highpass filtering
c) when you resample and
Hi, there.
Could someone explain to me what this new option called 'RH_AMP'
of LAME CVS version means? Makefile for gcc tells me just
'special noise calculation.'
However, I have no idea about what exactly this means. Oh, well...
Thank you in advance.
Keeshond.
If you make a
:: FYI, the strategy I took with MAD was to provide full (28-bit)
:: internal precision output from the decoder library API and let
:: the application decide how to scale or resample it to however
:: many bits of precision it wants.
::
I want 86 dB (CCIR). That can be achived with 16
Jaroslav Lukesh schrieb am Die, 22 Aug 2000:
lame -h -m j -b 64 --voice --noshort --resample 22.05 --lowpass 11.025
--lowpass-width 0 --mp3input x.mp3 x.small.mp3
why not lame --preset fm -h -k x.mp3 x.small.mp3 ???
but I would not use -k there.
Note that --voice options sounds
Frank Klemm schrieb am Die, 15 Aug 2000:
I have a historic recording (1962, Spoken words) with nearly no useful
signal above 11 kHz. So I tried to code it with 22.05 kHz and 44.1 kHz.
The file with 44.1 kHz is much smaller than the file with 22.05 kHz.
Is this right? The difference is +42%
Mark Taylor schrieb am Fre, 18 Aug 2000:
The mpglib/mpg123 routine is supposed to return only 1 frame
of data. 1 frame = 1152 samples MPEG1 layer 3, 576 samples MPEG2 layer3,
and (not-very-good) the check looks like this:
if ((outsize!=576) (outsize!=1152)) {
Hi all!
Albert Faber schrieb am Don, 17 Aug 2000:
Yesterday, I made the modification/additions in order to support layer I/II
decoding. However, since my linux environment is not running correctly right
now (and since I'm always scary to change things without testing them) I did
not made the
Hi all!
I just updated the Makefiles and tested LAME's new decoding capabilities
with some toolame-02h generated MP2s.
I did not find the time to do the same with mp[1g] files yet, maybe later.
OK, I found the time, but with LayerI there seems to be a problem:
Sterling Windmill schrieb am Don, 17 Aug 2000:
I realize that it will play if renamed, but I need an actual wav header to
be present, I know these utilities exist, I just can't seem to find one.
You may look at dailymp3.com ?
Ciao Robert
--
MP3 ENCODER mailing list (
Bill Currie schrieb am Don, 17 Aug 2000:
I've been having problems with lame `randomly' writing `incorrect' Xing
headers. I finally figured out that it's not random (it's my fault) and lame
isn't writing incorrect Xing info, but no info at all. What's been going on? I
start up lame
lame -k
Hi Dimitry and Nathan!
Nathan Blomquist schrieb am Mit, 16 Aug 2000:
I did some testing.
I had a test.wav and I used my lame-3_86BetaWin32.zip and my lame-3_86BetaDJGPP.zip.
I then tried -v only. They came up different. I then tried --vbr-new and
they both came out the same. Then came
Frank Klemm schrieb am Die, 15 Aug 2000:
lame -mm --cwlimit 11.025 --resample 22.05 --lowpass 11.025 -b64 -V1 input.wav
output.mp3
coredumps.
The bug seems to be in count_bits_long() and huffman_init()
in takehiro.c. It occurs when big value becomes 576.
I'll patch it later this evening.
Hi Mike!
[EMAIL PROTECTED] schrieb am Son, 13 Aug 2000:
Robert wrote
I checked in today a round about 20 percent
faster old VBR code.
What changes did you make?
As you probably know, the old VBR routine tries to
get an acceptable quantization at different bit
constraints, resulting
Hi Magnus!
Magnus Holmgren schrieb am Sam, 12 Aug 2000:
Robert Hegemann wrote:
Btw, after a test run, I noticed that 405 bytes differ (at least
according to the simple cmp program I wrote :). Is that something to
worry about?
Well, for me using the gogo routine decreases
Hi David!
David Bridson schrieb am Son, 13 Aug 2000:
As you probably know, the old VBR routine tries to
get an acceptable quantization at different bit
constraints, resulting in something like a binary
search for the optimal bit amount needed.
While we're on the subject of VBR, I have
Hi all,
I checked in today a round about 20 percent
faster old VBR code.
Have fun
Robert
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
engdev schrieb am Don, 10 Aug 2000:
I assume that most users of LAME are using the Linux OS, as the GTK
extensions are based around (I believe) X-windows. I don't use Linux, and am
stuck with windoze. Are there any utilities around to run the frame analyser
with windoze 95, 98 or NT ?
PS: I
1 - 100 of 230 matches
Mail list logo
