cannot load open cinema DCP onto dolby server

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1.  Cannot get the dolby server to recognize the DCP
2.  Works fine on other servers.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by zachary....@gmail.com on 30 Jun 2009 at 8:40

GoogleCodeExporter commented 8 years ago

hi all , we just got the same problem here , just realized that , the DSS100 
uses
interop-atom mxf file format , and is not a certified server by DCI . but the 
new
DSS200 uses SMPTE and interop formats on the DCP^
anyone found a way to ingest and play a propper DCP usig opencinematools ??

Original comment by dsil...@gmail.com on 11 Sep 2009 at 7:51

GoogleCodeExporter commented 8 years ago

Same problem here as well. Using a DSS100 any DCP created with opencinematools 
(2D 
and 3D) fails. Does anyone know a way to properly modify (or create new, 
working)XML 
packaging? I'm trying to create a DCP of a short film in both 3D and 2D (same 
film, 
just different formats for different cinema's).

Thanks

Original comment by chucky3...@gmail.com on 15 Sep 2009 at 10:24

GoogleCodeExporter commented 8 years ago

Opencinematools emits XML namespaces incompatible with DSS100. After comparing
commercially generated files with the ones generated with opencinematools, I 
came up
with the following work-around:

(using sed for search-and-replace)

####
cd TESTCLIP
mkcpl --kind test --title "TESTCLIP" --norating TESTCLIP.jp2k.mxf 
TESTCLIP.pcm.mxf |
sed -f ..\cpl.sed > TESTCLIP.cpl.xml
mkpkl --annotation "TESTCLIP" TESTCLIP.jp2k.mxf TESTCLIP.pcm.mxf 
TESTCLIP.cpl.xml |
sed -f ..\pkl.sed > TESTCLIP.pkl.xml
mkmap --annotation "TESTCLIP" TESTCLIP.jp2k.mxf TESTCLIP.pcm.mxf 
TESTCLIP.cpl.xml
TESTCLIP.pkl.xml

cat VOLINDEX.xml | sed -f ..\volindex.sed > VOLINDEX.tmp
cat ASSETMAP.xml | sed -f ..\assetmap.sed | sed -f ..\assetmap2.sed > 
ASSETMAP.tmp
mv VOLINDEX.tmp VOLINDEX.xml
mv ASSETMAP.tmp ASSETMAP.xml
cd ..
####

pkl.sed:
s/smpte-ra.org\/schemas\/429-8\/2007\/PKL/digicine.com\/PROTO-ASDCP-PKL-20040311
#/g
("http://www.smpte-ra.org/schemas/429-8/2007/PKL" ->
"http://www.digicine.com/PROTO-ASDCP-PKL-20040311#")

cpl.sed:
s/smpte-ra.org\/schemas\/429-7\/2006\/CPL/digicine.com\/PROTO-ASDCP-CPL-20040511
#/g
("http://www.smpte-ra.org/schemas/429-7/2006/CPL" ->
"http://www.digicine.com/PROTO-ASDCP-CPL-20040511#")

volindex.sed:
s/smpte-ra.org\/schemas\/429-9\/2007\/AM/digicine.com\/PROTO-ASDCP-VL-20040311#/
g
("http://www.smpte-ra.org/schemas/429-9/2007/AM" ->
"http://www.digicine.com/PROTO-ASDCP-VL-20040311#")

assetmap.sed:
s/smpte-ra.org\/schemas\/429-9\/2007\/AM/digicine.com\/PROTO-ASDCP-AM-20040311#/
g
("http://www.smpte-ra.org/schemas/429-9/2007/AM" ->
"http://www.digicine.com/PROTO-ASDCP-AM-20040311#")

assetmap2.sed:
s/file:\/\/\///g
("file:///" -> "")

----
Ingests and plays succesfully on DSS100 / DSP100.

(NOTE: Do *not* use the "-L" (SMPTE UL) command line switch with asdcp-test as
opencinematools wiki example would suggest if you're working with Dolby DSS100 /
DSP100. They require MXF Interop, which is the default in absense of "-L".)

Having a command line switch for selecting the emitted xmlns (something like 
"--xmlns
smpte / --xmlns digicine" perhaps?) would be fantastic.

Original comment by jussi.i....@gmail.com on 17 Sep 2009 at 11:35

GoogleCodeExporter commented 8 years ago

Hi all,

INFO on Comment 3 do not work in 3D-DCP.

For 3d is not possible do not use "-L" comand line,

mkcpl do not accept 3D INTEROP and send the message:

"EditRate and SampleRate do not match (24.000, 48.000).
File may contain JPEG Interop stereoscopic images.
DCP3D_INTEROP1.video.mxf: Can't open file."

DCP3D_INTEROP1.video.mxf is the file resulting of
wrapping the JPEG2000 (Left and Right folders).

How to make a valid 3D DCP valid for DOLBY DSS100 ?

Original comment by professo...@gmail.com on 21 Sep 2009 at 1:51

GoogleCodeExporter commented 8 years ago

Hi
This is Tim from Milan.
Here in Italy we just investigated about the problem 2 months ago, therefore we 
started a topic called "ARGUMENT ADJUST FOR DOLBY SERVER".

Jussi is right.
We successfully get the dolby server (100 vers.) ingest the dcp created with 
opencinematools simply adjusting the schemas signature.

By the way we automated the process writing a simple bat file to stay in the 
pipe 
and correct the aboves only on needed tasks.

The focus is the dolby show store (DSS100) as user starting the topic DSILVAO 
said, 
the new DSS200 server does not relate to this problem, here we can not confirm 
this 
since we have no access to the new dolby server.

Now even user on comment n°3 is right, would be great if anyone could add some 
line 
of code to make opencinematools work on INTEROP 3D MXF file.

Tim (Milan-ITALY)

Original comment by timothy_...@hotmail.com on 25 Sep 2009 at 11:49

GoogleCodeExporter commented 8 years ago

An update on this issue and how it relates to Dolby software releases:

Currently DSS100 / DSP100 combos on the field have *mostly* the series 3 of the 
Dolby
system software (3.2 if memory serves).

4.0.2 firmware is available (and has been for a while now) from Dolby in two 
flavors: 
- the non-compliant version (which is compatible with the old firmware as far 
as the
"ingestibles" are concerned)
- the DCI-compliant version (which should ingest the SMPTE formats)

Deployment of the comliant firmware is on hold for now "until the industry 
switches
over [to DCI compliancy (?)]". So the end of this mess is in sight and 
eventually the
problems will just go away as the Dolby servers get their sh... stuff together.

(The absolutely latest firmware (4.2) seems to be available only for DSS200 for 
now:
the firmware apparently occasionally crashes on the DSP100 media block leaving 
"snow"
on screen.)

Original comment by jussi.i....@gmail.com on 26 Nov 2009 at 9:47

RicoCasta / opencinematools

cannot load open cinema DCP onto dolby server #6