In Windows, I usually use either foobar2000 or easyLAME for MP3 encoding.

I always got the annoying miniscule gap that comes with MP3, yet never the two second one.

With Linux, encoding from the command line with LAME 3.90.3 gets me a two second gap. This wouldn't be a problem, but the program that I use to get ID3 tags and filenames for it uses FreeDB and the two second gap screws it up when the song is 4:10 instead of 4:08.

I tried encoding one song at once, with the usual



and with what I use to encode an entire directory of WAVs



Is there anyway to get rid of the pregap it puts on them, or a switch? I know I'm missing something simple here. I did a search, and got nada.

Also... I'm using --alt-preset insane, since I've got well enough room for it, for what I'm doing now.

Thanks for helping an ignorant fool. B)

hm ...

2 second long gaps is nearly impossible if your wav's are clean. as far as i know mp3's are just a few frames different than the source material.

commandline for ripping:


commandline for encoding:


if your files still way to long, your cdrom might be a "very good one"

BadHorsie

Edit: have you tried to play the wav's? are the gaps still there?

That line worked. Thanks!

ähm ... which one?

was it a ripping or a encoding problem?

BadHorsie

For encoding.

I had an APE+CUE file, I converted to WAV+CUE, seperated, then converted.

That line, it worked, well, halfway. Some of the MP3s will have a one second gap, some won't.

I want to see if any other distro has this problem. Despite how good slackware is, it's the only distro to have these annoying quirks.

What also angers me, is that it always does it on the same tracks. Actuallty, it's the same exact WAV each time.

I tried unRARing the APE+CUE, converting to WAV, and seperating again, then converting, and still the same thing. So there's no way I can pinpoint the problem.

BTW, I used bchunk to seperate the WAV+CUE into seperate WAVs.

Last time I comment on my own thread.

When I rip the problemetic track off the CD it's 4:12. When I encode the one, that I seperated from the CUE+WAV, with oggenc, it's 4:09, which is the size of the track I seperated from the WAV+CUE. When I encode that track with LAME, I get a 4:10 long track. When I encode the 4:12 track I ripped from the CD, with any encoder, it's 4:12.

Now I'm a bit confused.

Fixed the problem.

Despite its popularity everyplace I've asked, bchunk is retarded when it cuts stuff. I just got EAC+WINE, and it cut it with gaps corrected, and when I converted them to MP3s, my proggy can recognize the album with freedb just fine.

Woah woah woah.... Hold on a sec. You've got EAC working under wine? [jedi]You are going to tell me the secret.[/jedi]

Now what are you running Linux on, your Inspiron?

EAC works fine under SuSE 8.2 and RedHat 9. but the ripping process does not work! on SuSE there's no cdrom available and under RedHat i can rip from cdrom but the wav are just silence.

BadHorsie

A clear example of ABX mythology; if your drives are producing clean rips from non-damaged discs, your 11/17 ABX score means little more than an equal number of coin flips. Sorry.

As for using EAC under Wine, I did a little Googling and came up with the following tidbit, which might prove useful (I've not tried it myself so I can't verify, but it sounds worth investigating at least):

Hope this helps.

- M.

As explained millions of times before: There is no point in ABXing rips. A rip is perfect or it is not.

BadHorsie, go get your asbestos suit, because you're gonna need it.

i have not a glue what you are talking about

BadHorsie

thanks for the link.

EAC still does not show the correct devices under RedHat 9. started as root, permission of the scsi devices changed ... ah bah ... who needs EAC

BadHorsie

Flames... Lots of big hot flames... >_<

Uh.. my secret? Typing wine EAC.exe

It works in Slackware. I'm using my only computer, Inspiron 8200. I haven't tried ripping yet, I've just tried using the seperate WAV by CUE with gaps corrected, and that works.

Just for the hell of it, I'll try setting it up to rip now and try ripping some 4-5 second skip before bed. B)

I still like GRIP, mind you, since my CDs are pretty perfect, and it works without WINE. Although, ALL OF EAC's features work with WINE. It might as well be %100 Linux compatible, I've never seen WINE behave this well. Maybe I'll use EAC after all.. or GRIP. Damn high class problems.

It works! %100 track quality in the log and the WAV plays nicely in XMMS.

I'll answer more questions tomorrow. For now.. time to sleep.

My only answer for now.. SuSE/RedHat/Mandrake are evil. I've had lots of experience with all of them.. Slackware, so long as you know people that can help you, is a good distro. Trying to be easy as windows and stable as Linux just doesn't work well. I like Slackware(despite crap like bchunk that makes it look bad ).

Hmm, I'll have to get it out and play with it again. I am a bit weird in that both my primary CD reader and my CDR drive are both SCSI, so maybe there's a little finesse involved in getting that working. I don't think the distro (Gentoo in my case) should be too much of an issue since they all use basically the same kernel/drivers and the same wine. I guess I'll futz with it (I needed an excuse to compile the lastest kernel anyway).