Please login or register. July 22, 2018, 10:19:15 AM

Author Topic: Troubles with encrypted DCP on Dolby  (Read 7291 times)

Lars_G

  • New Member
  • **
  • Posts: 16
    • View Profile
Troubles with encrypted DCP on Dolby
« on: July 14, 2014, 11:27:48 AM »
Greetings all.

We're modifying an existing DCP to add extra MXFs at the start and end for required material. We're not touching the existing MXFs because they were laboratory produced and we just don't want to touch them. We've tried testing the resulting DCP on a Dolby DS220 machine with a Cat 745media block. But the device hangs up in an infinite loop when trying to play the DCP where the media server loses contact with the media block, until the file or composition is deleted from the media server to stop the constant reconnection and losing contact with the MB cycle.

To test further I created several test DCPs with the same start material only, both encrypted with asdcp (ver 1), encrypted with opendcp, and unencrypted (with opendcp). The format is Interop since the main material is interop, and so far I've tested encrypted DCPs created by ourselves only on SMPTE, and only on Doremi since it's the equipment we have easier access to. The result is the same, only since the material is smaller (I guess, could be wrong), all encrypted DCPs forced us to restart the media server this time to exit out of the "lost contact with cat 745" endless loop as it was impossible to delete de resource this time (until reboot).

I know it's not the KDM as I've prepared and used and tested a KDM for the lab produced (interop) encrypted original DCP and it has worked great on the same Dolby server... the server has firmware 4.5 which by comparison is pretty new for local firmwares as I've seen a couple dolbies with 4.3 on them.

I've shared the test DCP created with asdcp MXF files here so you can give it a view as well as check the MXFs in case you can help me pinpoint what's wrong. And I thank you profusely for any feedback you can share with me.

DCP: https://www.dropbox.com/sh/kkpzvvjbyxfnowf/AADxDXtdXf5oAQBxyqDFLoMga

Asset keys:
MDIK: d5156d66-92d0-40a1-9964-c3fbc11464bd : d579ca4695ff146c649a74d3558d3d04
MDAK: f47b902f-e076-41be-a505-0577ab82ee28 : eb9b15d8cea0ffb9c81fccc4067ddecd

joop!

  • New Member
  • **
  • Posts: 26
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #1 on: July 15, 2014, 06:42:28 AM »
Could it be because the scheme of the volindex is wrong:

Code: [Select]
<VolumeIndex xmlns="http://www.digicine.com/PROTO-ASDCP-AM-20040311#">
This is the assetmap scheme

Terrence Meiczinger

  • Administrator
  • Hero Member
  • *****
  • Posts: 560
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #2 on: July 15, 2014, 12:02:05 PM »
Could it be because the scheme of the volindex is wrong:

Code: [Select]
<VolumeIndex xmlns="http://www.digicine.com/PROTO-ASDCP-AM-20040311#">
This is the assetmap scheme

Code: [Select]
<VolumeIndex xmlns="http://www.digicine.com/PROTO-ASDCP-AM-20040311#">
That is the correct namespace for volindex. There is no volume index specific schema.

joop!

  • New Member
  • **
  • Posts: 26
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #3 on: July 15, 2014, 04:12:28 PM »
I am confused. The reason I came to this is because EasyDCP player throws up an error about this. And what I see in other interop DCP's is:

Code: [Select]
<VolumeIndex xmlns="http://www.digicine.com/PROTO-ASDCP-VL-20040311#">

Lars_G

  • New Member
  • **
  • Posts: 16
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #4 on: July 15, 2014, 04:26:06 PM »
The thing here is I'm pretty sure it has to do with the MXFs alone. As when this caused the same trouble with the edited dcp, I added the reels to the existing dcp (which works on dolby), using the same schema. Edited the CPL PKL and assetmap acoordingly (and didn't touch the volume index). Signed the CPL, corrected size and hash on the PKL, signed the PKL, and ran a verification on the DCP and it passed with flying colors, plus it plays correctly on NeoDCP (made a KDM for it and ingested it). So the only common factor between the two DCPs was the MXF files.

The projectionists on the test site do not have the admin password for their Dolby. I doubt the Dolby gives any more information, their error messages are always skimpy and limited... but if anyone has a dolby (with admin password), and is willing to test the test dcp there, give me your cert and I'll make a KDM for you.

Terrence Meiczinger

  • Administrator
  • Hero Member
  • *****
  • Posts: 560
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #5 on: July 15, 2014, 06:05:31 PM »
I am confused. The reason I came to this is because EasyDCP player throws up an error about this. And what I see in other interop DCP's is:

Code: [Select]
<VolumeIndex xmlns="http://www.digicine.com/PROTO-ASDCP-VL-20040311#">

Try going to the URL http://www.digicine.com/PROTO-ASDCP-AM-20040311 and then try http://www.digicine.com/PROTO-ASDCP-VL-20040311. I'm not sure how it would be valid to use a non-existent namespace. From the documentation and specs I've seen, the volume index uses the same schema as asset map. If anyone has a link to specification that says otherwise, please let me know.

joop!

  • New Member
  • **
  • Posts: 26
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #6 on: July 16, 2014, 07:50:45 AM »
Try going to the URL http://www.digicine.com/PROTO-ASDCP-AM-20040311 and then try http://www.digicine.com/PROTO-ASDCP-VL-20040311. I'm not sure how it would be valid to use a non-existent namespace. From the documentation and specs I've seen, the volume index uses the same schema as asset map. If anyone has a link to specification that says otherwise, please let me know.

Thank you Terrence. Interesting topic. Unfortunately, I cannot find more information about this. I guess I have to ask Fraunhofer for that.
However, a footnote, visible without buying on the bottom of a page of iso.org (https://www.iso.org/obp/ui/#iso:std:iso:26429:-9:ed-1:v1:en:sec:ZZ) suggests it still can be a valid namespace, without being an online resource:

Quote
1 Readers unfamiliar with URI values as XML namespace names should be aware that although a URI value begins with a "method" element ("http" in this case), the value is designed primarily to be a unique string and does not necessarily correspond to an actual on-line resource. Applications implementing this standard should not attempt to resolve URI values on-line.

(Sorry Lars, for stealing your thread)

Terrence Meiczinger

  • Administrator
  • Hero Member
  • *****
  • Posts: 560
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #7 on: July 16, 2014, 11:24:52 AM »
Quote
(Sorry Lars, for stealing your thread)

Yeah, if you want to continue the discussion on this, let's create a new thread.

luca

  • Jr. Member
  • ***
  • Posts: 56
    • View Profile
Re: Troubles with encrypted DCP on Dolby
« Reply #8 on: July 20, 2014, 06:21:30 AM »
Hi Lars_G,
your audio mxf could be problematic on that Dolby MB. It appears you used the option "-l 7.1" with asdcp-wrap to wrap your 8 channel silence.
The result is an Interop MXF with ChannelFormat 3 (SDDS) and ChannelAssignement UL. You can see this with:
Code: [Select]
asdcp-test -i -v IntroSonido.mxf
[...]
ChannelFormat: 3
ChannelAssignment: 060e2b34.0401.010b.04020210.03010300
If you check the feature you received, it will very probably have:
Code: [Select]

 ChannelFormat: 0
 ChannelAssignment: 00000000.0000.0000.00000000.0000000
whatever the number of channels is.

Best regards
Luca

dcinemaforum.com

Re: Troubles with encrypted DCP on Dolby
« Reply #8 on: July 20, 2014, 06:21:30 AM »