Testing encrypted DCPs and KDMs
wolfgangw edited this page Apr 17, 2013
·
26 revisions
Pages 21
- Home
- A Father's Letter
- Cinemaslides
- Cinemaslides Usage
- DC Auth Blog
- Digital Cinema
- Digital Cinema Authentication
- Digital Cinema X.509 certificate chains
- Frequently asked questions
- Links
- MISC
- MPEG2 essence support for opencinematools 1.1.2
- Mystery Meat
- Notes
- Notes on DCI specification and related SMPTE papers
- Notes on handling audio assets for Digital Cinema
- Open source tools for a digital cinema pipeline
- Scripts
- Testing encrypted DCPs and KDMs
- TODO
- White Gamut
- Show 6 more pages…
Clone this wiki locally
I’m collecting feedback and data about ingest and playback of encrypted signed DCPs and KDMs generated with Cinemaslides or other related free tools. The point being to create — in parallel to proprietary knowledge pools — a publicly available pool of knowledge about the field.
Test reports will be much appreciated. A useful test sequence would include the following steps:
- Head over to Downloads to get TONEPLATES-SMPTE-ENCRYPTED, unzip and ingest the encrypted package on your server/media block.
- Check server log for error messages.
- Either create a KDM targeting your server/media block using Cinemaslides1 or let me make a set for you.
- Before ingesting a KDM: Select for playback to confirm the package will not play.
- Ingest KDM. If you’re testing a set of KDM formulations ingest and test 1 KDM at a time.
- Check server log for error messages.
- Select again for playback to confirm the package decrypts and plays back properly.
- Send me a little report including model, make, server/media block serial number and software version.
Feedback, corrections, insights, code, as usual, very welcomed and much appreciated. Get in touch
Wolfgang Woehl
Server model | Versions | Ingest encrypted DCP | Ingest KDM | Playback encrypted DCP | Variants & Notes | Tester |
Sony LMT-300 | 2.21.3 | OK | OK | OK | mt1 2 | Tom Aspy |
Doremi ShowVault-4 | 2.2.2.0 | OK | OK | OK | mt1 | Tom Aspy |
Dolby DSP/DSS 100 | 4.3.9 (13) | OK | OK | OK | mt1 | Tom Aspy |
Doremi DCP-2K4 | 21.2 k, 2.2.5-0, SM 2.0.8-0 | OK | OK | OK | ds | Olivier Perrière FreeDCP.net |
Dolby DSS 200 | 4.3.5 (6), 4.4.2, SMS 4.3.3.7-d | OK | OK | OK | ds, mt1 | Olivier Perrière FreeDCP.net |
Fraunhofer easyDCP Creator+ | 2.0.0 (Mac) | OK | OK | OK | mt1, ds | Joen Carlstedt Svensk Medietext |
Fraunhofer easyDCP Player+ | 1.8.0 (Mac) | OK | OK | OK | mt1, ds | Joen Carlstedt Svensk Medietext |
ROPA CS 2 | CS-008-009-0112 | OK | OK | OK | t1, mt1, da, ds | Andrä Steiner, github.com/andrae-steiner |
Doremi Showvault (Christie CP4230) | 30.05g / 2.2.3-0 (2.2.0-5) | OK | OK | OK | t1, mt1, da, ds | Julius Schall, Digital Cinema Mastering |
GDC SA-2100A | 7.7a-combined3 | OK | OK | OK | t1, mt1, da, ds | John Roddy |
Imax Digital DCP2000 | 1.0.4-2, 2.0.1Y / 20.1.89.20 | Fail | not tested | not tested | SMPTE DCP not recognized | John Roddy |
DVS Clipster | 4.3.1.3 | OK | OK | OK | t1, mt1, da, ds | Tammo Buhren, zweiB |
Dolby DSL 100 | 4.2.1.3 | not tested | not tested | not tested | ds | Terrence Meiczinger, OpenDCP |
Dolby DSS 200 | [4.2.1.3] [4.3.9 (13)] | OK | (OK) | OK | [ds. KDM Ingest only after signature prefix change from dsig to ds ] [mt1] |
[Pavel Klepinin] [Tom Aspy] |
Dolby DSS 200 | 4.2.? | OK | not tested | not tested | ds | Terrence Meiczinger, OpenDCP |
Doremi DCP2000 | ? | OK | OK | OK | ds | Ronan Delacroix |
Doremi DCP2000 | 2.0.10 (21.1z) | OK | OK | OK | ds | Jonathan K. F. Jensen |
XDC Cinestore Solo G3 | 5.5.3-88 (SP2) | OK | OK | OK | t1, mt1, da, ds | Wolfgang Woehl, Digital Cinema Tools |
1 Here’s a recipe for rolling your own KDMs for TONEPLATES:
Get the content_keys.zip
from Downloads, unzip and run
cinemaslides -v debug --kdm \
--cpl <path to the cpl from TONEPLATES-SMPTE-ENCRYPTED...> \
--target <path to public key certificate of your targeted server/media block> \
--keysdir <path to content_keys> \
--formulation <kdm formulation>
This assumes you have a SMPTE compliant certificate chain in CINEMACERTSTORE/, used here to sign the generated KDM. See make-dc-certificate-chain.rb (and preferrably read it before using it) for a proof-of-concept script to create those certificates.
2 KDM formulations: Transitional 1 (t1), Modified Transitional 1 (mt1), DCI Any (da), DCI Specific (ds)