Wolfgang Woehl
Well-known member
I'll ingest your test DCP on our Doremi DCP2000 and wait for a KDM, so I can test it when we have a quiet moment here.
I'm not sure how to get you the right certificate, unless you just mean the server serial number?
Test would be great. Thanks Jonathan.
For targeting a KDM to a cinema server one needs the actual server certificate. Facilities who do this for mainstream distributors invest considerable amounts of money and time into collecting and nursing their in-house databases. These databases gather all required information about screens, servers and certificates. It's a business and they will, naturally, not share their hard-earned info.
While this 1000-islands approach works (most of the time) people in the industry are aware of its shortcomings. The level of inefficiency is outlandish. Tracking changing screen/server information by endless email blasts should be, I can only imagine, nightmarish. End users (theatres) are encouraged to join a dozen service providers for easier access to keys etc.pp.
Outside the mainstream distribution paths we are, for now, pretty much left with the same brittle and inefficient mechanism: Collect data one by one, stuff it in a database and come up with some kinds of access to it.
For our test case we want to correlate your server's serial number to a location on Doremi's site for certificates (which we have to find in the first place). Another option is to ask your integrator (the guys who sold and installed your equipment). When we bought our XDC Solo G3 last summer asking for our certificate was the 2nd question. Integrator gave us a blank stare. Called XDC and after a short Kafka run a dev told me about their ftp server and the required access info (See a previous post).
Well, we'll get there
It's really exciting, all this recent development in the opensource DCP community.
Digital screenings are quite new here in Denmark, and it's interesting to follow the "first" footsteps of the companys who dare to walk the road of DCP![]()
Yes, interesting indeed. And somewhat depressing, considering the platform was conceived almost a decade ago, right?
For a little pet project of mine, I have found all the info here in this thread a big help and inspiration to start builing my on scripts for opensource DCP making.
You got public code somewhere?
Specially with OpenDCP it seems more simple to optimize the workflow and utilize more than one cpu core.
Yes, Terrence's work is a big leap forward. I mean, on the open-source side of the pond we're still living in caves, grinding away on stone tools -- For example take CineCert's Wailua and the scope of its authoring features and one can see that there's a lot of work left to even approach that kind of flexibility. I'm very glad that people like Terrence decided to dedicate time and energy to improve our tools.