Re: [MP3 ENCODER] Interesting high quality settings and possible bug

Gargos Chode wrote about the -k switch: Hrmm... that is an interesting idea. I completely hadn't thought of this. Does this actually take away bits from being used to encode the audio frame? If so then what is the real use of this switch? I had thought this switch would help to prevent

[MP3 ENCODER] VBR brutal test file, bug in ATH?

I've started testing Lame with synthetic input to test some lame properties. One is a dual tone sweep, a slow araising sweep from 16 Hz to 14 kHz and a second arising from this frequency up to 18 kHz. CBR (-b160): adds some clicks at the end of every fast sweep VBR (-V4):

Re: [MP3 ENCODER] AIFC - MP3 encoding

Chad Cunningham wrote: Hi, I seem to have hit a wall here... I want to do an mp3 ripper for Mac OSX, which I thought would be a simple enough project, but it's getting more complicated. The OS automatically mounts cd's in a /Audio CD directory as aiff files. I thought this would make things

Re: [MP3 ENCODER] MP3 encoding speed : LAME XING

On Fri, 6 Oct 2000, engdev wrote: You're right Mark, compared to Lame 387 MMX --abr 128 Xing is only two times faster Bo) Regards, Wim Speekenbrink Using 160kbps for both LAME and Xing, encoding "Dire straits - telegraph road" LAME takes about 1.5 times longer than Xing. Is that

Re: [MP3 ENCODER] Interesting high quality settings and possible bug

Hello, Hrmm... that is an interesting idea. I completely hadn't thought of this. Does this actually take away bits from being used to encode the audio frame? If so then what is the real use of this switch? I had thought this switch would help to prevent the mp3 from being possibly corrupted

Re[6]: [MP3 ENCODER] -q1

Hello Gargos, Friday, October 06, 2000, 2:13:24 AM, you wrote: GC Hello, GC Roel, maybe you should give these settings a try on that track: GC -V1 -mj -b128 -q2 -d -k --nspsytune --athlower -35 -X3 GC The bitrate stays pretty low (~224kbps) and it sounds very good... GC almost identical to

[MP3 ENCODER] modularization

Hi, I browsed the archive and have some comments: Takehiro wrote: (install prefix) BTW, default is changed /usr/include, by Florian. I think we should use /usr/local. At first I used /usr/local, but it seems that /usr/local/lib isn't in the standard library path. It seems that not many

Re: Re[6]: [MP3 ENCODER] -q1

also: isn't that "-35" not extremely harsh on the athlower? I think that using a negative value with athlower is a bad idea. Regards, -- Gabriel Bouvigne - France [EMAIL PROTECTED] mobile phone: [EMAIL PROTECTED] icq: 12138873 MP3' Tech: www.mp3-tech.org -- MP3 ENCODER mailing list (

Re: Re[6]: [MP3 ENCODER] -q1

-- On Fri, 6 Oct 2000 16:40:23 Roel VdB wrote: It sounds much better on fatboy than the other options. GC I'd like to hear your thoughts on these settings. I think it's possibly only usable on this fatboy example. On velvet it sounds really poor and the bitrate is much too high: Im

Re[8]: [MP3 ENCODER] -q1

Hello Gargos, Saturday, October 07, 2000, 1:40:57 AM, you wrote: GC Im not sure which part exactly you mean sounds very poor. The graphs you provided show a lower noise, this because --nspsytune probably. It simply sounds poor, really poor. It sounds nothing like the original on my

Re: Re[8]: [MP3 ENCODER] -q1

Hello, I use the one with the "RH extensions" from Dmitry. (thanks for all the compiles and hard work Dmitry btw!) Do you have a link to this version? I would like to try it out. Thanks. Dibrom 10% cash back on all your calls through 2000 at Lycos Communications at http://comm.lycos.com --