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 - how i, a computer neophyte, made an open source dcp on my ma

Christopher Lowden

Well-known member
Joined
Jan 4, 2010
Messages
182
Reaction score
1
Points
18
PART 1

DIGITAL CINEMA PACKAGE - HOW I, A COMPUTER NEOPHYTE, MADE AN OPEN SOURCE DCP ON MY MAC.

Intro:
Firstly, I would like to thank Chris Perry at bitfilms. What I will describe below is a mac version of his linux workflow and of what is written was by him.
http://bitfilms.blogspot.com/
Secondly, I would like to thank, amongst many, Fabien Illide, Terrence Meiczinger, Agustin Goya,John Hurst at Cinecert and Wolfgang Woehl
http://wiki.github.com/wolfgangw/digital_cinema_tools/
Thirdly, all those that contributed to the Digital Cinema Package thread, in particular Leerafel
http://www.reduser.net/forum/showthread.php?t=33118
I suggest you read all of the above sites info before starting.
Without their work and the work of many others (plus some cash from the European Union), none of this would be possible. Many thanks

This document is not a manual, but more a 'how a managed it'. It is a starting point and I hope that my peers who are far more qualified than myself can contribute to a more definitive version.

DISCLAIMER: I CANNOT BE HELD RESPONSIBLE FOR THE ACTIONS DESCRIBED BELOW . ALSO, I AM NOT A UNIX PRO, SO I WILL NOT BE ABLE TO TELL YOU WHY IT IS NOT WORKING FOR YOU. I AM A FILM EDITOR.

Preamble:
1. What I describe below is how I did it. This is not necessarily how it should be done. You must be prepared to work your own version as I am sure that it will not work for you first time round.
2. You should read what is written on Chris Perry's blog
http://bitfilms.blogspot.com/
and also all the elements at
http://wiki.github.com/wolfgangw/digital_cinema_tools/

YOU MUST HAVE A BASIC UNDERSTANDING OF MAC TERMINAL COMMANDS AND APPRECIATE HOW THE TERMINAL WORKS. There are loads of web pages explaining basic unix commands. It took me a few days and alot of hasseling others to understand how to use the basic commands needed for this tutorial.
Basic commands needed for this tutorial are:

sudo su
cd
cd ..
ls
./
*
make

DO NOT CONTINUE UNTIL YOU HAVE MASTERED THESE SIMPLE COMMANDS.

The work on this tutorial was done on a macintel 2.66ghz OS 10.5.8. This tutorial will probably not work on a PowerPC and may not on 10.6 or 10.4. You can always try, though. TRYING IS THE ESSENCE OF THIS TUTORIAL.

Before you start:
To help you in this endeavour, I suggest that:
1. You have mastered the very basic unix commands. Check out;

http://www.ee.surrey.ac.uk/Teaching/Unix/

2. You have a very large, empty hard drive (for a 30min film I used up 1 terrabyte of HD with all the file that are created.)
3. Loads of time and patience.
4. A very clean OS. I suggest you install a virgin OS on your dedicated DCP work disk. An old OS full of dodgy apps off the web may not help.
5. Your film must be finished and that you have a 5.1 mix (You can do this with stereo elements but you will probably end up having to duplicate the stereo tracks into the 6 tracks needed for a standard cinema theatre).
6. You must have Xcode installed. It can be found either on your OS DVD install or at
http://developer.apple.com/technologies/xcode.html
You must install the version that corresponds to your OS.
7. I suggest that you install a free utility called ONYX
http://www.titanium.free.fr/
if you wish to see all the hidden files that you will be manipulating.
8. Make friends with your local projectionist who has a digital projector and a server. I have found that projectionists are very curious about all this and so very approachable.
9. Macports: some much more talented persons than myself, were able to short curcuit some ofthe installation procedures described below using macport. Macport is well documented on the web and the Porticus application
http://porticus.alittledrop.com/
is simple to use and open you up to loads of opensource apps that are very interesting. That said, I never managed to get any of the apps described below to install properly, hence this document.
10. Be aware that a DCP is based on ISO standards, therefore the rules are very strict concerning how it is formatted. Be prepared to spend loads of time getting your film up to these standards.

How to create a Dolby 5.1 from a stereo file.
Using Soundtrack Pro that comes with FCP, you can make a very simple 5.1 mix from stereo elements. The discussion below explains how.
http://discussions.apple.com/thread.jspa?messageID=11437878&#11437878

I'll give you some general "rules of thumb" whatever that means. The thing you have to be careful about is what happens when the tracks get downmixed, which they will at some point and you will have no control over that. So you have to be careful about just duplicating tracks and putting them both front and rear, or putting dialog in all the channels, etc.,

1. Dialog goes C channel only
2. Music goes L-R, if you want some surround put a slight delay or reverb of the music in the surrounds. A good upmix plug-in can be used for this.
3. Hard sfx and foley generally go in the C channel, other sfx L-R, and passbys or special effects can go in the surrounds.
4. Backgrounds. If like most people you're working with stereo backgrounds what one generally does is put one or more bgs in the front and a couple of different ones in the rears. You can collapse them a bit toward center if they sound too wide.

This is all pretty general, and you do have to monitor it properly. Try to avoid the beginners mistake of using the surrounds too much, they are they for support the screen is in the front that's where the sound comes from.
 
Last edited:
The film I am working on is a PRORES 1980x1080 4:4:4 10 bit QT file from Final Cut Pro.
FOR A STANDARD DCP, THE FILM MUST BE IN 24fps. You will probably have to pitch the sound to get the right frame rate if you are not in 24fps. Some server might hande 25fps, but this is unclear.
The audio is a 5.1 24bit 48khz Protools mix in 6 seperate mono wave tracks.
The audio and video must be exactly the same length.


STEP 0. Prepping your QT for 24fps
First thing to know is that a 24fps DCP is 24fps, not 23.98 or anything else. I am in 25fps world, so I used Apple's Cinema Tools to conver the file video to 24fps.
The DCP 24fps Dolby 5.1 version of the film was mixed in protools with a low res version of the 24 QT file, applying a 4.1% pitch change. Naturally, this means that your film runs longer.
A list of pitch percentages for protools is available in their manual.
Otherwise, you can recut you film in a 24fps ...

Also you can read the Leerafel explaination that uses Adobe Premier.
http://www.reduser.net/forum/showthread.php?t=33118

Preparing film into reels
Each reel is a seperate DCP, therefore they must be prepared before starting the process below.

Preparation of Sound files:
Dolby 5.1 24bit 48khz with 6 seperate mono wave tracks. (2.0 and 7.1 are possible)
Ref at 1khz: -20dbfs
Speed: 24fps
If reels are made, each reel must have 6 assoociated tracks
Wave files are named:
Reel Number + track L / R / C / Lfe / Ls or Rs
Each track must start with a 1khz beep with coresponding image at 48 frames before start of programme.
The audio and video must be exactly the same length.


CHECK THE NUMBER OF FRAMES THAT THE QT MASTER HAS. A FRAME COUNTER CAN BE FOUND BY CLICKING ON THE TIMECODE DISPLAY IN THE PLAYER.


STEP 1. export PNGs from source QuickTime movie
Use Quicktime Pro to export a PNG image sequence, in Millions of Colours, non-interlaced to a dedicate folder on your new HD.
I suggest that you keep your file QT file name very short.
TEST EVERY STAGE OF THIS TUTORIAL ON A FEW SECS OF IMAGES BEFORE DOING THE FILM.



Step 2: convert to 12 bit per channel XYZ color images
DCPs do not have a RGB colourspace. They use an XYZ colour space. To convert your png files to the new colour space you need ImageMagick

You can download the latest version of ImageMagick
http://www.imagemagick.org/script/download.php?ImageMagick=7j7ci2rtpr0prq7qiiuciu1og0

The installation procedure is described clearly at
http://www.imagemagick.org/script/install-source.php#unix

Chris Perry writes "This takes a 1920 x 1080 PNG from step 1, removes any alpha, pads the image with 64 pixels of black on each side so that it becomes 2048 x 1080, sets the bit depth to 12 bits per pixel, and does a linear-space color shift from RGB->XYZ. Then it writes the image out as a TIFF."
This app works on single images. I reworked the chris Perry command to make it repeat on all the elements in a folder. You will have to rework the command below for your own file paths (hence why you need to have an understanding of unix).

In the terminal, navigate to the folder that has your pngs. Then copy:


for image in *; do echo $image; convert $image -type TrueColor -alpha Off -background black -extent 2048x1080-64 -depth 12 -gamma 0.454545 -recolor "0.4124564 0.3575761 0.1804375 0.2126729 0.7151522 0.0721750 0.0193339 0.1191920 0.9503041" -gamma 2.6 <TIFF FOLDER NAVIGATION>$image.tif; done


When you open the tiff files, they will have a wierd colour. If you want to see them correctly, you need to install EASYDCP player.
http://www.dcinema.fraunhofer.de/en/veranstaltungen/ibc/player.jsp


Seemingly, you can also do this within After Effects. Details can be found at
http://groups.google.fr/group/openjpeg/browse_thread/thread/b195bbe7b784f39e

CHECK FILES BEFORE MOVING FORWARD.
 
Last edited:
PART 3
Step 3: convert TIFFs to JPEG-2000
INSTALL VERSION - THE OFFICIAL VERSION THAT I NEVER MANAGED TO GET TO WORK - HELP PLEASE
To install OpenJPEG. (I was never able to get the SVN version of the app to install correctly but I will describe how to do it anyway. Maybe someone can correct the errors.)

THIS EXPLAINS HOW TO INSTALL LATEST BUILD OF OPENJPEG USING SVN - SUBVERSION.

GET AND INSTALLED OPENJPEG FOR MAC OSX INTEL
To get the latest version of the OpenJpeg
In the Terminal application type

sudo su

and enter your user password

then type

svn checkout http://openjpeg.googlecode.com/svn/trunk openjpeg-read-only

At the end of a long list of events, the result is

Checked out ...

Go to the root of your user, using the cd command, type

ls

Hopefully you will find a folder called openjpeg-read-only

Then type

cd openjpeg-read-only

Then type

ls

A similar list to the one below should appear in the terminal

.svn Makefile doc
CMakeLists.txt Makefile.osx indexer_JPIP
ChangeLog OPJViewer jp3d
DllOpenJPEG.dsp OPJ_Validate jpwl
DllOpenJPEG.sln OpenJPEG.rc libopenjpeg
DllOpenJPEG.vcproj README.cmake libs
JavaOpenJPEG README.linux license.txt
LibOpenJPEG.dsp README.msvc mj2
LibOpenJPEG.dsw README.osx openjpeg.xcodeproj
LibOpenJPEG.sln clean.bat
LibOpenJPEG.vcproj codec

If so, you have downloaded the elements and checked that they exist

Installation
------------

If you have Xcode installed, you can double click on the file

openjpeg.xcodeproj

and in the window, click the BUILD button. This will compile the elements and place them in the right folder. (This did not work for me but it should)

If not, you can do it through the terminal.
Note: You will need to have root privileges in order to install the library in
/usr/include and /usr/lib directories.
The installation process is as simple as this :
1) Make sure that you are in the openjpeg directory which has the
make osx, make osxinstall and make osxclean files listed. See above

2) To build the distribution, type :

make osx

make osxinstall

3) Clean all files produced during the build process
make osxclean
------------------------

INSTALL VERSION B - This is not the right way but it worked for me.
Go to
http://code.google.com/p/openjpeg/downloads/list

and download the latest verion for mac. I used openjpeg_v1_3_osx.zip

Find the image_to_j2k file and copy it to the folder where your tifs are.

------------

To create JPEG 2000 files from the TIFFs

Copy the image_to_j2k to the folder that holds all the tiff files.

Open the terminal. Go to TIFF file folder.

for image in *; do echo $image; ./image_to_j2k -cinema2K 24 -i $image -o $image.j2c; mv $image.j2c <YOUR FOLDER PATH>; done


NOTE: THERE ARE MANY TYPES OF JPEG 2000 TYPE FILES. THE IMPLEMENTATION FOR CINEMA DCPs IS VERSION 3 or 4, WHICH DOES NOT SEEM TO BE THE SAME AS THE EXPORT VERSION YOU HAVE IN QT OF PREVIEW. BE AWARE. USE GOOGLE TO FIND OUT MORE.
 
Last edited:
PART 4
Step 4: Create a DCP compatible MXF file
Download the latest stable version of asdcplib from
http://www.cinecert.com/asdcplib/
I used version 1.5.32

To compile and install:

To unpack the file:

tar xzvf asdcplib-1.5.32.tar.gz

Then to build:

cd asdcplib-1.5.32
./configure --with-expat
make
sudo make install

The last step will ask for your password.

The script below will have the PROJ.video.mxf file name. This can be changed but the name must end with .mxf


Navigate in the terminal to the same level as the folder that holds the j2c files. Then type:

asdcp-test -v -L -c PROJ.video.mxf <FOLDER NAME THAT HOLDS ALL THE j2c FILES>

A PROJ.video.mxf should be created at the same level as the folder that contains the j2c.

I have not found a way to test this file. Just check that the size is about the same as the j2c folder.

Now that you have all the j2c files, I suggest you create a script in Automator to rename the j2c files to a simple file sequence such as 0000001.j2c etc
 
Last edited:
PART 5
Step 5: make all the necessary DCP files with opencinematools

Download opencinematools
http://code.google.com/p/opencinematools/

The official route that did NOT work for me:


Get the latest release (http://www.cinecert.com/asdcplib/asdcplib-1.5.32.tar.gz) and install. Change 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.



To install, open the terminal:

sudo su

chmod +x ./build/macosx/build.tcsh

then

./build/macosx/build.tcsh


--------------
Thanks to Terrence Meiczinger, he offers this working solution and also, thanks to Wolfgang Woehl for the install advise.

Duplicate the build.tcsh file, open it in textedit, delete the code in it and paste the code below. Rename the new file Makefile.

CC = g++
LIBS = -lm -lasdcp -lkumu -lcrypto
SRCS = ../../src/
BINS = ../../bin/

all : mkcpl mkpkl mkmap

mkcpl : $(SRCS)mkcpl.cpp
$(CC) -o $(BINS)mkcpl $(SRCS)mkcpl.cpp $(LIBS)

mkpkl : $(SRCS)mkpkl.cpp
$(CC) -o $(BINS)mkpkl $(SRCS)mkpkl.cpp $(LIBS) -D_FILE_OFFSET_BITS=64

mkmap : $(SRCS)mkmap.cpp
$(CC) -o $(BINS)mkmap $(SRCS)mkmap.cpp $(LIBS) -D_FILE_OFFSET_BITS=64

install :
install -v -p -s ../../bin/mkcpl /usr/bin
install -v -p -s ../../bin/mkpkl /usr/bin
install -v -p -s ../../bin/mkmap /usr/bin

In the terminal, navigate to Makefile you have created and type:
sudo su

then

make all
make install

then, in the mac finder use a utility like ONYX (see above) to reveal your mac's hidden files. You will discover a whole new world of folder. BE VERY CAREFUL WHAT YOU DO WITH THESE NEW FILES! Navigate to bin folder at /usr/bin/ and copy the files:

mkcpl
mkmap
mkpkl

to the folder where are creating the DCP elements. Sadly, the find function does not seem to work on these folders.

VERY IMPORTANT NOTE
Naming conventions are very important for DCPs, so I highly recommend that you read about them yourself and make informed choices.
http://digitalcinemanamingconvention.com/

Preparation of Sound files:
Dolby 5.1 24bit 48khz with 6 seperate mono wave tracks. (2.0 and 7.1 are possible)
Ref at 1khz: -20dbfs
Speed: 24fps
If reels are made, each reel must have 6 assoociated tracks
Wave files are named:
Reel Number + track L / R / C / Lfe / Ls or Rs
Each track must start with a 1khz beep with coresponding image at 48 frames before start of programme.
The audio and video must be exactly the same length.

Multiple reels

If yo want to name them video.reel1.mxf sound.reel1.mxf video.reel2.mxf sound.reel2.mxf. write in this order in the .cpl and .pkl .map and the dcp will automatically pick them up in this order. You can check it's working by downloading easyDCP player.

Subitles
The DCP subtitle standard is TI CineCanvas, which is a specific XML standard.
Currently, Belle Nuit (www.belle-nuit.com) or MacCaption (www.cpcweb.com)
Below is a partial sample of a CineCanvas "subtitle script". (the subtitles are in Japanese). Courtesy of www.thedigitalcowboy.us



Subitile timecode is based on reel length.


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--

*** XML Subtitle File ***

-->
- <!--

*** Created By CANVASs Co.,LTD. ***

-->
- <!--

*** Wednesday, February, 18, 2004 ***

-->
- <DCSubtitle Version="1.0">
<SubtitleID>B396FFBC-75CB-4738-AAB1-2BC7E10D9B94</SubtitleID>
<MovieTitle>Kamen Test</MovieTitle>
<ReelNumber>1AB</ReelNumber>
<Language>Japanese</Language>
<LoadFont Id="theFont" URI="Font/FANRG7BFCONV.TTF" />
- <Font Id="theFont" Color="FFFFFFFF" Effect="shadow" EffectColor="FF000000" Size="60">
- <Subtitle SpotNumber="1" TimeIn="01:00:42:125" TimeOut="01:00:43:177">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??</Text>
</Subtitle>
- <Subtitle SpotNumber="2" TimeIn="01:00:46:219" TimeOut="01:00:47:167">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??!</Text>
</Subtitle>
- <Subtitle SpotNumber="3" TimeIn="01:00:54:010" TimeOut="01:00:55:031">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??</Text>
</Subtitle>
- <Subtitle SpotNumber="4" TimeIn="01:00:58:052" TimeOut="01:00:59:021">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??!</Text>
</Subtitle>
- <Subtitle SpotNumber="5" TimeIn="01:01:05:010" TimeOut="01:01:05:219">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">???!</Text>
</Subtitle>
- <Subtitle SpotNumber="6" TimeIn="01:01:06:219" TimeOut="01:01:07:208">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??!</Text>
</Subtitle>
- <Subtitle SpotNumber="7" TimeIn="01:01:09:010" TimeOut="01:01:10:156">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??! ??!</Text>
</Subtitle>
- <Subtitle SpotNumber="8" TimeIn="01:01:11:052" TimeOut="01:01:12:219">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">???! ??!</Text>
</Subtitle>
- <Subtitle SpotNumber="9" TimeIn="01:01:13:125" TimeOut="01:01:14:135">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">(??)?? ??</Text>
</Subtitle>
- <Subtitle SpotNumber="10" TimeIn="01:01:17:115" TimeOut="01:01:18:115">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">???</Text>
</Subtitle>
- <Subtitle SpotNumber="11" TimeIn="01:01:20:073" TimeOut="01:01:21:083">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">??…</Text>
</Subtitle>
- <Subtitle SpotNumber="12" TimeIn="01:01:25:188" TimeOut="01:01:29:198">
<Text HAlign="center" HPosition="0.0" VAlign="bottom" VPosition="13.00">???? ????…</Text>




To create the DCP: (copy from the Chris Perry blog)
This step has five substeps, each of which generates one or more of the files needed for the DCP. Naming conventions are very important in DCP land, so I highly recommend that you read about them yourself and make informed choices. When you see DCPFULLNAME below, that's shorthand for what I used, which was the mouthful:

TOWER37_FTR_F_EN-XX_US-XX_51_2K_ST_20100212_OV
ICARE_SHR_C_FR-EN_FR-AA_51_2K_20100423_OV

Command A (create a video MXF file from the folder of J2K files):

asdcp-test -v -L -c PROJ.video.mxf FOLDER_OF_J2KS

Command B (create an audio MXF file from the six wavs):

asdcp-test -v -L -c PROJ.audio.mxf -l 5.1 left.wav -l 5.1 right.wav -l 5.1 center.wav -l 5.1 sub.wav -l 5.1 surrLeft.wav -l 5.1 surrRight.wav

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 DumDumFilms --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 DumDumFilms PROJ.video.mxf PROJ.audio.mxf PROJ.cpl.xml PROJ.pkl.xml


I used a bit of shorthand above since I did not identify enclosing folders. I suggest that if you make a DCP this way, you use temporary folders for all the inputs (and the results of steps 1-3), then create a finalDCP folder which you populate with only the files that will be part of the eventual DCP itself (namely, the 2 mxfs and the 4 XML files that come from step 4).

Command D may take sometime to produce. Be patient.

You should end up with 6 files that look something like:
VOLINDEX.xml
PROJ.video.mxf
PROJ.pkl.xml
PROJ.cpl.xml
PROJ.audio.mxf
ASSETMAP.xml

Some quick notes:

* It is important that you check your XML files to make sure the file paths don't contain any incorrect information: if you aren't careful during step 4, your file paths in the XML may be incorrect! Here's what one of my entries looks like in my final ASSETMAP.xml file as an example: file:///tower37_complete3.video.mxf
* I don't know what happens if your audio and video durations are different, so I was careful to make sure mine were not. Check them in the CPL (the tag is ).
* Work with a small movie file for starters, a minute or less, until you get the steps ironed out. Then move to your full film.

CONGRATULATIONS:
YOU HAVE MADE A DCP ...

Check it first using EasyDCP then ...

Step 6 : Taking the files to the Projectionist.

DCP servers are often either based on Linux so it is best to format the disk that you will take to the projectionist in .ext3. If not, NTFS formatted disks should be read. Check with the projectionist beforehand. You can find opensource NTFS and ext3 solutions on the web.
http://macntfs-3g.blogspot.com/
http://www.paragon-software.com/home/ntfs-mac/
http://www.paragon-software.com/home/extfs-mac/
 
Last edited:
Attached is the above doc with the right tabulations for the command lines
 
Christopher: First I would like to say thanks for this Mac "guide" and congrats on your first DCP! I've quietly followed the Reduser thread on the OpenCinemaTools for a while.

"Each track must start with a 1khz beep with coresponding image at 48 frames before start of programme. The audio and video must be exactly the same length."

The few DCP's i've successfully made had the audio out of sync (video came before the audio), so I wonder if the above have something to do with this?

Do you mean that the first 2 seconds (48frames) of each audiotrack should have a 1khz beep... and what exactly do you mean by "a coresponding image"?

It seems weird to me that the first 2 seconds of your file should be be without useable sound, but i could be mistaken.

English is not my primary language, so excuse me if it's straight forward :)

Thanks in advance!
 
To my knowledge, the inclusion of trailing beeps is NOT part of the DCP format obligations, but part of the distribution master (DCDM). Every reel of a DCDM schould have academy '2 pop' leaders - but not the DCP aimed at presentation!

The cinema servers have no means to detect and omit trailing beeps in DCPs, they would consider them to be 'normal' program and play them - unless 'masked out' by a suitable playlist.

You can find a lot of useful information concerning mastering aspects here:

http://www.edcf.net/articles.html
http://www.edcf.net/technical_support.html

and especially this one:

http://www.edcf.net/edcf_docs/edcf_mastering_guide.pdf


- Carsten
 
Thanks for the links Carsten!

From the mentioned document it seems the playback of the leader and trail can be adjusted in the CPL:

"Often the incoming .tiff files will include the head leader
(SMPTE is creating a standard for the digital cinema leader)
and a tail leader. It is important that one include both when
making the track files. This is true for both sound and picture
track files. It is not a significant impact on the track files size
and the CPL will allow one to start playing track files after
the header leader. The header leader will include the “2 pop”
and this is sometime helpful in verifying audio sync in the
final QC process."
 
Christopher,

I've few questions.

Would the image after multiple conversion from QT -> PNG -> Tiff -> Jpeg 2000-> MXF(no loss since its a wrapper) wont have generation loss or image degradation and even banding?

Interms of DCDM, with few friends in QUBE heard that first frame will skip. Is it true?

Rather than these steps and image degradation if any, would be nice to use EASY DCP+ which is cost effective and not free definitely!

Whats your thought about this!
 
Christopher,

I've few questions.

Would the image after multiple conversion from QT -> PNG -> Tiff -> Jpeg 2000-> MXF(no loss since its a wrapper) wont have generation loss or image degradation and even banding?

Interms of DCDM, with few friends in QUBE heard that first frame will skip. Is it true?

Rather than these steps and image degradation if any, would be nice to use EASY DCP+ which is cost effective and not free definitely!

Whats your thought about this!

All I can say is that it has worked for me. The workflow is based on the opensource apps available. PNG and TIFF are not lossy codecs as a rule.

I added a beep at the beginning of my DCP for sync issues as it is very hard to make sure that everything is sync.

EASY DCP is cost effective when you make a living out of it. I do a DCP every 3 years.
 
Thanks Christopher. Great article and links. Makes me want to try this out.

Any particular reason why you go through .PNG files instead of using ffmpeg to produce Tiffs directly from QT?

One suggestion: your commands use the * wildcard, which will take anything that happens to be in that directory. Includinhg sub-directories. You could replace it with *.tiff, *.png, etc. to make sure you only get the right files.
 
I have been reworking the above tutorial.

Concerning the installation of ImageMagick

I could only install ImageMagick when I was a ROOT user.
I also had to install the ImageMagick many, many times before the ./configure allowed the installation of the Tiff operation. Read the end of the configure log to see if the installation of the tiff to see if the installtion is available. What I have found is that if the tiff plug in is not installed, ImageMagick will do the job and even export a file with a .tif, except that the file is not a tiff but a png.
I have not found a reason why the installation is unstable for me but to help things along, you can always install the opensource tiff library at

ftp://ftp.remotesensing.org/pub/libtiff/

Always check each step with a single file before launching the rest.
 
Lastly, i suggest that you download GraphicConverter as it is able to open .j2c files (amongst many other).
 
Back
Top