Let's quickly show you the most important use cases. I'm assuming you have
downloaded and installed ddptools and a terminal/dos promt
opened. I'm also assuming you're at least somewhat familiar with working
on a terminal/dos prompt. The instructions here are written for Linux and OSX but
they work for Windows as well, with one exception: instead of
for listing all files in a directory use
Create a DDP master from a cue/wav image
First we need a cue/wav image where the complete audio for the CD including all pauses between tracks is renderd into a single Wave file. Let's assume the two files are placed in the current directory
$ ls MyMaster.wav MyMaster.cue
Now a DDP image is a collection of four or more files, since the names of these files are fixed I'd highly recommend placing them into their own directory so you can distinguish them from other DDP files. So let's make a new directory.
$ mkdir MyDDPImage
To start the actual DDP creation call
$ cue2ddp –t MyMaster.cue MyDDPImage
–t option includes CD Text into the DDP image, given that
the cue sheet has CD text info set, which
cue2ddp does not by default.
The conversion produces detailled output showing all subcode information, it also
checks that your cue sheet is valid.
Show information about a DDP master
When dealing with DDP images, the most important thing is to know which files
are actually part of it, so you send the right files to the plant. Furthermore
it's tremendously helpful to be able to see and check all the meta data found
in the master. This is what
ddpinfo is for, it even has an
--expert option to show absolutely all data fields from the
various DDP files.
To show a readably summary of our newly created DDP master type:
$ ddpinfo MyDDPImage
Another usfulthing to do, especially if you've been copying or transfering the
DDP files to another location is to proof that the image is still unaltered. This
can be done by verifying the checksum files, that
cue2ddp created for
$ ddpinfo -y MyDDPImage
Now of course you may want to burn a referenc copy of the project from your client. Given that you already have a cue/wav image, which most burning programs will accept and who's audio is bit-identical to the DDP image, you should be fine. But it's always good to have options, and so just for the fun of it, we'll make a cue/wav image out of our DDP image. Let's also create a new diretory, to keep things clean:
$ ddpinfo MyDDPImage -w loadback.wav
This will create two files
that you can use to burn CDs.