Rip Rip Hooray! is a specialized audio CD-ripper optimized for track recovery.

It doesn't beat a drive senseless every time a read error is encountered; it simply notes the problem and moves on. Its iterative design allows it to grab what it can, as it can, progressively filling in the gaps from run-to-run.

Between those (relatively quick) runs, you can actually do things. You can inspect the disc, give it another clean, switch drives, shut down your computer and go to bed, or check to see the rip is already good enough for CUETools repair to finish up for you.

Total recovery is not always possible — drives can only read what they can read — but Rip Rip Hooray! will rescue more data than traditional CD-ripping software, more accurately, and in significantly less time.

Iteration is key. Individual Rip Rip rips take minutes intead of hours or days, getting you access to the recovered data — regardless of "completeness" — as quickly as possible. You can re-run Rip Rip at any time, as many times as you want, with as many different optical drives as you want, to retry the outstanding regions and refine the data. You can also abort a rip early without losing your progress.

Beyond that, it supports all the good things:

• C2 error pointers
• Subchannel timecode synchronization
• Drive read offset auto-detection
• Drive read offset correction
• AccurateRip checksum verification
• CUETools checksum verification
• HTOA (can rip the pre-gap track, if any)
• Cache busting
• Sample re/confirmation
• Backwards ripping
• Good ol' WAV output
• Cue sheet generation (when ripping the whole disc)

Rip Rip Hooray! does not aspire to manage your media library, so doesn't muck about with track metadata, format conversion, album art, etc.

But it does print a nice little summary of the disc's table of contents and its various TOC-derived and encoded identifiers:

• AccurateRip ID
• CDDB ID
• CUETools ID
• MusicBrainz ID
• Track ISRCs (if present)
• UPC/EAN (if present)

(That summary can be produced on its own using the --no-rip flag if that's all you're looking for.)

Rip Rip Hooray! is a command line utility built for and tested on x86-64 Linux systems, but it may well work with other 64-bit Unix platforms and/or Windows WSL too. See the installation section for information about building it from source.

Because of its focus on recovery, Rip Rip Hooray! imposes stricter requirements on optical drives than most CD-ripping software. To work with this program, your drive will need to support:

• Accurate Stream (most modern drives qualify)
• SCSI/MMC 2+ (again, most modern drives qualify)
• C2 Error Pointers

The drive will also need a known read offset to be auto-detected, or you'll need to know and enter the appropriate value using the -o/--offset option.

If your drive has a read buffer cache that isn't auto-detected, enter its size in kilobytes with the -c/--cache option so Rip Rip can try to mitigate its effects.

Programmatic detection of cache sizes is unreliable, so Rip Rip maintains its own manual list. To have your drive included, simply open an issue with the drive's vendor/model string — as displayed in the Rip Rip summary — along with a link to the manufacturer's spec page or manual (showing the buffer size).

Unlike traditional CD-rippers, Rip Rip Hooray! can't just react to data in realtime and promptly throw it away; it needs to keep track of each individual sample's state and history to progressively work towards a complete rip.

This data is only needed while it's needed — you can delete the _riprip subfolder as soon as you've gotten what you wanted to reclaim the space — but is nonetheless hefty, generally about 1-3x the size of the original CD source.

Its peak memory usage is also higher than most other CD-rippers, though it varies based on the length of the longest track being ripped. A few hundred megabytes of RAM will usually suffice, but in worst-case scenarios like the 74-minute single-track album Delirium Cordia by Fantômas, nearly 3GiB will be required!

Rip Rip Hooray! does its best to mitigate drive confusion and inconsistency, but like any other CD-ripping software, it is ultimately dependent on the drive's ability to accurately read the data on the disc, or at least be honest about any inaccuracies.

When a disc's surface is as pocked and cratered as the moon's, or disc rot has started to take hold, chances are some of that data will remain inaccessible, no matter how many times a drive, or multiple drives, attempts to re-read it.

(The unaffiliated) CUETools's repair feature can be instrumental in filling in those final bits. If Rip Rip can't confirm the rips, toss them into CUETools to see if they're close enough for automatic repair. If not, re-Rip Rip and try again.

Hopefully with a little back-and-forth, you'll wind up with perfect rips, one way or another.

Rip Rip Hooray! is run from the command line, like:

riprip [OPTIONS]

# To see a list of options, use -h/--help:
riprip --help

First things first, rip the entire disc and see what happens!

Because Rip Rip Hooray! is optimized for recovery rather than quick, efficient transfers, you may want to use a traditional — but accuate — CD ripper for the first pass, like fre:ac or EAC. Just be sure to disable their advanced error recovery features, or you'll be in for a very long ride. Haha.

From there, re-rip the problem tracks with Rip Rip:

# Say you need 2, 3, 4 and 10. Use the -t/--tracks argument.
riprip -t 2-4,10

# Equivalent alternatives:
# -t 2,3,4,10
# -t 2 -t 3 -t 4 -t 10

If you'd rather stick with one program to keep things simple, that's fine too. Rip Rip will rip an entire disc, including the HTOA (if any), by default, and generate a helpful cue sheet at the end of the process too:

# Rip the whole disc!
riprip

Whether you're ripping a few tracks or all tracks, Rip Rip will check them against both the AccurateRip and CUETools databases to verify their accuracy. Confirmed tracks are exempted from subsequent rip passes, so aside from being perfect, they'll speed things up too.

If any tracks don't verify after the initial Rip Rip rip, check to see if enough data was recovered for CUETools repair. You'll need the whole album for this, so if you used a different program for the good tracks, you'll need to merge those files with the ones Rip Rip partially recovered, otherwise you can just open the Rip Rip's cue sheet directly.

If automatic repair works, great! You're done!

If not, iterate!

Simply re-run Rip Rip. It will pick up from where it left off, (re)reading any sectors that have room for improvement, skipping the rest.

# Refine the original rip.
riprip

# If ripping specific tracks, keep being specific.
riprip -t 2-4,10

You can do this as many or as few times as needed. If you know you'll need several passes to get the data good enough for CUETools, you can automate them with the -p/--passes option, like:

# Run through each track up to three times, if needed.
riprip -p3

# Automation also allows for other fun things, like alternating between
# forward and backward traversal:
riprip -p3 --flip-flop

If problem tracks remain, recheck the refined album rip with CUETools repair. Rinse and repeat until everything is perfect, or the drive has clearly read everything it's ever going to read.

There are a number of different options that can come in handy for tricky situations, so be sure to take a look at the --help screen for inspiration.

Good luck!

Debian and Ubuntu users can just grab the pre-built .deb package from the release page.

While specifically written for use on x86-64 Linux systems, both Rust and libcdio are cross-platform, so you may well be able to build it from source on other 64-bit Unixish systems using cargo:

# Clone the repository:
git clone https://github.com/Blobfolio/riprip

# The libcdio development headers are required when building from source;
# Debian/Ubuntu users, for example, could run the following:
sudo apt-get install libcdio-dev

# Run Cargo build from the project root:
cd riprip
cargo build --release

See also: CREDITS.md

Copyright © 2024 Blobfolio, LLC <[email protected]>

This work is free. You can redistribute it and/or modify it under the terms of the Do What The Fuck You Want To Public License, Version 2.

DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004

Copyright (C) 2004 Sam Hocevar <[email protected]>

Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.

DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. You just DO WHAT THE FUCK YOU WANT TO.