Cutting tracks

Cut tracks writes one FLAC per track into the record's review directory.

If there are unsaved changes it saves them first, so what gets cut is what you can see. The status line says how many tracks were written.

Cutting clears anything already in the review directory, so re-cutting after a retitle leaves no old files behind.

Before it cuts

The plan is validated first and nothing is written unless it passes. A plan is refused when a track would:

• end before it starts
• overlap its neighbour
• share a number with another track
• run past the end of the side

The error names the track and the reason. Fix it in the track table and cut again.

Padding

Each cut keeps lead seconds before the track starts and tail seconds after it ends — 1.3 and 1.5 by default, set in the configuration. This is what stops a cut landing on the first instant of sound.

Checking the result

Finished tracks in the side panel lists what is actually in review/, read back from disk. The console below shows the raw output from the tools. If those two disagree, believe the file list.

Any track that would not decode after being written is named. That is worth acting on before importing.

From the command line

ripdoctor split <plan.json> <side directory> <output directory>

--dry-run prints the cuts without writing anything.

Next

Importing.