or Connect
Head-Fi.org › Forums › Equipment Forums › Computer Audio › Using 2+ drives to rip CDs on Windows
New Posts  All Forums:Forum Nav:

Using 2+ drives to rip CDs on Windows

post #1 of 5
Thread Starter 

Anyone using 2+ drives to rip CDs at the same time on a Windows machine? If so, what ripper are you using?

 

Ideally, I'd like to just use 3-4 drives and just have it do the following automatically when I insert a disc:

  • Auto-detect gaps
  • Match CD via MusicBrainz
  • Generate CUE sheet
  • Rip all audio tracks to WAV
  • Perform compression/tagging automatically
  • Eject CD

 

This way, I wouldn't even have to look at a monitor. Just keep feeding it discs whenever I happen to pass by the machine.

 

Right now, with EAC, I have to do this via multiple instances of EAC:

  • hope that it matches something via CDDB
  • Click No twice for Cover Images/Lyrics (Haven't figure out how to disable this)
  • Hit F4 to detect gaps
  • Create noncomplaint CUE Sheet
  • SHIFT-F6 to copy tracks
  • Click OK when it's done
  • Eject CD (does this automatically)

 

I then do a batch pass at the end to move things into MusicBrainz and then use Foorbar for a DR scan, and a ReplayGain scan.

 

Somewhat labor intensive for a few hundred CDs.

 

A few months back I started the process of ripping my entire CD collection after buying a handful of drives to plug into my HTPC, figuring that my time was worth more than the incremental cost of a few extra DVD-RW drives. While the machine clearly has enough resources (CPU, RAM, I/O bandwidth, etc) to handle multiple discs at once, I've noticed that EAC seems to sporadically barf (1 out of 10 discs?) during the FLAC compression stage. In particular it's almost as if the algorithm used to generate temporary filenames has a bug that causes it to use the same filename for files being extracted from 2 different EAC instances and it gets confused. Unfortunately, either my version of Flac doesn't return a proper error code or EAC doesn't actually respect the returned flag. So in addition to not generating a good FLAC file, it ends up deleting the WAV file when this happens, so I have to go back and re-extract it again. The alternative would be to leave the .WAV files around to avoid re-extraction, but then I'd still have to re-run the compression. Either way, I would prefer that everything was a 1-pass operation.

 

Miscellaneous constraints:

  • I'm only looking at freeware, so please don't suggest dBpoweramp.
  • Ideally I'd like to move away from AccurateRip and use MusicBrainz since it's non-commercial.
post #2 of 5
Have you tried Cue ripper from the cuetools package (it has musicbrainz support)?

Why rip all tracks to WAV first and then compress and tag when you can save time and rip directly to FLAC and either let the ripper tag or use an external tagger.

Also to get around the file name clash make sure each EAC instance is ripping in to a separate folder.
Edited by A_Man_Eating_Duck - 6/5/14 at 1:07am
post #3 of 5
Thread Starter 
Quote:
Originally Posted by A_Man_Eating_Duck View Post

Have you tried Cue ripper from the cuetools package (it has musicbrainz support)?

 

Not yet, that's what's on my list, but I was hoping someone else had tried it already.

 

Quote:

Originally Posted by A_Man_Eating_Duck View Post

Why rip all tracks to WAV first and then compress and tag when you can save time and rip directly to FLAC and either let the ripper tag or use an external tagger.

Also to get around the file name clash make sure each EAC instance is ripping in to a separate folder.
 

That's just how pretty much any ripper works. Even if you tell it to use a particular kind of compression, it rips a WAV first, then kicks off compression on the output WAV file.

 

The name problem seems to occur even if I'm ripping things to two completely separate folders. My general process is to use whatever comes back in CDDB and multi-disc albums usually have "Disc 1" or "Disc 2" in the title. Still happens even if they are 2 completely separate folders. I don't think this is just a filesystem problem. I think it's an EAC problem and it will probably just get worse if I start ripping 3-4 at a time.

post #4 of 5
Quote:
Originally Posted by BeyerMonster View Post

That's just how pretty much any ripper works. Even if you tell it to use a particular kind of compression, it rips a WAV first, then kicks off compression on the output WAV file.
Sorry I was confusing your method with the rip as WAV and then use another tool to do the FLAC encoding.

Using Cueripper will encode directly in to FLAC without the need to create an intermediate WAV file. It's a very good tool but you can get some cryptic errors when it tries and rips some dirty CD's.
post #5 of 5
Thread Starter 
Quote:
Originally Posted by A_Man_Eating_Duck View Post
 
Quote:
Originally Posted by BeyerMonster View Post

That's just how pretty much any ripper works. Even if you tell it to use a particular kind of compression, it rips a WAV first, then kicks off compression on the output WAV file.
Sorry I was confusing your method with the rip as WAV and then use another tool to do the FLAC encoding.

Using Cueripper will encode directly in to FLAC without the need to create an intermediate WAV file. It's a very good tool but you can get some cryptic errors when it tries and rips some dirty CD's.

Thanks for the recommendation. I tried it today (sample size of 1), and it worked fine. The fact that there is a setting in the options for running multiple instances is encouraging that it's actually meant to run that way.

 

I found the output message somewhat confusing, but it basically said things look correct:

Quote:
(392/399) Accurately ripped, or (2/399) differs in 321 samples @00:54:08,
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Computer Audio
Head-Fi.org › Forums › Equipment Forums › Computer Audio › Using 2+ drives to rip CDs on Windows