Thanks. This fix is also in but in a slightly different way. I modifed
the actual tagging routines in lame.c to check for Ogg Vorbis output
rather than making the client code responsible, so we only have to do
the test in one place rather than in all clients.
On Fri, Jul 07, 2000 at 01:08:55AM
I forgot to mention:
There is no advantage to use --nspsytune with CBR 128 as far as I
tested.
Please use --vbr-old when use --nspsytune.
--nspsytune turns on -Z.
--
Naoki Shibata e-mail: [EMAIL PROTECTED]
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
From: "Naoki Shibata" [EMAIL PROTECTED]
--nspsytune command line option turns on following things
1. Addition of simultaneous masking.
What does this one mean?
2. MAXNOISE is selected if max/avg exceeds predefined threshold.
3. long block fft window function is changed to blackmann
Mathew 1. Addition of simultaneous masking.
Mathew
Mathew What does this one mean?
If there are two or more maskers, produced masking threshold is not
just an addition of them, but more than that in most case. I coded this.
This page explains same thing, but the formula I used is not
Fair enough I guess.
-Original Message-
From: Mark Taylor [mailto:[EMAIL PROTECTED]]
Sent: Saturday, July 08, 2000 10:31 AM
To: [EMAIL PROTECTED]
Subject: Re: [MP3 ENCODER] new VBR code
There is so much stuff constantly changing with lamenew
options, VBR,
CBR,
I was under the impression that VBR mode was better...so I have been trying
to use it. But at this point I have absolutely no idea if what I'm encoding
is better than CBR mode or not. I have absolutely no idea if I'm using a
good set of options or not. I'll probably just wait until lame is
I cannot see the point in using -V0 with "-b %bitrate% -B %bitrate%". I´ve
been trying, and can´t see (or hear) the difference.
Maybe it´s just me, but I suppose -V0 *must* encode with optimum quality. I
don´t know... In this case, if we want minbitrate AND maxbitrate to be 128,
why don´t try CBR
Hi,
I have just commited changes to add --nspsytune option.
With this option, vbrtest.wav is encoded perfectly, and
encoded sound becomes more natural to my ear though encoded file size
increases.
--nspsytune command line option turns on following things
1. Addition of
I was under the impression that VBR mode was better...so I have been trying
to use it. But at this point I have absolutely no idea if what I'm encoding
is better than CBR mode or not. I have absolutely no idea if I'm using a
good set of options or not. I'll probably just wait until lame
test
I am definitely interested in bitrates higher than 128. In my personal
opinion, 128 is not good enough. In CBR I would have to encode at 192 to be
happy. I was under the impression that if I use VBR mode with 128 as the
bottom...that I would get an average about about 185 or so (which is what
Hi!
I'm new here so please don't bash me too hard
;)
Anyway, just found this wonderfull encoder, LAME
:)
I've noticed that it seems to raise the dB level
very slighty in the encoded mp3 files, found this out by loading the original
.wav file into sound forge and the mp3 one, "clipping"
When encoding 44.1 kHz audio to a 128kbit/sec mp3, lame by default cuts
off the high end with a transition band of 15115 Hz - 15648 Hz. (32 kHz
audio to 128kbit/sec mp3 has a slightly lower cut-off by default with a
transition band of 14065 Hz - 14452 Hz.)
If someone was encoding
Quality (default value Normal):
With the LAME encoder, you can specify the output quality; thus you can trade
off encoding time against sound quality. The default (normal) is recommended,
since the high output option might cause ringing artifacts at lower bit-rates.
The voice quality is
On Sun, 9 Jul 2000, Don Melton wrote:
Thanks. This fix is also in but in a slightly different way. I modifed
the actual tagging routines in lame.c to check for Ogg Vorbis output
rather than making the client code responsible, so we only have to do
the test in one place rather than in all
David,
Avoid HTML mail. Please send text-only e-mails to this list, since this
list is intended for multiple people who uses mail agents other than
Outlook Express 5.0, and even non-Microsoft platforms.
Claudio
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )
Is there any way to force a DOS box close after lame has completed encoding?
With the Windows binary, it exits properly but with the DOS one it just says
Finished and the box stays open. So if I'm using the DOS version to encode
with say audiograbber, I can never get to the next track without
Click on Props for the DOS icon, select Program and place a tick in "Close
on Exit"
- Original Message -
From: "Joshua Bahnsen" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, July 10, 2000 12:56 PM
Subject: [MP3 ENCODER] lame exit problems
Is there any way to force a DOS box
Title: RE: [MP3 ENCODER] lame exit problems
This should work.
Right-click the icon at the top left of the DOS window. Select Properties in the Program tab select Close on Exit. This will create a LAME.PIF which Windows should recognise when loading LAME.EXE.
Ross.
-Original
After 8-9 hours of trying to grasp a fraction of the source (no
programmer, no psy-coding background, plain dumb :)) (in a futile attempt to find
the reason why
"-b" is misinterpreted (?)) this catched my eye:
qadjust=-2.5; /* start with -1 db quality improvement over quantize.c VBR
Hi,
I have just commited changes to add --nspsytune option.
With this option, vbrtest.wav is encoded perfectly, and
encoded sound becomes more natural to my ear though encoded file size
increases.
--nspsytune command line option turns on following things
1. Addition of simultaneous
On Sat, Jul 08, 2000 at 09:39:59PM -0400, Joshua Bahnsen wrote:
Has there ever been any thought of using something like id3lib
http://id3lib.sourceforge.net to handle tagging?
Yes. When I rewrote the tagging code recently to add ID3 version 2
support I considered it. But if you look at my
22 matches
Mail list logo
