Skip to main content

Hello. Anybody out there aware of a way to manipulate the CD text information of a DDP file set? For example: if you inherit a DDP file set, and discover a mispelling in the CDtext content, is it possible to correct that spelling without re-running the audio content?

Topic Tags

Comments

Zilla Mon, 04/18/2005 - 14:32

I may not have asked my question very clearly. Let me try again, with the actual problem at hand as the example:

We have mastered an album that has beem assembled in Sonic. The client then informs us that they would like to include CDtext, but Sonic does not currently support this. The project could be reassembled in our AudioCubes (which does supports CDtext) but the engineer prefers the sound of Sonic for this project. What to do?

So I think to myself: the various CD elements are distributed among the several files contained in the DDP file-set. Maybe it would be possible to hack into the DDPID or PQ-DESCR files to insert the needed CDtext without touching the audio image itself. This should work around re-running the audio image and avoid another generation.

Has anybody ever done anything like this?

FifthCircle Mon, 04/18/2005 - 17:45

How is the CD Text done right now?

In Sequoia, the DDP that is generated, we have the 4 standard DDP image files plus a file called cd_text.cdt. That CD Text file is the only one that contains the cd text information.

If you load the DDP back, first of all, you shouldn't have to change the image.dat file (which contains the audio). If every sample stays the same, your new DDP with new PQ-Desc and DDPID files should be fine. You replace the old ones with the new and you're set. Heck, even regenerating the DDP to a new directory could give you the new info. DDP is supposed to be universal (although, I've certainly heard of differences between specs that shouldn't be there). As long as the PQ files refer to the correct samples in the image file, you should have a valid DDP image.

I'd give that a try, then load the new DDP back into your DAW and make sure it nulls before you send it out just to make sure that everything is kosher.

--Ben

Michael Fossenkemper Mon, 04/18/2005 - 17:46

Key features of SonicStudio•DDP v2

* Load and save to DCA’s DDP or Disc Description Protocol format
* Fast, easy editing with smart fade tool
* Segment & breakpoint-based gain adjustment
* Opens AIFF, WAV, BWF & SD2 44.1 kHz interleaved files at 16 to 24 bits
* Saves version 2-compliant DDP image file sets, regardless of source integrity
* Complete PQ editing, including SCMS, emphasis, UPC/EAN and ISRC
* Automatically generates & validates PQ subcodes in real time
* Convenient Mark Info pop–up
* Comprehensive Transport Controls
* Creates CD-DA reference discs on CD-R
* Saves in Roxio’s Jam image file format
* Premastering–optimized metering
* Produces industry standard SonicStudio PQ log files
* No additional hardware required - plays back through Core Audio
* Clean, easy to navigate NGC user interface
* OS 10-native application for Mac OS 10.3.5 or newer

Now I would imagine that complete PQ subcode editing would include Text, but I could be wrong.

anonymous Thu, 05/12/2005 - 08:13

we got this kind of problem in the studio wher i m working and the only solution we found was to use the Sadie station (dsd format), then we could change the PQ informations without re-processing a ddp file. we just had to change the pq or the isrc code , naturally you have to get a Sadie station ....again very expensive...

ps: sorry 4 my bad english