Help / CD ripping

A rip failed or stopped part-way

A rip can go wrong three ways: one track with a red badge, a rip that stopped with an error, or a Stop you pressed. Each leaves something different behind.

The short answer

One unreadable track does not sink the disc. The rip carries on, that track is marked failed with no file written for it, and every other track lands in your library. Clean the disc and rip it again in Secure mode. The output folder is keyed to the disc, so a second attempt goes back to the same place and writes over what it can read.

If the whole rip stopped, an error appears in the warning strip near the top of Vesari RipCore, quoting what the drive reported rather than guessing at a cause.

One track failed, the rest are fine

A track the drive cannot read is skipped, not saved as silence. On the progress list you get a red failed badge and a bar that stays empty, and the summary adds ", 1 not saved" straight after the headline count. The rip log marks that row FAILED with the drive's own reason and its footer counts the tracks not saved.

To try again:

Clean the disc, paying attention to the outer edge.
Check that Secure is selected rather than Burst.
Press Rip CD.

Every track failed

When not a single track could be read, that is a failed rip rather than a finished one, and Vesari says so plainly: "The rip failed: none of the 12 tracks could be read", followed by the drive's reason. No rip log is written and no audio is left behind, so nothing can be mistaken for a finished album, though an enhanced disc's cover art may stay in the otherwise empty folder. That points at the disc or the drive rather than one track: heavy damage, a dirty surface, or a drive that will not deliver CD audio.

The disc came out mid-rip

If the tray opens or the disc is pulled during a rip, the recorded reason is exactly that: the disc was removed or the tray opened during the rip. Tracks that had already finished are kept. Everything after that point is marked failed, because the rip keeps going and every remaining read fails the same way.

You cannot cause this from inside the app by accident. Eject is refused during a rip with "A rip is in progress. Press Stop first, then eject." That refusal lives in the engine, not only in a greyed-out button.

You pressed Stop

Stop appears only while the drive is being read, and it is a clean stop rather than an abort:

Tracks that finished are kept, written, indexed and tagged like any other rip.
The track being read when you pressed Stop is discarded, so nothing truncated is written.
The headline reads as a partial, for example "Ripped 4 of 12 tracks (stopped)". The denominator stays the disc's own track count, so it cannot be mistaken for a full album.
The log is written as rip-log.partial.txt, opening with a banner saying the rip was stopped and that it attests only to the tracks listed.

Press Stop before the first track finishes and nothing is saved: no files, no log, and the empty folder is removed.

Running low on disk space

Vesari does not check free space before it starts, so a disk that fills up mid-rip surfaces as a write failure part-way through, with the error in the warning strip. Tracks written before that point stay in the folder, and no rip log is written: the failure stops the rip before the log stage.

Refused before the read begins

Three things stop a rip in the first second, checked in this order:

Another rip already running. Only one rip can hold the drive.
A destination outside your library folders. Files saved there would refuse to play, so the rip never starts. Pick a folder from Add to library folder. The same message appears when the folder list itself could not be read.
The free rip allowance. Free licences include five discs, a trial twenty, covered in Caps and allowances. It is spent only once a rip lands in your library, so a failed rip, or one stopped before the first track completes, costs nothing.

What ends up on disk

Rips go into a Ripped folder inside the library folder you picked. The subfolder is named with a short disc id rather than the album title, so expect a run of letters and numbers. Inside sits one FLAC per saved track, named as "01 - Title.flac", a cover image if the disc carried one, and either rip-log.txt or rip-log.partial.txt. A failed track has no file. Only one log survives per folder: a complete rip clears an earlier partial, and a stopped re-rip clears an earlier complete log that no longer describes the files beside it.

When it keeps happening

Every rip writes its start, outcome and each failure to a dedicated rip log, bundled in automatically when you send a report. If one drive keeps failing on discs that read fine elsewhere, use Report a Bug in Settings and name the discs. See Reading the logs and How to report a problem.

← All help articles