Burst Mode?

Feb 18, 2004 at 1:57 AM Post #4 of 15
Usually burst mode should be fine if there are no scratches, but I prefer to just stick with secure mode for piece of mind that it is always the best possible quality. Use secure mode for scratched CD's, for sure.

OT: It must be great to live in Lakewood, what a nice area. Some friends of my mother live there, we come to visist every once and a while. I just love Colorado in general, though. Been to Ouray before? It is a fun little city to your south.
 
Feb 18, 2004 at 2:08 AM Post #5 of 15
Burst mode defeats the purpose of using EAC..since the purpose of EAC is to do a highly accurate bit for bit rip of the contents of the CD.

Secure mode is gonna be slower, sure, but makes sure no errors get through.
 
Feb 18, 2004 at 2:39 AM Post #6 of 15
Eh, i tried secure mode and just found it to be entirely too slow, averaging about 5x speed for ripping, literally taking 10-15 minutes per cd...absolutely ridiculous. So i switched to burst mode and now it only takes a few mins (if that) to rip a cd using lame. So far, everything sounds fine out of my njb3 and hell, i don't plan on doing any critical listening so it doesn't bother me that much anyway and none of my cd's are scratched.
 
Feb 18, 2004 at 4:44 AM Post #7 of 15
Quote:

Originally posted by Helloween
Eh, i tried secure mode and just found it to be entirely too slow, averaging about 5x speed for ripping, literally taking 10-15 minutes per cd...absolutely ridiculous. So i switched to burst mode and now it only takes a few mins (if that) to rip a cd using lame. So far, everything sounds fine out of my njb3 and hell, i don't plan on doing any critical listening so it doesn't bother me that much anyway and none of my cd's are scratched.


It doesn't matter whether the CDs are scrathed or not. Read errors can occur on brand new discs, for example a disc that came from a bad batch of pressings.

Haste makes waste, and this is Head-fi after all, lol.

BTW, you mustn't have experience with the days of quad speed CDRW..I remember my old 2x drive. Took 40 minutes just to burn 1 CD. You should consider yourself lucky
smily_headphones1.gif
 
Feb 18, 2004 at 5:37 AM Post #8 of 15
Thanks for the advice. I was taking speed over quality I suppose. However, I still think I'll use Burst on random CD's to save some time, but make use of Protected Mode for the recordings that I care about. My CD drive is rather slow.

Iron_Dreamer: Yeah, Lakewood is a pretty great place to live. I've certainly no complaints (only that there are no hi-fi stores anywhere to my knowledge). Soon I'll be a Boulder man though, when college starts... Sorry, never been to Ouray, but I'm sure it's as nice as you say.
biggrin.gif
 
Feb 19, 2004 at 3:01 AM Post #9 of 15
I don't find 10 minutes to be a long time to rip a CD, but whatever.

As far as accurate ripping in EAC goes, the problems you might encounter with Burst mode are noticeable audio glitches at certain spots; such as clicks, dropouts or "blorps". However, you really have to listen to the full song on every song that gets ripped to know whether those ar in there, because in Burst mode EAC's error indicator isn't accurate. In secure mode, if EAC tells you "no errors occurred" after ripping a disc, you can basically be confident you will not hear any problems. And if it tells you "suspicious position" you better listen to that song because it may have failed to rip it properly. In Burst mode you run the risk of having this stuff happen but having EAC tell you "no errors occurred" anyway.

Basically, it's not worth saving a couple minutes per disc. Really. Just take your time and rip your discs over the period of several days, while doing other stuff. I've re-ripped and recompressed my 200-CD collection in secure mode about 4 or 5 times now (to use increasingly better compression formats), and it hasn't ever been a big hassle.
 
Feb 19, 2004 at 8:30 AM Post #11 of 15
Quote:

Originally posted by Helloween
Eh, i tried secure mode and just found it to be entirely too slow, averaging about 5x speed for ripping, literally taking 10-15 minutes per cd...absolutely ridiculous. So i switched to burst mode and now it only takes a few mins (if that) to rip a cd using lame. So far, everything sounds fine out of my njb3 and hell, i don't plan on doing any critical listening so it doesn't bother me that much anyway and none of my cd's are scratched.


You think 10-15 minutes is long??? I remember back in the day when it took over an hour to encode a cd to mp3 because of cpu limitation.
 
Feb 19, 2004 at 9:59 PM Post #12 of 15
I want a perfect copy. I use secure mode.
Time isn't the issue, I want the best copy I can get.
 
Feb 19, 2004 at 10:01 PM Post #13 of 15
I also burn at 4X or lower as well, some people say burning at high speed is no problem, but I know from creating MANY data disks at high speed that ended up being coasters that is is a problem.
 
Feb 19, 2004 at 10:14 PM Post #14 of 15
Quote:

Originally posted by UberNewb
I also burn at 4X or lower as well, some people say burning at high speed is no problem, but I know from creating MANY data disks at high speed that ended up being coasters that is is a problem.


I can burn a disc at 52x while playing games, doing heavy drive work, etc, and not have a problem. Thank god for burn proof!

Some say however, that the best way to get the best quality from a self burned audio CD is to burn at 1x.
 
Feb 20, 2004 at 1:02 AM Post #15 of 15
This thread gave me a good scare!
I use Gentoo Gnu/Linux exclusively, so I'd never even heard of EAC. And I've ripped hundreds of my own cds to flac with the frontend "grip" which uses a program called cdparanoia to do the ripping.
I've never heard any indication that my rips weren't good. I mostly rip cds as I buy them- and I buy a lot of cds- mostly IDM, post rock, and odd experimental stuff which often includes pops and clicks and digital noise. So I was worried
etysmile.gif

But I shouldn't have been. With a name like cdparanoia? By default it does all sorts of error correction I'd know if it ran into any problems.
Chalk another one up for Team GNU
 

Users who are viewing this thread

Back
Top