8 Mar
2016
8 Mar
'16
9:44 a.m.
On Mon, 7 Mar 2016 23:53:49 +0100
Carsten Kurz <audiovisual(a)t-online.de> wrote:
Am 07.03.2016 um 23:31 schrieb Carl Hetherington via DCPomatic:
Yes, that's all a bit clumsy. If you make a KDM later you have to open
the original project as the key for the MXFs is stored in the
metadata.xml.
Your approach is better in a lot of ways (in particular, the CPL
details and keys are kept in one place), but it depends on the
DCP-o-matic certificate/private key not changing. If you recreate
those keys your DKDMs will no longer work and your DCP will be lost (as
you won't have the key to decrypt it).
Regards,
Carl
Do you have another use for those DKDMs? I mean
other than
subsequently using them in the KDM creator?
Ah, alright... I thought I could store that DKDM as a separate file
together with the DCP, then re-open BOTH in KDM creator and proceed
from there.
I recently had an issue where I did not create a KDM directly after
creating the encrypted DCP. So, after doing other things in DOM, I
later went into the KDM creation dialog in DOM, looked up the CPL I
wanted, then created the KDM. But it didn't work, it seems it was
using the wrong key. So I thought creating and storing a DKDM would
be the safer way to create KDMs later from the DCP and a single DKDM
file. As I create encrypted DCP rarely (actually most of the time for
testing purposes only, like for this Barco issue...), I never really
used KDM creator so far, just went in and checked the translations ;-)