How to Preserve Optical Games with Data, Audio Tracks, and Subchannel Evidence
A lawful optical-media preservation workflow covering drive choice, disc condition, raw sectors, audio, subchannels, retries, hashes, metadata, and repeat reads.
An optical game can contain more than a single ISO file: multiple data and audio tracks, pregaps, indexes, raw-sector error-correction bytes, and subchannel information may affect identity or behavior. Preservation starts with media you own or are authorized to archive, a drive known to expose the required data, and repeated evidence. One successful emulator boot is not a verified dump.
Document the physical source
Photograph the label and matrix/ring codes, record region and revision markings, note visible damage, and assign a non-secret specimen ID. Clean only with a method appropriate to optical media, wiping radially rather than around the track. Never polish a rare disc as an unrecorded first experiment.
Identify the drive model, firmware, interface, operating system, and dumping tool version. Drives differ in raw-sector, cache, audio-offset, lead-in/out, and subchannel behavior. Use the preservation project’s current drive guidance for the target platform rather than assuming the fastest modern USB drive is the most accurate reader.
Capture the format the platform requires
A Mode 1 data-only disc may be representable as logical user sectors for some purposes, while mixed-mode discs require a descriptor plus separate binary/audio data or a raw format retaining track boundaries. Systems with copy protection or subchannel-dependent behavior need a documented specialized workflow. Converting to ISO before analysis irreversibly discards information that was never read.
Use a purpose-built tool such as the one recommended by Redump or the relevant preservation project, with the documented drive settings. Save command output and error/retry logs. Do not improvise commands for protected media: incorrect offsets or cache behavior can produce stable-looking but wrong bytes.
A descriptor is part of the preservation object. It records track types, start positions, pregaps, and file relationships. Keep it with the raw data, normalize line endings only in a derived copy, and hash every component:
find dump -type f -print0 | sort -z | xargs -0 sha256sum > dump.sha256Use a deterministic locale and stable relative paths in a long-term manifest. Store tool-generated hashes required by the project’s database as well as SHA-256 for local integrity.
Read again and compare
Perform at least one independent second read after eject/reinsert; for important or problematic media, use another known-compatible drive. Compare track hashes and structural metadata. Identical independent reads are stronger evidence than a single read with no reported errors, because a drive can conceal corrected or cached behavior.
If hashes disagree, inspect the tool’s error map and the exact sector range. Reclean, cool the drive, change read speed only according to tool guidance, and try another compatible drive. Do not majority-vote arbitrary bad reads into a “good” sector. Mark the artifact unresolved until it matches a trusted database or repeated reliable acquisition.
Audio tracks require offset-aware comparison. Different drives may return samples shifted by a known offset and may handle boundaries differently. A waveform that sounds right is not sample-identical preservation. Follow the database’s normalization and offset rules exactly.
Verify, package, and retain originals
Compare the dump to an official preservation database without renaming away unmatched evidence. Test a derived copy in an emulator with the correct firmware and settings. If converting to CHD, keep the raw source and descriptor until chdman verify, round-trip extraction, and target compatibility all pass.
Store at least two independently protected copies with manifests and periodic scrubbing. Include provenance but keep personal purchase data private. Optical preservation is a chain of custody: physical source, drive, command, logs, track layout, repeated hashes, database result, and derived formats. Missing one link can make a clean-looking image impossible to authenticate later.
Related:
- Fixing Incorrect Colors in an Emulator Without Hiding the Cause with a Shader
- Audio Resampling in Emulators: Reconciling Console Clocks with Modern Sound Hardware
Sources: