Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Digital Cinema Package

Many many thanks
When I did it in sudo su with the instructions above, it worked. I have just done a test. The Command C creates a file but D and E say that C is invalid.

PROJ.cpl.xml: Invalid CompositionPlaylist or PackingList file.

I used Chris Perry's steps

Command C (create an XML composition playlist):
mkcpl --kind feature --title DCPFULLNAME \
--annotation DCPFULLNAME --norating \
PROJ.video.mxf
PROJ.audio.mxf > PROJ.cpl.xml​
Command D (create an XML packing list):
mkpkl --issuer BitFilms --annotation DCPFULLNAME \ PROJ.video.mxf PROJ.audio.mxf PROJ.cpl.xml > PROJ.pkl.xml
Command E (create the ASSETMAP and VOLINDEX XML files):
mkmap --issuer BitFilms \
PROJ.video.mxf PROJ.audio.mxf PROJ.cpl.xml PROJ.pkl.xml
Anyway, I am going to have a play and see how I get on. Many thanks again,
 
As promised, I have listed all the stages I have used to install an openscource version on a mac. It is work in progress so, if any of you have the time I would be very interested to have any contributions to make this doc better.

Digital cinema package - how i, a computer neophyte, made an open source dcp on my mac
http://www.reduser.net/forum/showthread.php?t=43787
 
Does anyone know how to format subtitles for the DCP?

You can look at Belle Nuit (www.belle-nuit.com) or MacCaption (www.cpcweb.com), both of which can generate TI CineCanvas files (the format required). I think you can get demo versions of both. The files are just XML files, so if you can generate some test files, you can probably gain enough knowledge to write your own from scratch, although it's much easier to use a program like one of these two to do that for you.
 
Another question. What is the workflow for creating reels for an open source solution? Is there a length limit? Any ideas?
 
Having had a look at the Cinecanvas XML, I see that it is referenced to a timecode. Where does this timecode come from? In the opensource workflow, I use numerous file formats that do not have timecode metadata, so I presume that DCP does not read file headers to extract the tc. Is the tc relative to the reel length? Any ideas?
 
Many many thanks
When I did it in sudo su with the instructions above, it worked. I have just done a test. The Command C creates a file but D and E say that C is invalid.

PROJ.cpl.xml: Invalid CompositionPlaylist or PackingList file.

I used Chris Perry's steps

Command C (create an XML composition playlist):
mkcpl --kind feature --title DCPFULLNAME \
--annotation DCPFULLNAME --norating \
PROJ.video.mxf
PROJ.audio.mxf > PROJ.cpl.xml​
Command D (create an XML packing list):
mkpkl --issuer BitFilms --annotation DCPFULLNAME \ PROJ.video.mxf PROJ.audio.mxf PROJ.cpl.xml > PROJ.pkl.xml
Command E (create the ASSETMAP and VOLINDEX XML files):
mkmap --issuer BitFilms \
PROJ.video.mxf PROJ.audio.mxf PROJ.cpl.xml PROJ.pkl.xml
Anyway, I am going to have a play and see how I get on. Many thanks again,

Hi Christopher, Did you overcome this issue? I've just run into exactly the same problem.

Desperate to hear what you did to get out of it.

Antony
 
I have contacted Chris Perry, a god, who started the google code thread, to see how he got around it. Hopefully, he will have a solution.
 
Does anyone know what the subtitle file should be called. For that matter, has anyone got a list of the file required for a DCP so I can make sure I have everything?
 
I did manage to contact John Hurst about this problem and he stated that XML support is optional in ASDCPLIB and that you have to enable expat while compiling ASDCPLIB. I have tried it but still the same error comes up. the code for this is ./configure --with expat-
This also links in to what Chris Perry was saying about turning on xml support.

Still not working for me though!!
 
I thought that I was using the asdcplib from cinecert for the MXF creation but the XML creation was done using the opencinematools elements. If this is not the case, why use opencinematools at all if asdcplib can do it?
 
1. Invalid CompositionPlaylist or PackingList file

What is your CPL.xml file?

2. XML support in ASDCPLIB

You need to ensure you have an XML parser lib installed, like xerces or expat.
You then need to run ./configure with the appropriate XML lib enabled (--with-expat-lib or --with-xerces-lib).
This is only needed if you are doing timed-text files(closed captioning or subtitles)

3. Opencinematools vs asdcplib

asdcplib wraps/creates an MXF container around your content (audio, video)
opencinematools creates the XML files used to describe a "playlist" or collection of mxf wrapped pieces.
 
Having spoken to Chris Perry, there seems to be an issue with the Kumu library on Open Cinema Tools (OCT).
http://code.google.com/p/opencinematools/issues/detail?id=25
He explains how to rebuild the app correctly for Linux.
It seems that the problem is that the Kumu library is not deployed correctly for the OSX build, or more to the point, it is not deployed at all in the OSX version. Therefore the easiest solution is to find a version of Kumu for OSX. (I am repeating what Chris said but I must confess I don't understand all of it)
So, in short, we need the help of the gods to get the OSX version off the ground. ( I hope Wolfgang is reading this.)
 
Last edited:
Christopher,
Kumu is part of asdcplib. Get the latest release (http://www.cinecert.com/asdcplib/asdcplib-1.5.32.tar.gz) and install. Then try changing 2 lines in opencinematools-1.1.2/build/macosx/build.tcsh:

* Change
$compileCmd -o ../../bin/mkpkl.o ../../src/mkpkl.cpp -I${PREFIX}/include
* to
$compileCmd -o ../../bin/mkpkl.o ../../src/mkpkl.cpp -I${PREFIX}/include -D_FILE_OFFSET_BITS=64

* and
$compileCmd -o ../../bin/mkmap.o ../../src/mkmap.cpp -I${PREFIX}/include
* to
$compileCmd -o ../../bin/mkmap.o ../../src/mkmap.cpp -I${PREFIX}/include -D_FILE_OFFSET_BITS=64

and rebuild the opencinematools binaries.
 
Christopher,

I have compiled everything on OSX, so it does work. As Wolfgang stated Kumu is part of asdcplib. What is your email? I will send you all of my versions, which hopefully you can compile.
 
Back
Top