3D DCP ON DOLBY SERVER (DSS100) [SOLVED!]

[GoogleCodeExporter]

Hi to everyone, it's tim from Milan (ITALY)

i'm following up about the 3d dcp creation with opencinematools.
Opencinematools does not allow us to create stereo dcp containing mxf 
interop asset, only smpte wrapped essence can be used (asdcp-test -L 
option).

We started investigated and finally solved the problem.
We dhave umped out the mxf interop, searched the uuid and manually 
replaced the <MainStereoscopicPicture ..> with <msp-
cpl:MainStereoscopicPicture xmlns:msp-
cpl="http://www.digicine.com/schemas/437-Y/2007/Main-Stereo-Picture-CPL"> 
(and relative </msp-cpl:MainStereoscopicPicture>) on a previously 
generated cpl file.

Then manually corrected all the info in the other file (PKL & MAP, uuid, 
size) deleted the hash tag (couse was not possible at that point generate 
a new valid one) and tried to ingest and TADA!!

Play succesfully also on DSS100.
Ok, this is not a ethic procedure, it shouldn't be considered in a 
production environment but you can try yourself for educative or test 
purpose only.

The good thing as ever should be to add missing lines of code in source 
file and recompile a working version.

Cheers

Original issue reported on code.google.com by timothy_...@hotmail.com on 26 Sep 2009 at 11:42

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

First of all take it easy and don't write stupid thing as well.
Digest is required from the DCI specific but yuo can ingest asset without it as 
well.
Hash certainly must be calculated easy and surely we do how to do that, but it 
should be implemented in the source code for interop UL mxf value. As i 
specified we 
realized a quick test to ingest 3d material only on DOLBY DSS100, maybe you 
didn't 
read the post entirely, i specified for test only, just to study and develop a 
free 
tools capable to do thing as well as commercial software, how do you think 
cineasset 
or qubemaster work?

Please you, connect your mind before post on this forum, read seriously DCI 
specific, test seriously on the server and finally study the source code and 
post 
comments can improve the development of opencinematools that (and i was not 
referring to asdcp) is not properly configured to produce dcp that dolby dss100 
can 
ingest.

Cheers.

Original comment by timothy_...@hotmail.com on 28 Sep 2009 at 2:39

[GoogleCodeExporter]

To manually create a HASH string, do this:

openssl sha1 -binary -out sha.bin videofile.mxf 
openssl base64 -in sha.bin -e

Cheers
Christer

Original comment by chris...@rezq.se on 29 Sep 2009 at 3:01

[GoogleCodeExporter]

Tim, did you use the -L switch on asdcp-test for your 3D-DCP creation.
(SMPTE or MXF Interop)

cheers
.c

Original comment by chris...@rezq.se on 30 Sep 2009 at 7:35

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi Christer

thank you for the open ssl tip ;)
You can use -L option on asdcp, it writes smpte Ul values (2labels only) in mxf 
file 
that opencinematools can use without problem..but the problem is that DOLBY 
DSS100 
(not a DCI compliant server) does not ingest and playback SMPTE DCP.

So, as i said, the only working solution (for test only) is:
1) wrap essence with mxf interop value (default);
2) manually replace tha "MainStereoscopicpicture" tag and urn:uuid with correct 
ones;
3) manually replace urn:uuid in pkl file (eventually replace hash with new one 
calculated as you said before);
4) replace urn:uuid in assetmap.

NOTE IMPORTANT: REPLACE OF ALL XMLNS SIGNATURE IN DCP FILE IS ALSO REQUIRED, 
OPENCINEMATOOLS WRITE SMPTE COMPLIANT PACKAGE THAT DOLBY DSS100 DOES NOT INGEST.

By the way DSS100 is no longer available on the market since dolby is marketing 
a 
new (smpte compliant) version called DSS200, but i suppose there are many 
working 
DSS100 dolby server in the world so implementation of code in opencinematools 
to 
support mxf interop package would be great.

Cheers
Tim

Original comment by timothy_...@hotmail.com on 30 Sep 2009 at 8:02

[GoogleCodeExporter]

Do you mean replace the urn:uuid for the video.mxf file, not the xml's 
urn:uuid??
Cheers
Christer

Original comment by chris...@rezq.se on 30 Sep 2009 at 3:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi Christer

Regarding your question it depends from how many stereoscopic (manually 
corrected) 
files you want to ingest on dolby dss100.
Since we realize a quick test we adopted previously generated working (interop) 
dcp 
files that was deleted from the showstore in the meantime.

In our test we replaced only the asset uuid but, of course, if you plan to 
ingest more packages you will need as many fresh uuid as every xml document 
(and mxf 
wrapped asset) you wish to load on dss100.

You know why..

Original comment by timothy_...@hotmail.com on 30 Sep 2009 at 5:49

[GoogleCodeExporter]

Please, rado.markov, be more constructive or do not answer to questions.  This 
software 
has been developed for both commercial and free use.

This time I've removed you comment, try to be king with other.

Original comment by marc.van...@gmail.com on 27 Jan 2010 at 9:56

[GoogleCodeExporter]

Hi Tim,

I was trying to email you on DSS100 Stereo solution.

Could you please attach any examples or screenshoots with more detailed 
instructions
on what to do with video.mxf, it is clear what to do with cpl,pkl, assetmap.

But what exactly to extract from video.mxf, what to replace with, what to take 
with
Dolby complaint(we have several working Dolby compliant projects) project 
(video.mxf)

Original comment by mr.denis...@gmail.com on 17 Mar 2010 at 4:55

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi to everyone, I'm Antonio, I have just a question about opencinematool. I try 
to
create a dcp for a local cinema but the output file from opencinematool isn't 
read
(ingest) from a Qube server and a Doremi server. If anyone have idea or know a
solution to this problem I'm so glad to talk about this.

thank's for all

Original comment by quelli-d...@libero.it on 26 May 2010 at 2:09