Editing the cd_text.cdt file?

[da goose]

Some time ago i just opened the cd text file with windows notepad to check what it looks like.
I think it should be possible to edit it this way though i remember it was not just clear text but also some 'strange' characters that i don't think it's a good idea to edit. So just edit the text that needs to be changed and i think you will be OK.

Just give it go with notepad, burn a CD from the editted ddp/cd text and see what happens.

[Darius van H]

Ooohh, that sounds a bit scary, who's to say the "strange" characters don't get garbled on opening in notepad?

In my experience factories are very fussy about any discrepancies in a DDP!

Hmmm

[da goose]

The good thing about notepad is that it doesn't do anything with text unless you want it to. So i think you could just try, leave the strange characters alone and triple check.
On second thought.. can't you just import the ddp in sonoris ddp creator, edit the CD text and export again as ddp? will also give you a new md5.

[Darius van H]

Could do, but that would be just as much work as exporting a new DDP from Sequoia!

[PieterS]

don't use notepad, each line in the cdtext file has a checksum!

With the DDP Creator you can import the DDP, make the changes and only export the cdtext.cdt file in the Tools menu. No need to export the DDP. The only thing that might go wrong is that the file size of the original cdtext.cdt file is stored in one of the ddp files and the new file can have another size. The duplication plant might ask about that. You can test that by reimporting the DDP again (in version 2.0.4) and see if you get a warning.

[IIIrd]

Couldn't the factory edit the cd text within their eclipse system?. I would have thought so.

[Darius van H]

Originally Posted by IIIrd

Couldn't the factory edit the cd text within their eclipse system?. I would have thought so.

In theory, yes, but in practice, unlikely they'd be willing, and would certainly charge the client to do it.


@Pieter, thanks, sound to me like it would just be safest to re-export a new DDP from Sequoia!

Would be lovely if you could persuade Magix to incorporate DDPC into Sequoia!

[IIIrd]

Originally Posted by Darius van H

In theory, yes, but in practice, unlikely they'd be willing, and would certainly charge the client to do it.


@Pieter, thanks, sound to me like it would just be safest to re-export a new DDP from Sequoia!

Would be lovely if you could persuade Magix to incorporate DDPC into Sequoia!

Seems arse about face really. I've always thought stuff like that should be factory things...ISRC's ICPN's and cd text. I'm biased as I'm dyslexic, but it strikes me that we do the audio and make our master, then the other numerical nonsence should be done plantside...if only.
I try and avoid cd text , copying via plextools or verifying can be torturous.

[Jerry Tubb]

I do this sometimes on my Mac with Text Wrangler.

If I need to generate a new DDP instead for a simple text correction, after the audio has already been proofed and approved, I'll use the image.DAT file from the approved DDP folder instead, just drop it in place of the the new one in the new DDP folder. Course you have to check that nothing else has changed, other than text characters.

JT

[dcollins]

Originally Posted by Jerry Tubb

I do this sometimes on my Mac with Text Wrangler.

If I need to generate a new DDP instead for a simple text correction, after the audio has already been proofed and approved, I'll use the image.DAT file from the approved DDP folder instead, just drop it in place of the the new one in the new DDP folder. Course you have to check that nothing else has changed, other than text characters.

So you then generate a new checksum for the changed line and add that as well?


DC

[Darius van H]

I've come to the conclusion that the few minutes saved by fiddling around with text file isn't worth the risk that something goes wrong, so will just keep exporting a new DDP - i can do a null test (or a checksum compare) on the two DAT files to save having to re-listen.

[Jerry Tubb]

Originally Posted by dcollins

So you then generate a new checksum for the changed line and add that as well?


DC

Hi Dave, as always you bring up interesting questions.

I'll then re-open the final DDP with soundBlade's (or PMCDs) DDP Option and check the text, ISRC, PQ Marks, audio, etc. and verify that all is well, and proceed to burn discs and/or zip the DDP folder for upload to an FTP server.

A practical approach, but no problems encountered so far.

IIRC a checksum is automatically added to the zipped DDP file when you use the "compress" feature of Mac's OSX.

Perhaps you mean a checksum between the EDL Session and the DDP image, before zipping the DDP for upload delivery?

Please elaborate.

JT

[GeorgeZ]

Eclipse language code error is BACK.