Slashdot Mirror
Slashdot Asks: SATA DVD Drives That Don't Suck for CD Ripping?
To work around the problem, I've temporarily yanked an old Promise IDE card I had in an ancient K6-2 rig (timothy found parts of it in a dumpster even) and am using the old drive, but it's approaching a decade and was pretty heavily used. What with having lots of moving parts and a laser or three, I don't see it lasting another decade, and I'd like to have a drive usable with a bus that hasn't been deprecated for almost as long. I'd also like to avoid anything that can read/write Bluray, because the hardware implemented DRM is pretty heinous.
For those interested in the gory details of the hardware I ran cdparanoia -A on both drives: ide drive, sata drive. As you can see, the old drive is way faster, and it looks like the primary difference is that it also has a cache that works with non-linear access, but that behaves "correctly." If you own a drive you want to recommend and can analyze it with cdparanoia, I'm interested in seeing the output.
A note on software suggestions: it has to be FSF-definition Free Software, and GNU/Linux is the only operating system in my house. That basically leaves... cdparanoia. I'm a bit uptight when it comes to tagging (mostly because: once I've done this, will I ever have the stamina to re-tag? Nope), but I'm not trying to start a pirate CD factory and don't really care about getting 100% frame-accuarate rips, just error-free ones.
I work in the entertainment industry, and we have to rip about 100 albums a month at work for online promotions of various sorts. The HP DVD drives work pretty well.
Why can't I mod "-1 Idiot"?
You trust online storage more than your CDs? Are you insane?
" (I trust online storage more than optical discs that may or may not last another twenty years)" Seriously? those discs will be around far longer than those online storage companies.
Why would you care how long a drive takes to rip a CD/DVD? Do you sit and watch and wait for each one to be ripped? Are you using some strange OS that only lets you do one thing at a time? I did the same thing a few years ago. I just had a big stack next to my primary computers, and just swapped them out while I was working on them. How long each one took wasn't relevant.
I don't respond to AC's.
It worked much better... Keep it around.
I agree it's silly that newer drives don't improve things.
You might find the following list very useful. It was made by the author of Accuraterip:
http://forum.dbpoweramp.com/showthread.php?25782-CD-DVD-Drive-Accuracy-List-2012
Rip the CDs at a rate of say 10 a day, and you'll be done in 45 days. I did this years ago, and my CDs sit untouched while I make use of the FLAC and files made from the FLACs. If you buy new CDs, the longer time required is likely not a big deal as you aren't doing a huge batch.
Most new drives come with a control for the sound level, which will intentionally keep them running slower so that they don't sound like they're going to take off.
http://hektor.umcs.lublin.pl/~mikosmul/computing/tips/cd-rom-speed.html
Buy more than one ya git! Rip em in parallel not serial.
From what I remember, (I haven't been following hydrogenaudio for at least 5 years) Exact Audio Copy was the ripper of choice. Paranoia would do things that were shown to be not necessary, and with accuraterip, you don't have to be paranoid about anything. Have you tested the ripping times for each program?
Buy a collection of USB CD roms, so you can rip many discs at once. Then you aren't pulling apart your computer to add these drives, and they have a lifetime beyond your current computer.
Who uses cd's anymore...
Sounds like you're far too anal and you might as well just start reading the bits 1 by 1 with a microscope.
Raw wavs.
Plextors are generally regarded as the fastest/most accurate although they really don't make them anymore (they do but they are just rebranded Lite-Ons).
Heres a pretty good chart comparing drive accuracy: http://forum.dbpoweramp.com/showthread.php?25782-CD-DVD-Drive-Accuracy-List-2012
What ever you get, get two or more. Having multiple decent speed drives will be much faster than just having one really fast drive. Also, pay a neighbor kid or some kid related to you to rip your cds. Show them how to do it and setup some sort of batch ripping script so all them have to do is just swap discs for you. Child labor is much better.
If you can't find a drive that you like, you might want to consider using EAC to do the ripping. With EAC, you can put it in "burst" mode and disable all the error correction algorithms which are what cause the caching issues. EAC will still use AccurateRip in burst mode to verify that the rips were good. So you'll know which tracks have a problem and need to be reripped with error correction enabled.
IIRC, my el-cheapo Memorex SATA drive can do a "burst-mode" rip in less than four minutes.
1. Stop using cdparanoia - it isn't very good, at all. It tests poorly, we're sad to say. The software you actually want to use is Exact Audio Copy. You want to use Secure Mode with NO C2, accurate stream, disable cache. Yes, we said DISABLE cache. Trust us on this. We checked. Very very extensively. Yes, we know it runs slowly: that is because it actually does need to physically read every sector at the very least twice - that's the POINT. Sadly EAC isn't open-source (and despite many years passing, there still is no open-source software that does a Secure Mode), and runs under Windows (although it will function in a virtual machine if the drive is passed through well, such as VMware).
2. Use AccurateRip in that if you can. Matching the read offset is strongly-recommended-to-required - ideally, find one of the few drives that can overread into lead-in AND lead-out. You won't hear it on many discs, until you come across That One Disc that has the track transitions exactly just so and thoroughly audible if they're off (despite the Red Book standard having a truly ridiculous amount of defined leeway either way).
3. Hardware time.
a) Best case scenario: The Plextor Premium, which does have a (rare) SATA version as well as the IDE version. That is the best CD drive ever made, and it is the highest quality DAE drive ever made, by far. That, and the above software (especially if you set the drive to "first session mode", or use AnyDVD), will rip clean through any "Copy Controlled" discs you may have in your collection too, by virtue of sheer quality. Be warned: that drive is no longer made, and REALLY sought-after. It will cost hundreds of dollars to find one new, and any used ones will be totally clapped-out by a lifetime of ripping and burning discs in professional CD-R duplication towers, or poorly refurbished.
b) Can't get that? The Plextor PX-716SA will do the best job of any DVD drive. If you can find one easily, grab it.
c) OK, plan C: something else. You'll need to check up on DAE quality. Check the offset tables on AccurateRip, which might give you a few clues. Lite-ON are way, way more reasonably priced, and some models work well at this; check them. So do a few LG drives. If you get lucky, you may have some good hardware already. Be warned, however, that you may NEED AnyDVD to rip any "Copy Controlled" discs that you may have correctly if you don't use one of the few drives that are out there that can do the job.
4. Destination: Rip it to FLAC --best. Really, you're making an archival copy, and you are probably talking about terabytes of storage to play with - why WOULDN'T you use a lossless codec that is suitable for archival, well-known, free and open source, contains an internal MD5 checksum, supported by damn near every toolchain, supports all the metadata you need, and is absolutely guaranteed to not leave you with any possible transcoding issues if you ever want to transcode to a lossy codec for portable or streaming usage at any bitrate in any codec you want in the future?
5. No online storage is even close to trustworthy enough for archival purposes. By all means, if you want, for convenience: but buy a couple of hard drives and put it on there too, and put them away. OK, they might not work after a long time on the shelf - that is a risk. But it is still A safety-net that is less likely to fail than an online storage company which bears a multitude of risks (many of them legal ones, if they are storing people's music files for them in any useful manner).
You said you're ripping to FLAC this time, i.e. lossless. Once you're done ripping, will you ever have to re-rip from these discs en-masse again? Probably not, so the longevity of your magic drive is actually not an issue.
If you're happy with the performance of the optical drive from your old rig, why don't you just install that drive in your new rig and continue using it?
Save youself the hassle and download from online "sources". I don't think it's even illegal in most places, if you own the CD.
Just throwing some other approaches out there - I'm sure people will point to SATA drives that rip plenty fast (myce.com is sure to have some recommendations, for what it's worth).
Alternative A: Why just 1 drive? Get multiple. They're cheap (sub-$15 for an external CD drive that'll happily do DVD as well. And burn them. Sell them on when you're done.)
Alternative B: Better yet, since you have so many discs, get a (semi-)automatic CD changer system. Sit back, let it rip a bunch at a time. Sell system on when done.
Alternative C: Why even bother with it yourself at all? Go find a CD ripping service. I have no experience with these guys - http://musicshifter.com/ - but at less than $1/CD and the option to have them rip lossless (yes, including FLAC) and send them a drive to put it on, perhaps it's worth it to let them deal with it and use your time and effort elsewhere. I know it's not much effort (I just digitized every single Stargate DVD between working on things, just swapping out the DVDs - each taking about half an hour), but the option is out there anyway.
Alternative D: Piracy! Well, it's not really piracy since you already have the CDs. There's some sites out there that will happily let you submit your CD's code (either the simple code used by e.g. Windows 95's media player or a more complex one) and spit out links for getting digitized versions. I'll let you do the Googling there.
Alternative E: Buy them. Certainly a lot (understatement, seriously) more expensive than the other options, but on the up side you should get perfect metadata, album art, etc. included.
and over load the slow usb bus
firewire and e-sata are better then that.
The problem isn't the drive speed, but the amount of manual labor involved in placing hundreds of drives, sorting out the ones that have failed to be retried, and then restocking them. There are multiple optical disk loaders out there, but they aren't intended for transient use and usually require a painful data entry step at the beginning before the drive can locate them.
I have a similar problem, but for a collection of over a thousand mixed-media items. What I've settled on is building a three-spindle set and using a robotic arm with a vaccum sucker to life each item off the spindle and set it into the drive. The spindles are incoming, complete, and failed. The arm is controlled by a simple microcontroller and a couple of sensors to track position and success of each pickup, and connected by USB to custom software. The software alarms if there's a failure, and stepper motors for precise location. The arm "free-falls" from the top of the platter (on a gas piston to reduce contact shock) and a pressure sensor to detect when contact with the next item has been made. It also controls the drive eject/load and the ripping software is triggered using auto-it scripts. Any failure is detected the same way, by watching window titles, and then signalling pickup of the optical media after. There is also a webcam placed directly over the optical drive insert with a bright LED, and a picture is taken of the 'top' of each inserted media at high quality (in case the title is only printed on the inner track). The picture is placed in the same directory as the ripped ISO, and each directory labelled sequentially.
All of this makes post-processing a lot easier; The system can be loaded once a day (before I go to work), and when I get home, it will have ripped about 13 bluray discs. It only takes me a few minutes to rename each ISO to match the disk title from the image, after which it's placed in the pending folder which the ripper autoloads periodically.
But this setup requires knowledge of basic programming and some basic understanding of how robotic tasks are performed; And a significant understanding of electronics and assembly. Any of the homebrew microprocessor kits out there can perform the interface tasks as long as they have GPIO pins. Arduino, for example, has pre-built shields for controlling stepper motors to further simplify this process. The hardest part for me was building the actual robot arm; For that, I looked to how 3D printers are assembled as they've largely solved the problem of using stepper motors and precise placement within a 3D space without significant feedback.
Just make sure your robot's "sucker" can reliably release the optical media and not drag it; it only takes a little bit of moisture or stickiness to lift the optical media slightly and misposition it in the tray, and once the LOAD command is sent, your drive will eat the disc, permanently damaging it. It's also difficult to detect this in software -- the only indication of fault will be an unreadable disk and drive being unresponsive to load/eject commands. Make sure your apparatus fails safe, and I suggest testing all possible failure modes with throw-away media before using on production material.
#fuckbeta #iamslashdot #dicemustdie
I know you said SATA, but I still use my SCSI Plextor drives under Linux for ripping. They're fast and accurate.
A pair of them in a low power purpose built machine, with a local copy of the CDDB, will do a disc every 30 seconds or so.
They're even cheap on ebay.
RIP it good!
I know it's a bit late now, but instead of voiding the warranty on your new shiny, you could've just gotten an IDE to USB adapter. A raw CDRom drive may not be the prettiest thing sitting on the desk, but once you get all your CDs ripped, you won't be needing it again until you buy a new CD, if even then. 15 min. to rip a CD isn't much when you only have one. You can rip that out while catching up on the days /. and email.
--- Keep the choice with the user..
I do a lot of movement onto and off of compact flash media and such. I recently got a USB 3.0 card reader and woo-doggy is it faster.
Similarly I would expect that paying the tiny extra sum for 3.0 drives would let you stack a couple CD/DVD read/write devices onto your system a lot more efficently.
You really can bump your head into the 2.0 data limits pretty easily at times.
Innocent people shouldn't be forced to pay for inferior software development.
--"Code Complete" Microsoft Press
The OP didn't mention why the need to re-rip and why he's going with FLAC (other than the obvious FLAC benefits and a concern over media longevity), but if he has the CDs and is concerned about the time to rip, go lossy! And if so I'll add one more alternative that will save even more time:
Alternative F: Purchase one year of iTunes Match ($25 US) and you probably won't need to rip most of your CDs at all. Depending on what you have now the downloaded iTunes versions may be of better quality. I'm making the assumption he doesn't already have them in FLAC format because if so why re-rip?
Never heard of it.
Years ago when I had to rip all of my CDs to MP3s, I had about 500 to go through. I was a Linux user, so take this with a grain of salt if you're not one, but I simply went to the local university surplus yard, picked up 12 2x SCSI CDs for about $5 each, and connected them to some spare SCSI adapters and powered them with junk PC power supplies and 4-pin Y-cables. I'm sure you could cook up something similar these days with SATA or even USB and cheap eBay bare-board SATA->USB adapters. You could probably piece together at least a 4-6 drive solution for less than $100.
Then, I wrote a shell script that leveraged some basic shell tools. I don't remember what they were (I haven't done this for years), but one was cddb-something (queried online CD databases) and of course cdparanoia and lame and I think one called id3tag.
I scripted things up with the following logic, run on all drives simultaneously:
While (forever):
Poll drive for inserted CD.
If one is in, query cddb, save names in shell variables.
Rip using cdparanoia and default filenames, encode with lame.
Rename all files using track names in shell variables and folder using album and artist in shell variables.
Use id3tag to tag MP3 files according to file and folder names.
Eject disc.
End while.
Ran this on all 12 drives simultaneously in a terminal. Whenever a tray popped out, I took out the CD that had just been ripped and tossed it in the "done, recycle plastic medium" pile, and then stuck in the next CD in the queue and closed the tray.
With all drives cranking, it took no more than a couple days' intermittent CD-inserting (in the midst of doing whatever else I was working on--browsing the web, writing, studying, etc.) to move through the queue. And then I was done.
When I was done, I stuck all of the basically valueless drives in the garage, and I think years later they ended up at the dump.
If I'd had to nurse along a single drive, I don't think I'd be done to this day. Too big a PITA. 12 slow drives with an automated script > 1 fast drive by hand.
STOP . AMERICA . NOW
Using a CD-ripper is so 1990s. What you want to do is buy a good quality scanner and scan your CDs using high-resolution mode -- should take about 20 seconds per disk. Then use any of the usual conversion programs to convert the scanned images into whatever audio format you prefer.
Never had a single problem with this drive. Available here: http://www.newegg.com/Product/Product.aspx?Item=N82E16827135204
Seek/read timing:
[53:27.17]: 18ms seek, 0.30ms/sec read [45.0x]
[50:00.32]: 17ms seek, 0.30ms/sec read [45.0x]
[40:00.32]: 20ms seek, 0.33ms/sec read [40.0x]
[30:00.32]: 16ms seek, 0.37ms/sec read [36.0x]
[20:00.32]: 21ms seek, 0.41ms/sec read [32.7x]
[10:00.32]: 25ms seek, 0.48ms/sec read [27.7x]
[00:00.32]: 50ms seek, 0.63ms/sec read [21.2x]
I'd suggest dBpoweramp. The dev (Spoon) is a frequenter over at the Hydrogen Audio forums and knows his stuff. Although you'll have to fork out some cash for the software, it is at least as accurate as EAC and much faster on undamaged discs. Try it yourself and see (there's a trial), and if you're not happy then you've still got EAC...
I have a cheap, bog standard LG brand SATA drive that seems to do OK. I don't rip audio CDs very often, but last time I did (I just do "cdparanoia -B") it didn't seem to take long.
Here's my output of "cdparanoia -A" (I did this three times with similar result)
This is on Linux 3.6.5 on x86_64.
grogan@getstuffed:~$ cdparanoia -A
cdparanoia III release 10.2 (September 11, 2008)
Using cdda library version: 10.2 /dev/cdrom for cdrom... /dev/cdrom for SCSI/MMC interface /dev/sr0
Using paranoia library version: 10.2
Checking
Testing
SG_IO device:
CDROM model sensed sensed: HL-DT-ST DVDRAM GH24LS50 YP01
Checking for SCSI emulation...
Drive is ATAPI (using SG_IO host adaptor emulation)
Checking for MMC style command set...
Drive is MMC style
DMA scatter/gather table entries: 1
table entry size: 524288 bytes
maximum theoretical transfer: 222 sectors
Setting default read size to 27 sectors (63504 bytes).
Verifying CDDA command set...
Expected command set reads OK.
Attempting to set cdrom to full speed...
drive returned OK.
=================== Checking drive cache/timing behavior ===================
Seek/read timing:
[74:21.35]: 62ms seek, 0.32ms/sec read [41.8x]
[70:00.32]: 56ms seek, 0.32ms/sec read [41.5x]
[60:00.32]: 57ms seek, 0.35ms/sec read [37.9x]
[50:00.32]: 61ms seek, 0.37ms/sec read [35.7x]
[40:00.32]: 58ms seek, 0.41ms/sec read [32.8x]
[30:00.32]: 61ms seek, 0.45ms/sec read [29.7x]
[20:00.32]: 62ms seek, 0.51ms/sec read [26.2x]
[10:00.32]: 73ms seek, 0.58ms/sec read [22.9x]
[00:00.32]: 71ms seek, 0.74ms/sec read [18.1x]
Analyzing cache behavior...
Approximate random access cache size: 16 sector(s)
Drive cache tests as contiguous
Drive readahead past read cursor: 234 sector(s)
Cache tail cursor tied to read cursor
Cache tail granularity: 1 sector(s)
Cache read speed: 0.14ms/sector [94x]
Access speed after backseek: 0.71ms/sector [18x]
Backseek flushes the cache as expected
Drive tests OK with Paranoia.
Get multiple drives and rip multiple discs at the same time.
Or if that's not possible, get multiple machines, and rip multiple discs at the same time that way.
Since this is just a single project to get through all your CDs as quickly as possible, forget about what's logical long-term.
There's been a trend on Slashdot to shoot down questions like this without due consideration of what the submitter is asking, or just posting some obvious answers and consider the issue resolved. It was really nice to see this thread put forth a lot of information from the community. I didn't realize that there were 1) issues with SATA drives having issues on things like this 2) that there were people who cared about this kind of thing enough to have done the homework and the research behind it. It's called to my attention that there's a sub-genre of people for whom this matters, a lot. I've ripped scores of CDs in the last decade, but never paid enough mind to have it as more than a rarely-used utility. Thanks for the information, and you go, geeks =)!
I'm using a SATA connected Hitachi GH15F and cdparanoia. This drive, as far as I can tell, is, or was, an extemely common OEM item.
It works absolutely fine with cdparanoia and, if correct offset is set, gives identical results to EAC in Windows (you need cdparanoia 10.2 or newer; older versions had real deficiencies). I checked this with multiple comparisons where I ripped various CDs, some in poor condition, both with cdparanoia in Debian and with EAC in XP and then md5 hashed the raw pcm output: non-different. I also did rips on different drives on different PCs and achieved bit identical results on those drives which passed cdparanoia -A. Obviously this wasn't a huge dataset and doesn't prove anything but it was good enough for me to stop caring any further.
Here is the output of cdparanoia -A:
CDROM model sensed sensed: HL-DT-ST DVDRAM GH15F EG00
Checking for SCSI emulation...
Drive is ATAPI (using SG_IO host adaptor emulation)
Checking for MMC style command set...
Drive is MMC style
DMA scatter/gather table entries: 167
table entry size: 524288 bytes
maximum theoretical transfer: 37074 sectors
Setting default read size to 27 sectors (63504 bytes).
Verifying CDDA command set...
Expected command set reads OK.
Attempting to set cdrom to full speed...
drive returned OK.
=================== Checking drive cache/timing behavior ===================
Seek/read timing:
[47:10.36]: 55ms seek, 0.36ms/sec read [37.4x]
[40:00.33]: 61ms seek, 0.39ms/sec read [34.6x]
[30:00.33]: 51ms seek, 0.42ms/sec read [31.9x]
[20:00.33]: 51ms seek, 0.48ms/sec read [27.7x]
[10:00.33]: 63ms seek, 0.58ms/sec read [23.1x]
[00:00.33]: 66ms seek, 0.74ms/sec read [18.0x]
Analyzing cache behavior...
Approximate random access cache size: 16 sector(s)
Drive cache tests as contiguous
Drive readahead past read cursor: 234 sector(s)
Cache tail cursor tied to read cursor
Cache tail granularity: 1 sector(s)
Cache read speed: 0.16ms/sector [85x]
Access speed after backseek: 0.71ms/sector [18x]
Backseek flushes the cache as expected
Drive tests OK with Paranoia.
As you can see it isn't going to be quite as fast as your old IDE drive but it isn't exactly slow either.
You can safely ignore fetishists who feel EAC is magically unique and that cdparanoia can't do secure ripping. It can, as long as the drive passes the cdparanoia -A test. If you feel the need to compare your rips with rips made by properly configured EAC or dbpoweramp or similar then you need to set the offset correctly.
Almost all the cdparanoia GUI's ignore the offset and don't allow the user to set it, so their rips will have a different checksum than an offset corrected rip by other tools. This doesn't have any bearing on the quality of the rip, only on the ability to compare it. It hasn't done much for cdparanoia's reputation but if you use it with a fully configurable command line front end such as ripit or abcde, or just by itself, you can get 100% secure rips equally good as those produced by magic tools with proprietary voodoo and vociferous fanboys.
ripit is a perl script front end to cdparanoia, it will:
"do the following without user intervention:
getting the audio
http://www.cdrinfo.com/Sections/Reviews/Home.aspx
http://www.myce.com/review/
I have an ihas 324, performs well with EAC. See reviews at above sites.
I have five LG brand USB drives which I found were much faster than IDE for BURNING. They may also be much faster for ripping. I use a little shell script which keeps them busy. All I do is swap disks once the job is started, I don't touch the keyboard or mouse.
Just wait two weeks, you'll be able to 3D print a CD grabbing robot arm to do it all for you. Print out a beer first.
Asus Z8NR-D12 = 14sata ports.
Okay it will cost few bucks but it's not all that much after all.
I've done a lot of work on streamlining my own ripping process (I've got well over 900 CDs to be ripped and tagged) and in the process, I got involved in helping out with developing rubyripper, a wrapper for cdparanoia. In the process, I've learned a lot about doing accurate rips and figuring out the various intricacies of the CD format. One of the things I observed was the relatively slow speed of ripping on my LG Blu-ray drive: it behaved exactly like you described: It would take 15 minutes to rip something (effectively ripping at 2x, 4x at BEST).
Now these drives do have something called "RipLock" to limit the ripping speed of DVDs and Blu-Rays, but this feature ostensibly doesn't affect CD ripping. What I eventually learned, however, is that the LG/Hitachi (HL-ST-DT) drives which make up the majority of DVD drives out on the market today actually do not have a firmware which plays well with the way that cdparanoia does its ripping and error checking. It turns out that HL-ST-DT drives actually read at a slower speed until they have read enough sequential sectors (about 30 seconds of audio), at which point they will actually speed up to full speed and stay at that speed.
Thus, my solution to the slow-ripping problem was to actually use cdda2wav in non-paranoia mode (so as to read sequential sectors) to read the first 30 seconds of the CD audio so as to warm up the drive speed. Once this is done, I can then run cdparanoia as before, and actually can rip at a reasonable rate.
Of course this isn't to say that the HL-ST-DT drives are very good. They've got a pretty big sample offset (+667) and actually have a pretty bad successful rip rate (closer to 90% instead of 97 or 98%). The best investment I've made so far is to buy a Plextor PX-716UF, which I use to rerip CDs that don't rip right on the HL-ST-DT drive. By doing this, I've probably managed to eliminate 4 out of every 5 "bad" rips; the only remaining "bad" rips are from obviously physically damaged discs (cracks, pitting, etc.), which I consider a pretty good hit rate. Of course the only downside of these drives is that they don't play well with the DVD-side of dual-discs.
Yep, you heard me right: old Plextor drives STILL can't be beat in rip quality with practically any drive out today. (But make sure you get an old one, not one of the newer ones that's just a rebranded Hitachi that claims to be a Plextor. Basically, any Plextor with a rip offset of +30 is good, but you might also want to refer to the Plextors on this list)
Sometimes the hardware isn't that terrible, it's the stupid ass firmware installed on the hardware that cripples it. Anyhow, it's not like most manufacturers want to do that - but rather some assholes out there have to ruin things for everybody.
This might be the place to go to find your answers...
rpc1.org
This therefore excuses the guys comment that he makes a valid point as i also have and get modded to hell and bad karma's to hell?
NO really i end up logging out so i can make 2 more posts before having to go away for a day....
the sites done for period.
Have a nice day , ya know instead of banning those MS jerks you allow them to gang up and mod everyone worthy to leave , that worked out well.
AccurateRip is a database that stores CD checksums submitted by users all over the world. Whenever someone does a rip using software supporting AccurateRip, the checksum will be calculated and compared with the checksum stored in the database. If it matches, you know your rip is good. Last I looked into this, both EAC and dbPowerAmp support AccurateRip.
I have been using my BD-RW drive, a LG HL-DT-ST drive without any problems for ripping my CDs to FLAC. I have also used it to successfully write BDs.
-Aaron
cdparanoia -A
cdparanoia III release 10.2 (September 11, 2008)
Using cdda library version: 10.2 /dev/cdrom for cdrom... /dev/cdrom for SCSI/MMC interface /dev/sr0
Using paranoia library version: 10.2
Checking
Testing
SG_IO device:
CDROM model sensed sensed: HL-DT-ST BD-RE BH08LS20 1.00
Checking for SCSI emulation...
Drive is ATAPI (using SG_IO host adaptor emulation)
Checking for MMC style command set...
Drive is MMC style
DMA scatter/gather table entries: 1
table entry size: 524288 bytes
maximum theoretical transfer: 222 sectors
Setting default read size to 27 sectors (63504 bytes).
Verifying CDDA command set...
Expected command set reads OK.
Attempting to set cdrom to full speed...
drive returned OK.
=================== Checking drive cache/timing behavior ===================
Seek/read timing:
[29:45.68]: 75ms seek, 1.92ms/sec read [7.0x]
[20:00.00]: 87ms seek, 2.17ms/sec read [6.1x]
[10:00.00]: 86ms seek, 2.59ms/sec read [5.1x]
[00:00.00]: 126ms seek, 3.36ms/sec read [4.0x]
Analyzing cache behavior...
Approximate random access cache size: 32 sector(s)
Drive cache tests as contiguous
Drive readahead past read cursor: 218 sector(s)
Cache tail cursor tied to read cursor
Cache tail granularity: 1 sector(s)
Cache read speed: 0.09ms/sector [154x]
Access speed after backseek: 3.57ms/sector [3x]
Backseek flushes the cache as expected
Drive tests OK with Paranoia.
This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
(I switched to MacOS in 2009 and my old Linux home folder now only exists in .tar.gz files on my backup raid).
Now that I think about it, I had two "scripts," one that dumped the files as .wavs using cdparanoia and renamed them and all of that (the one that ran while loops for each drive) and a separate "script" that ran in a separate terminal and was just something like:
while true; do find /path/to/rips -name '*.wav' | while read music; do lame --r3mix "$music"; done; sleep 1; done
Or something to that effect (it's been a long time since I had to recall how lame handles command-line arguments).
Then I think I actually ran one pass at the very end of the entire ripping process, again just a command-line, not actually saved as a script, with the id3 tagger that just traversed the whole tree and tagged each track as disc name "folder" and track name "file."
It wasn't fancy. It was just to get the job done. Honestly the scripting was like three minutes; getting all of the drives in place and compiling in the extra kernel code for both controllers and creating the nodes in /dev and searching freshmeat for the tools I wanted were the bigger pains; that prep work took an afternoon, but I was determined to do it all in one weekend and be done with it.
The "main" script was less than a screenful of inelegant stuff handed off to bash.
STOP . AMERICA . NOW
I had the same problem. Windows doesn't play along nicely with multiple SATA drives sometimes. Especially if you have RAID in the mix or different types of hardware (IDE and SATA and so on). It kept having cache and access and speed issues. Eventually it started dropping the DVD drive or reporting that it was merely a CD drive. I was pulling my hair out.
Then I got an external Firewire case. Problems dropped to ZERO. I tried USB but it was too slow and it conflicted like crazy. But evidently firewire uses its own bus and controller that's separate from the rest of the idiocy (being based upon SCSI technology). I can plug it in and out and it always works. My burner is a bog-standard $30 ASUS burner. My software is happy as a clam with it. I've burned Apple, Windows, and Linux CDs as well as made bit-for-bit copies of the latter (which isn't even a recognized format by Windows). Coasters are a result of bad media if it happens.
MP3 to FLAC Converter. :)
LRN 2 SWM
Perhaps you should give Vortexbox a look. I took a customer's throw away computer ( a dell dimenison 4300) and tested vortexbox so I could rip my family's various cd collections into 1 big collection to back and store for safe keeping. A little tweaking of the configuration had me ripping in no time. With 7min being the average for audio cds. It is very nice and had I not just been using to rip cds for storage, I would have used the server aspects Vortexbox. Just keep swapping the cds out until you have run through them all :D
I tested 1 movie, and it worked fine as well. I was very impressed. Give it a shot.
A computer once beat me at chess, but it was no match for me at kick boxing. Emo Philips
Since we're talking about a manual process of inserting disks and clicking buttons, the different between five minutes and fifteen minutes can be rendered insignificant if you plug in enough drives. Since we're talking about a SATA system here, any reasonably high-end PC can easily support 6 to 10 SATA ports -- with enough channels to handle CDs certainly.
In your case, I'd focus my efforts not on finding a good ripper, but in configuring ten mediocre rippers. Your over-all speed with easily multiply.
Maybe this wouldn't work for the OP, but my first solution would be to use an IDE CD-ROM drive in an external USB enclosure if SATA CD drives are the cause of the problem. The external USB enclosures should be cheap and relatively easy to find.
As far as CD ripping, before it was faster to simply download an already ripped copy of an album vs rip it yourself, I know Plextor and Kenwood had some of the hot drives. Specifically Kenwood had a drive line called True X with claimed speeds of up to 72x I believe, and everyone that ripped music wanted one of them. If you could find one that still works, that would probably be a pretty safe bet as I don't think much of anything related to reading CDs has changed in the past 20 years.
If an external enclosure won't work, I'm sure you could probably find a SATA to IDE adapter. As I understand, the problem is with the caching mechanism in SATA drives and not with SATA itself, so this should work.
http://cdexos.sourceforge.net/
You can also use flac as an external encoder using these parameters:
--force-raw-format --endian=little --channels=2 --sign=signed --sample-rate=44100 --bps=16 -8 -V -A tukey(0,5) -o %2 -T "artist=%a" -T "title=%t" -T "album=%b" -T "date=%y" -T "tracknumber=%tn" -T "genre=%g" -
"Sadly EAC isn't open-source (and despite many years passing, there still is no open-source software that does a Secure Mode)" .net stuff ... I'm getting ready to deal with the CD ripping mess too. http://www.cuetools.net/wiki/CUERipper
Not true. CUERipper is GPL and includes Secure Mode ripping. It looks like it may be a good alternative to EAC and looks to be easier to setup. It's windows
> Stop using cdparanoia - it isn't very good, at all. It tests poorly, we're sad to say.
Really! As the author, I'd love to hear hard specifics. or maybe a bug report.
> You want to use Secure Mode with NO C2, accurate stream, disable cache.
You can't disable the cache on a SATA/PATA ATAPI drive. The whole point of cdparanoia's extensive cache analysis is to figure out a way to defeat the cache because it can't be turned off. There is no FUA bit for optical drives in ATA or MMC.
The 'accurate stream' bit is similarly useless (every manufacturer interprets it differently) and C2 information is similarly untrustworthy.
Plextors are not recommended for error free or fast ripping. They try to implement their own paranoia-like retry algorithm in firmware and do a rather bad job about it. They also lie about error correcting information (you do not get raw data, you get what the drive thinks it has successfully reconstructed). Plextors often look OK on pristine disks, but if you hit a bit error (like on just about any burned disk), you don't know what it's going to do. Plextors are, overall, among the more troublesome drives _unless_ you're using a ripper that does no retry checking (ie, NOT cdparanoia and NOT EAC). If you use iTunes, you want a Plextor. Otherwise, avoid them.
What the hell are CDs? and why would you rip them?
I had a similar sized collection of CDs and ripping them was a time consuming process. I managed to find a good number online that were FLAC and cut down the time involved a significant amount.
to give my laptop optical drive a spin which is being unused to wake it up
That's because Microsoft is Estimated to Spend $1.5 Billion on Windows 8 Marketing. $1.5 billion will buy a lot of praise from say-for-pay pundits, astroturfers and shills. There will also be a small percentage of the mainstream public that will get pulled along.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
What the fuck, how is that of any help at all? Jesus Christ.
Might as well tell him to get the music on torrents, no need to pay anything.
Has iTunes dropped DRM all together? I know last time I used them, it was kind of hit or miss if the music you were getting was DRM-free or not. I know in the past, I would sometimes have to burn the files I got off of iTunes to an audio CD, then rerip. Kinda defeats the purpose. However, I know that MANY (not all) of the songs I bought when I had an iPhone I was able to put on my Android (when I saw the light). I am sure there is probably some software out there that will convert all my iTunes tracks to MP3s, but I just haven't got around to looking.
Amazon Cloud has a similar service, although I don't think they have nearly as big of a library as itunes. Out of the 3,000 MP3s I put on my Amazon Cloud account, I think about 400 songs were upgraded.
i think both services, though, still limit to 256kbps, and Amazon is MP3 (while this works for compatability, its still an old losssy audio format). While this should be fine for most people, and more than fine enough if you are listening through earbuds, true audiophiles will probably still have issues with the fact that these are not lossless
I would rip to SSD's and then copy to HD's + 2 backup HD's.
But then I'm a novice in the area.
Mundus Vult Decipi
I ripped + encoded + tagged my entire collection with some shell scripts, just using cdda2wav to get the data. It was all auto pilot after some initial testing. IE every time the disk tray ejected I just dropped the next disk off the stack in. Sometimes I was in front of the computer doing other things, other times the display was off I was just walking past it.
I have since been listing to my collection for years on a variety of devices and never once heard an audible error I can reasonably attribute to the initial ripping/encoding. I used shorten at the time ( like I said years ago ), but have since converted to flac.
Knowing what I know about the technology I am certain the rips were not error free, most errors should have been fixed, but the unrecoverable errors must therefore be preserved. My point is it really does not impact my ability to enjoy the material though. Even if someone did have golden ears, would a few bad frames spread across several moments for audio really distract? Seems hard to believe.
I think the article poster should consider he might be solving the wrong problem. Rather than trying to get perfect rips done fast, maybe he should try to get very good rips done fast.
Repeal the 17th Amendment TODAY! Also Please Read http://www.gnu.org/philosophy/right-to-read.html
I have a large music collection, praise it.. I am also a hiptser "audiophile".. praise me.
Since I discovered Streamtuner, ripping became a total waste of time. I don't even care about losing my ripped CD collection anymore.
Excuse me, but please get off my Pennisetum Clandestinum, eh!
The OP didn't mention why the need to re-rip and why he's going with FLAC (other than the obvious FLAC benefits and a concern over media longevity), but if he has the CDs and is concerned about the time to rip, go lossy!
He did mention it, numbskull. To paraphrase and elaborate, modern cheap storage has made him not give a shit about filesize, therefore the inherent quality/size tradeoff he made when he originally ripped them no longer applies. He also explained that ripping, not encoding, was the bottleneck, which surprised exactly noone but you. The only thing switching to lossy will do is give him a pile of lossy shit with artifacts largely inaudible to humans, but deeply problematic for any further lossy re-encoding (e.g. by A2DP cans or whatever), it won't speed it up AT ALL. I/O and CPU, learn the difference.
Really, if you can't be arsed to read the summary, stfu already.
More helpful than your comment, at least :)
It's Ask Slashdot - for better or for worse, that means you're going to see diverse replies. Some more helpful, some not so much. Some on-topic, some the usual racist flamebait.
If you were expecting just drive model brands, types, numbers and diagnostic output - well, there's plenty of those answers as well. Feel free to read only those in the future :)
P.S. I'm pretty sure one of the alternatives I mentioned comes down to your suggestion ;)
stick the old drive in the slot and do the ripping... then stick the new drive back in the slot when finished...
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
Many people use EAC (Exact Audio Copy) for ripping without realizing that it has known speed issues for ripping. Try using a BD drive to rip with it. Your rips will take about an hour for one audio CD. The slow ripping speed is a known issue that has yet to be fixed. EAC is free, so you get what you pay for. I don't rip audio CDs much, but when I do I now use the free CDex which has much better times.
Just torrent the flac files and be done with it.
So, just under 10 years ago, before HD got standardized and DVDs were still the best you could get for personal video content I got a Netflix account. I abused that sucker pretty hard, and when they eventually throttled me I quit, and in doing so ended up with a binder of decrypted DVDs. Now those DVDs, while decrypted, are also of a lower quality than many of the originals since most of the original DVDs were dual layer and I was burning them to a single layer DVD-R.
That being said I had been moving around the HTPC concept for a while, used a WD TV Live system, but now I have a full fledged HTPC that I am putting my movie library on. Overall I have been very pleased with the results save for the fact of Blu-Ray integration. Given that my HTPC is hooked up to a huge 1080p TV via HDMI one would think that a Windows 7 machine should be able to easily move to the next level of tech...but no. We are in a war right now with content manufactors, hardware manufacturers, the software, and of course the DRM that is quite frankly a mess.
And I'm going to say right now I have no moral qualms about abusing whatever media I want to consume. You can call me a pirate (factually correct only in a digital context), call me a thief (factually wrong), call me whatever. Fuck you and the DRM you rode in on. The day the content manufacturers allow Fair Use and reasonable copyright lengths I will cede the high moral ground I stand on. Until then, bite me.
So back to the point. I am in the process of ripping that library to the HTPC, via Handbrake, and are using an old Sony (lols) DVD-ROM. It is actually rather good at doing its job and once I am done I plan on putting a real drive in there such that the box will be able to burn stuff as well. But for now why would I want to use up the mechanicals, and from taking apart many many many CD/DVD drives (and I have no great hope that Blu-Ray drives will be of any better quality unless I spend a grand+ for them), the gears are going to be plastic. The belts are going to be high quality rubber at best. I'm gonna burn up this old drive ripping my stuff then put in the burner when it is done.
And another aside, omg Yamaha, I had a Yamaha front loading (no tray) drive at one point. Clearly at one point a group of their engineers set out to make some kick ass CD-ROM drives and they did so with a gusto. Best drive I have had to date.
Moving parts suck. I will never forget what Google said about hard drives, they suck. When you look at them across a huge sample size...wow. But I always temper myself by thinking about ME's when I talk about rate of failure. When I run into a ME and start talking about HD failure rates they give me a rather patronizing look as if that valve they just bought for $1231232967.99 should not fail within 30s of being put under pressure. Brings me back to reality.
And finally as such we have to then look to what drives/parts are going to be best to handle a job that the OP wants? Further what is the CBA of what drives will do such a job? Is it best to get an industrial level drive that has metal gears, belts that have nylon in them, and so on? Or is it better to get 5x consumer grade drives? I've already done enough damage with this post and this thread is likely going to head off the front page so I'll leave those questions to another day.
Really, I know what I'm doing...Ohhhh, look at the shiny buttons!
I trust active storage more than optical discs that may or may not last another twenty years.
LOL. Perhaps you should examine the differences in survivability between a pressed CD and a burned CD.
How many times will you rip the same CD? Several years ago, the cost of hard drives, reached a tipping point where massive storage became cheap! At that point, all my rips became .WAV. I've re-encoded my collection twice since making that decision and on both occasions, it was a completely painless process because I simply pointed a script at the .WAV archives.
FLAC will fall out of favor soon enough and you'll be re-ripping again. Enjoy.
(Argh, I just lost a 20-paragraph post because I chose to change my post style to plain old text so it would format nicely. Thanks slashdot...)
I'll be brief this time. Disclaimer: I'm the author of morituri, a CD ripper for Linux with support for AccurateRip, modelled after Exact Audio Copy but command line.
I was in the same situation as you a few years ago. I had originally ripped my collection to Ogg/Vorbis, and thought that this time I wanted everything 100% lossless so I would never have to rip again, but just transcode from the rips. The main issue I wanted to solve, besides going lossless, is to make sure I had no bad tracks with skips in my collection. (You detect those skips over the years listening to the songs, not as you do the rip, and you're never sure if there are glitches in the tracks or not, and it drove me crazy).
But when I researched what it meant to get it right this time, my mind got blown at everything that could go wrong. Here's a condensed version of the results of my research.
The biggest eye opener to me was that the fact that each drive model reads samples with a different offset. That offset is always the same for that model, but different across models. I have no idea why it is so (does anyone know), and we're lucky that it's constant for a model, otherwise I wouldn't even be able to solve my main concern - the detection of skips and bad rips. Nowadays people use AccurateRip, a database of checksums for ripped tracks that people upload. If your rip matches several other people's rips, you can be reasonably sure that you have a correct rip.
Since at the time there wasn't a single Linux-based ripper doing this, I created morituri.
There are several other issues that make ripping a fragile activity. I recommend you get a drive that is able to rip Hidden Track One Audio (The audio in Track 01 but between Index 00 and 01). Maybe you don't care, but I have a few gems in my collection with good stuff there (two Soulwax albums and Luke Haines's Das Capital spring to mind). Some drives are simply not able to get at this data. Most software doesn't get it either. EAC can be told to do so, but it's a manual and fragile process. morituri's goal is to create a perfect image so that you can burn a bit-exact copy; so it rips the HTOA tracks always.
I suggest you rethink whether you really want to go quick and dirty. You're going to rip the cd's once and then listen to the result many times. Are you sure you don't want to get it right on the first try this time ? Is your time spent changing the discs not valuable enough to not have to repeat it ?
morituri is probably slower than less accurate rippers, as the focus is accuracy. I would argue that the time spent ripping and encoding really is not the biggest issue. The real trouble is having to change disks, which is going to take time no matter how much time it takes for your computer to do its thing.
I made a quick calculation of how much time I would be spending to put in my 1600 CD's, and decided to spend that time on creating a LEGO CD changer instead (I had checked the price of disc changers, and the cheapest I could find was around $800, with no real guarantee of whether I'd be able to control it from Linux).
Friends visiting shared their scorn and admiration in equal doses, but the robot was able to do around 20 CD's reliably in one go, so I would just load them up in the morning before work. 3 months later my 1600 CD collection was digitized.
morituri interfaces with MusicBrainz to get the metadata, and you can retag albums later on based on a different release id or when the data is updated on MB. There's also options to do an encode of lossless rips; I regularly run a simple shell command to transcode the flacs to mp3s, and it only transcodes what wasn't done before.
Give it a try, let me know what you think.
I wish I had mod points for you.
But honestly, thomasvs, when you come this late to the discussion, AND you have something this interesting to say, I think you are allowed to post it higher in the thread, even if it's not 100% on topic.
I mean, you're politically correct to post it here, but nobody will read it. Isn't that worse than posting SLIGHTLY off-topic higher up in the thread but where it can be an added value to people because they will read it?
For what it's worth, I have a large number of 50-disc CD ripping Robots that I need to get rid of. They are USB connected. Internally they consist of a USB hub, a USB serial port controlled robot and a USB bridge connected IDE Teac CD-RW drive that work with Windows XP and dbpoweramp's batch ripper. Plus a command line driver stub I wrote that dbpoweramp calls. I need to get rid of them. Most of them are unused and in their original boxes. The boxes are heavy, so UPS ground shipping is about $30 per box to the lower 48 states (maybe a few bucks less). International shipping is prohibitive and probably not worth it ($100 to $200 per box) due to weight and size. I am giving them away for the cost of shipping. Contact me directly at brendan.hoar@gmail.com if you're interested. You can read more about them in the dbpoweramp forums if you look up "kodak" robots there. Brendan
from the previous century?
You guys don't understand Microsoft's business model. Trashy releases like Windows Vista and Windows 8 are deliberate. Trashy releases earn more money when people "upgrade".
Okay, that's my opinion, but other agree.