HOFA CD-Burn.DDP.Master: DDP Images & Red Book CD Delivery

CD-Text · ISRC · EAN/UPC · MD5 checksum
Pause detection · CUE/DDP import

Tansel Günay (aka Punkat) — Punkat Music Sàrls | Steinsel/LUXEMBOURG

Preparing a DDP image and Red Book Audio CD with HOFA CD-Burn.DDP.Master

Even in the streaming era, “delivery” never really goes away. Because the final meters of mastering can be just as critical as the mix itself: track order, gaps, indexes, metadata, and verification. Especially for CD replication/pressing or archive-grade physical releases, a well-prepared DDP image is still one of the most reliable ways to deliver a master.

In this post, I’m sharing a practical workflow for preparing a project as either a Red Book Audio CD premaster or a DDP image using HOFA CD-Burn.DDP.Master.

Quick note:
“I sent WAV files, it’s fine” can lead to surprises around gaps, CD-Text, ISRC/EAN/UPC, PQ details, and transfer integrity. A DDP image helps lock all of that into a controlled package.

What is a DDP image, and why does it still matter?

DDP (Disc Description Protocol) stores an Audio CD’s structure and content inside a dedicated folder set: audio data, track information, metadata, and verification files are kept together. For pressing plants, the goal is repeatability — getting the same result every time — so DDP is often one of the lowest-risk delivery formats.

What you’re really “locking in” with DDP

Track order, gaps/pauses, and index decisions
CD-Text and codes (e.g., ISRC, EAN/UPC) embedded properly
Verification: using an MD5/checksum approach to confirm file integrity

What does HOFA CD-Burn.DDP.Master do?

HOFA CD-Burn.DDP.Master is built around the “delivery” stage of mastering/pre-mastering: you can import audio, edit, create fades/crossfades, manage markers and track transitions, then export the project as a burned CD, a DDP image, a vinyl export, or various audio formats depending on the final deliverable.

The features that matter in real-world sessions

DDP image export + Red Book Audio CD burn
Tag Editor / metadata: track title, artist, album, CD-Text
Codes: ISRC and EAN/UPC support
Automatic pause detection + manual marker workflow
Import: DDP images and CUE import (a lifesaver for revisions/fixes)
Multi-CD projects (long live sets / audiobooks / compilations)
Track list export (report-style output)
MD5 checksum workflow for transfer integrity/verification

Note: On the “App” side, the integrated HOFA plugins can be used as a quick mastering/pre-mastering chain. In practice, I like thinking of it as an “outside-the-DAW final delivery control layer”.

Standard or PRO?

The Standard version covers what most people need for CD/DDP delivery. PRO adds extra speed and flexibility for heavier studio workflows.

Key PRO differences

3rd-party plugin support (VST3)
Presets: save/recall entire plugin chains
Comprehensive metadata handling (e.g., ID3, CSV workflows)
Advanced dither options for clean bit-depth conversion at delivery

My practical rule:
If your goal is simply “solid CD/DDP delivery”, Standard may be enough.
If you want your own 3rd-party chains, fast preset recall, and systematic metadata workflows, PRO makes more sense.

A practical workflow: preparing an album as DDP

1) Project settings: sample rate logic

For CD, Red Book typically implies 44.1 kHz / 16-bit. Still, it’s totally normal to work at a higher sample rate during production/mastering and convert at the export stage. The key is to be clear from the start about the final deliverable(s).

2) Audio import + edits

Drag & drop your files, set the track order.
Create fades, crossfades, and any necessary edits.
Always listen through transitions — especially on live or concept albums where “silence” may not be silence.

3) Markers / pause detection

Automatic pause detection is a great starting point, but the final call is always “ears + intent”: track start points should feel musical, and the gap length should support the album flow.

4) Metadata: CD-Text + ISRC + EAN/UPC

CD-Text: fill track titles, artist, and album fields.
ISRC: correct codes per track.
EAN/UPC: the release/album code (if applicable).

5) Export: DDP image (and ZIP if needed)

The goal after exporting is to send a pressing plant a “single, complete package”. A DDP image is typically delivered as a folder set; for transfer I usually ZIP the entire folder. The key rule here: don’t send the files one by one and don’t rename anything.

DDP folder example: CDTEXT.BIN, DDPID, DDPMS, IMAGE.DAT, MD5_CHECKSUM.MD5, PQ-Sheet.pdf, PQDESCR — A typical DDP folder exported from HOFA. Keep the set together (preferably as a ZIP) when sending it to the plant.

Inside the DDP folder (files shown in my example):

IMAGE.DAT
The “main body” of the DDP. This is where the Audio CD’s audio data is stored (the core data the plant reads).
PQDESCR
The heart of the disc layout: track starts, index points, gap/pause lengths, and PQ structure are defined here. (Codes like ISRC and UPC/EAN can also be carried via this structure.)
DDPID
Think of it as an identifier file for the DDP set — one of the key files that helps DDP readers recognize the image properly.
DDPMS
Another control/metadata file that accompanies the DDP set, used by DDP readers to interpret the image correctly as part of the standard workflow at the plant side.
CDTEXT.BIN
The binary file containing CD-Text. Track titles/artist/album CD-Text fields are written here. (Not every player displays CD-Text consistently — that’s normal.)
MD5_CHECKSUM.MD5
The “fingerprint” of the export. Used to confirm nothing got corrupted during upload/download/transfer. This is a very useful verification step for pressing plants.
PQ-Sheet.pdf
A human-readable report: track durations, start points, codes, etc. It’s not always mandatory, but it makes communication and approvals faster.

Verification: what do I check before delivering the DDP?

Exporting isn’t the end. The “professional” part of delivery starts with verification. Here’s my basic checklist:

Is the track order correct?
Are start/end points musical? Are fades correct?
Are gaps/pauses correct? (hidden intros/outros, live applause, etc.)
Is CD-Text correct?
Are ISRC and EAN/UPC correct?
Does the MD5/checksum verification pass cleanly?

Mini delivery tip:
If client approval is needed, a player approach that lets them audition the DDP and check gaps/metadata (e.g., the HOFA DDP Player / DDP Player Maker ecosystem) can speed up the process a lot.

Common mistakes (and quick fixes)

Using “grid-like” identical gaps everywhere
Instead of applying the same pause length to every track, set gaps according to the album’s flow.
Adding ISRC/EAN/UPC in a last-minute panic
If you have the codes, enter them early — revisions and approvals stay cleaner.
Making decisions without level matching
Level-match when comparing before/after. Avoid the “louder = better” trap.
Sending a DDP without verifying it
Always do at least one full pass check after export to avoid unnecessary email back-and-forth with the plant.

Conclusion: delivery is the invisible half of mastering

HOFA CD-Burn.DDP.Master is a powerful tool for organizing the “final delivery” stage after mastering. When preparing DDP images and Red Book CD premaster deliverables, it helps you systematize the technical side so your creative decisions land on a safer foundation.

Quick decision line:
If “CD/DDP delivery + metadata + verification” is a recurring need in your workflow, HOFA is a very clear solution.