IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
LAME 3.98.2 -r flag error
EricFGregory
post Sep 27 2009, 09:36
Post #1





Group: Members
Posts: 3
Joined: 30-August 09
Member No.: 72770



Okay, lets start from the beginning. Sorry for the ensuing giant wall of text; I'm a little drunk.
For the longest time I have been trying to rip MP3s in LAME and have been getting the same damned problem. At the start of every file there was this very audible click. Almost like a bad popping sound from some old vinyl. I started downloading some really poorly done precompile from a shady site (I'm reformatting that computer soon) and got so annoyed I actually installed VS .Net to compile LAME for myself.
No matter what I always got this damned click. Hardware made no difference.

The whole time I'd been tweaking flags trying to fix it, and improve quality. Now before solving this problem my flags looked like this:
-r -s 44.1 --bitwidth 16 -V 0 -q 0 --replaygain-accurate --clipdetect --priority 3 --add-id3v2 --pad-id3v2 --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" %s %d
(Note: EAC to LAME)

I was trying -V and -q as likely suspects, as they actually did something.

Now I know LAME will auto detect the raw PCM input that -r denotes, but at the time it seemed more intelligent to just tell it that the CD was PCM at 44.1kHz and a bitwidth of 16.
Just made sense to not have it detect this.

Long story short -r, for whatever reason, causes the output file to start with a freaking loud popping sound.

Also I think -r is actually slower than having LAME detect input on it's own.
FML.

Anyways, just thought I'd give everyone here a heads up.
Go to the top of the page
+Quote Post
NeoRenegade
post Sep 27 2009, 09:54
Post #2





Group: Members
Posts: 723
Joined: 29-November 01
Member No.: 563



Itís happening because youíre telling LAME that something that isnít raw PCM is raw PCM.

ďItís not a bug, itís a feature.Ē
Go to the top of the page
+Quote Post
lvqcl
post Sep 27 2009, 10:24
Post #3





Group: Developer
Posts: 3212
Joined: 2-December 07
Member No.: 49183



Just remove "-r -s 44.1 --bitwidth 16" switches because EAC doesn't send raw data to LAME.
Also "--replaygain-accurate --clipdetect --priority 3" switches are quite useless IMO.
Go to the top of the page
+Quote Post
greynol
post Sep 27 2009, 20:14
Post #4





Group: Super Moderator
Posts: 10000
Joined: 1-April 04
From: San Francisco
Member No.: 13167



Almost all of these switches are either totally useless (-q0, -replaygain-accurate, --clipdetect) or simply unnecessary.

-V0 %s %d

This is all that is really necessary since EAC can tag mp3 files.


--------------------
Your eyes cannot hear.
Go to the top of the page
+Quote Post
EricFGregory
post Sep 30 2009, 14:03
Post #5





Group: Members
Posts: 3
Joined: 30-August 09
Member No.: 72770



QUOTE (NeoRenegade @ Sep 27 2009, 04:54) *
Itís happening because youíre telling LAME that something that isnít raw PCM is raw PCM.

ďItís not a bug, itís a feature.Ē

Ahh, that will teach me to gloss over the research. I was under the impression .wav was PCM. Stupid me.

Also; do --replaygain-accurate --clipdetect and -q0 actually do nothing? They seem to have documentation behind them.
Go to the top of the page
+Quote Post
pdq
post Sep 30 2009, 14:19
Post #6





Group: Members
Posts: 3305
Joined: 1-September 05
From: SE Pennsylvania
Member No.: 24233



Just to clarify, wav files nearly always consist of a header plus PCM data. A RAW PCM file is just the PCM data, no header. By adding the -r switch you were telling lame that ALL of the contents of the wav file were PCM data, so the header was encoded as though it were more audio data, making a loud noise at the start.
Go to the top of the page
+Quote Post
lvqcl
post Sep 30 2009, 16:22
Post #7





Group: Developer
Posts: 3212
Joined: 2-December 07
Member No.: 49183



1) LAME calculates track replaygain value and stores it in LAME header in mp3 file. It slows encoding down, and almost all programs never use this value. It can be better to use --noreplaygain instead of --replaygain-accurate --clipdetect.

2) for LAME 3.98 there is no difference between -V0 and -V0 -q0.
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 20th April 2014 - 09:48