Sucess rate on ripping collection

Not open for further replies.


Always At Your Service
Bryan : Dastardly scoundrels. Gadzooks.

Arise! Arise! Dudley Doright and Under Dog to the rescue. Swiftly, make haste.

Ken Petersen

Account Closed
I drop into this forum (this thread in particular) to obtain research on "Compromised file qualities” as a minor subordinate claim to building the point of a “P2P downloading of music is bad” thesis.

I also sit outside like a water-soaked puppy in a rainstorm somewhat wishing I *could* go digital…

Then I read Cap’s and Bryan’s little exchange and think, “Great… This is what I have to look forward to?”

Ken Petersen

Account Closed
At least I can admit the thesis is fun but horrible.


_______X________ is "good" or "bad" (pick one).

Topic guidelines:
Topic may not be "legal in nature"
Topic may not possess any "Well, duh!" traits.
Content must reveal a "choice of side," no fence-sitting allowed.
Presentation, must not coherce, but persuade.

James Kane

New Member
Back to the original topic.

I've found it's not so much the software but the hardware being used that determines the outcome of reading a disc. From time to time I'll find a disc that one drive will refuse to rip accurately, but if I put it on another machine with the same ripping software everything works fine. In many of these cases the original disc appears to be in perfect condition.

Basically if you're getting a lot of bad reads, you may be better served replacing your optical drive. Unless you have one of the cheaper $400 Dell specials... then it may be time to upgrade everything.


New Member
Okay. This is how I do it.

1. First, insert the Cd :lol:

2. Adjust the burn speed. I generally burn anywhere from 4x - 2x

3. Make the minor adjustments (fade out the ends, eliminate the
lead {Blank Space})

If anyone remembers one of my old threads, you'll know I only use
.wav files.

In the event, I need to increase the gain, I will. However, I rarely
do (I love Dynamic Headroom). considering I don't want the added
compression, when the peak exceeds the 0 dB level.

I don't use EAC or Audiograbber. I use Wavelab made by Cubase.

All in all burning at slower speeds prevents errors than trying to burn
at top speeds.

You should always have your burning software operating only, when
making the transformation. Remember, multiple tasks creates more
confusion, and, sucks up your system resources.

Best Regards,


Active Member
I think I may just start back a square one again. Just doesn't seem worth the risk of leaving things as they are in case I run across another bad file while at an event. Oh well...



New Member
In 3 years, all I did was run across one bad file at an event. That was the file with the 'ticking' through it. Came home, realized there was a smudge on the disc, cleaned the surface of the CD and re-ripped the song.


Active Member
That's good to hear John. I think I'll continue ripping using the "new" 10x speed discussed here and leave everything I've already ripped as is. That'll give me time to think about whether to re-rip or not.

Thanks JWG!



New Member
I have to agree with John here. Ive ripped over 10k tracks in the past 3 years and have come across only a few that have had the ticking noise, this was due to a scratched or dirty disk.

I use Audiograbber and rip at 10x with no problems.

SoftJock Rick

ProDJ Sponsor
I've followed this thread with interest, and thought I'd share some info, since I deal with AG everyday, and end up doing quite a bit of support for it (and it's not even my program). Besides, it's Saturday, and I don't feel like working anymore :) .

I've literally ripped hundreds of thousands of tracks with AG over the years since it's been around. I do my collection over and over again for various testing purposes of my software, plus I always find some new thing to do with my music that requires a re-rip, and sometimes, I just get bored.

I use the default speed now always. There are a number of reasons, but mainly because I've disassembled most of the code, and realize it defaults that way most of the time anyway -- basically the combo of AG -> OS -> BIOS -> Storage calls, result in the drive sending back what it can, when it can (remember, this is a messaging based OS). Appears to be a non-issue, although it may help to slow it down if you have some hardware problems.

I also rip exclusively to WAV first, then encode to MP3 if needed. There are other reasons besides speed of rip for doing this; 1) You can double check the checksums; 2) Your processor will use roughly <= 10% of it's utilization ripping to WAV, while the conversion to MP3 will usually range from 80-100% (more prone to error if something else sends Win a message). This equates to - You can successfully rip to WAV even while surfing the net, but you should probably not do the conversion to MP3 while doing anything else.

There are also a couple of features in AG that hardly anybody seems to use, like calculate checksum, compare files to name a couple. Jackie gave us all the tools to do a successful rip, and double check anything if need be.

If you get the same checksum each time you rip the suspect song, then the WAV is an exact copy of the data read off the disc. If you get a different checksum, rerip it to WAV again. If you see an X in the checksum field, you probably have a problem, and the checksum field is no longer a valid check to use. If the error comes after that, it probably occurred in the MP3 conversion, so reconvert it to MP3.

Enough technical details, where's the beer and soapbox :)

[Soap Box On]

Any song you plan to play in front of an audience, should be auditioned in it's entirety before playing it before said audience, IMHO. If you were playing a guitar, you would practice first, right?

Now, I know you're saying, I don't have time to listen to 50,000 tracks right? That's ok, because you are not going to play 50,000 tracks. I have a firm belief that no DJ has the need to carry that many tracks, nor burden their computer with that many taking up processing time for searches and sorts (that is both a personal and professional opinion).

I rip all songs on my CD's (it's faster), but I only transfer the ones I might use to the gig computer, and they are listened to before playing, so no surprises. I just consider it part of the job when DJ'ing (with or without a PC). When I used vinyl and CD's, I listened to every track before I played them then as well (not the whole album or CD, just the tracks I might play).

It only seems fair that you should give the same (or more) consideration to the files on the computer, since they go through a process chain before reaching the audience's ears, and the benefits derived from using a computer, are well worth the effort of listening to, and categorizing your files properly, and re-ripping them if need be...

[/Soap Box On]

Jim Weisz

ProDJ Sponsor
Staff member
SoftJock Rick said:
I use the default speed now always. There are a number of reasons, but mainly because I've disassembled most of the code, and realize it defaults that way most of the time anyway -- basically the combo of AG -> OS -> BIOS -> Storage calls, result in the drive sending back what it can, when it can (remember, this is a messaging based OS). Appears to be a non-issue, although it may help to slow it down if you have some hardware problems.
I've always used default speed too. On my old computer that was between 15-20x. Just ripped my first disc with new computer and most tracks were between 35-40x. I like that it's going so fast but it almost seems too fast. Not sure I need to go all the way down to 10x but might shoot for 20-25. I just checked several of the tracks (ripping to WAV) and all sound great but just don't want to take any chances.


New Member
I rip at max speed all the time (up to 48x). If there is an error, EAC will detect them and tell me about them.

4 years, not one problem


Active Member
Since my "default" speed is usually around 13x-14x, slowing it down to 10x shouldn't affect me too much. Maybe I just got lucky and found the only 2 mp3s with blips on them!



New Member
I started using audio grab- (good software).
I run BPM STUDIO and have been using the built in ripper. I have ripped about 40 gig of mp3's - Only one bad file. (Hint - don't do anything else will ripping) although I ripped one song once while preforming with BPM STUDIO.
Average rip time for one song, lest than 15 seconds wave to mp3. BPM puts the song where I want it then makes a list of new ripped music.
BPM does the tag edits. It will also edit silence at the beginning and end of the song, but I prefer using cool edit for that.
Works for me.



New Member
Ripping CD's

Everybody has they're personal favorites. I'm a TRAKTOR/PCDJ Red 5.3 type of guy. Even though I've converted to being a TRAKTOR guy for performances, for ripping discs, PCDJ Red v5.3 is still the best one that I've found. It takes about 10-15 minutes per disc and I rarely have a problem.

Here's where you get your LEGAL copy---

here's where to find the guide for ripping with PCDJ Red 5.3--

I've purchased loaded and installed PCDJ RED 5.5, BPM Studio, PCDJ-FX and Traktor. All of them except TRAKTOR have a ripper.

Out of all of them, PCDJ Red has proven flawless and easiest --FOR ME. It's old reliable, and I burn thousands of songs each week.

Traktor 2.5 and Traktor 3.0 will analyze each mp3 and give a graphic representation of the file so you can tell it's screwed up or cool just by glancing at it.

Traktor 3.0 analyzes automatically every time you play a song.
If you build a playlist in advance you can find any "bad files" at home before you deaort for your event.

Minimum System Requirements for PCDJ Red 5.3:
OS: Windows95/98/2000 and XP
Processor:pII or AMD 350mhz
RAM: 64mb
Video: 8mb
Sound: DirectSound Compatible


New Member
RE: Audiograbber

Thank y'all for this interesting and educational topic.

Just installed Audiograbber and am ripping my first CD now... I was all happy, then looked and saw the blue screen of death... hmm... I know it did not convert the last track on the CD, and neither did Windows Media Player when I first converted using that program...


New Member

The last known stable version of PCDJ Red before VRM was 5.2. 5.3 was kinda buggy. And, I've NEVER heard of PCDJ Red 5.5.

10-15 minutes per disc - your rip speed must be in the neighborhood of 3x-4x for that length of time. Usually 10x is more than sufficient.


New Member
Win2K and PCDJ 5.3 for ripping is fast and relaible

The PCDJ 5.5 was a typo I always mean 5.3 and I'ven personally never had any problems. I admit that it only ripps with windows 2000---not XP--but I have a machine set up for ripping for that purpose only. I get the TM Century A, B, C, D and latin each week for myself so I'm constantly ripping new stuff as well as my back catalog stuff. Anyway, I found PCDJ 5.0 to be super buggy and 5.3 super reliable. I don't use 5.3 to actually DJ with, I use Traktor 3.0 for performances. I only use PCDJ 5.3 to ripp with. The 10 minute window is not just ripping time only- it's typing all the information for ID tags AND ripping too, 10 minutes per CD, it's easy and fast with PCDJ 5.3 and Win2K.
Not open for further replies.