Results 1 to 15 of 122
Thread: DCP Trailer Q & A
02-05-2013, 07:33 PM #1
DCP Trailer Q & A
Bendermac, I dont know why make the untouched LPCM 6 channel wave files into dts, but, to each their own.
Yes, I do have Iron Man 3 Trailer 1 LPCM 5.1 track.
02-06-2013, 08:11 PM #2
02-07-2013, 12:23 AM #3
Bendermac, good reason, I understand. I will just keep doing they way I've been doing. As I dont have a HD A/V reciever. D4rkshadowz, As for Iron Man 3 trailer, I will share that soon. I dont have Man of Steel. Which version of Man of Steel Trailer are you interested in? Its up to 3.
02-07-2013, 04:18 AM #4
djaxle, how big are the source files? if it isn't much to ask for, could you please share a trailer in the original format for testing?
men of steel full trailer would be nice, if you can get your hands on it.
thanks for your efforts
02-07-2013, 01:37 PM #5
I haven't gotten around to testing the playback as I have a couple trailers from 3D blu-ray discs with the left and right video.
I imagine playback would have to be through something like Stereoscopic Player or similar that is familiar with 3D formats (especially uncommon MKV 3D formats).
I would also love a copy of the original format of the 3D trailer to do some test conversions to 3D.
Netload can support large sizes but more or less are preferred for Premium users.
ZippyShare has fast speeds but the file size limit is 200mb so splitting them into small .RAR files would be quite excruciating.
Perhaps MicroSoft's "SkyDrive"?
02-07-2013, 06:01 PM #6
DCP Trailer Q & A
I'm not a professional and am not an expert with the information and the tools I share in DCP converted trailers. I will share information and hope others will share back with what and how they convert DCP trailers for consumer playback on home media streamers/players. I've been searching for several years for a Mac OS X way to convert DCP trailers and I finally found a method that I will share here. Please do not ask me to share my source files.
Here's some info first:
DCP- Digital Cinema Package
DCI- Digital Cinema Initiative
MXF- Material Exchange Format (a wrapper in a container) It contains essence files. The DCP has 1 video.mxf which is the jpeg2000 video track and the audio.mxf is an audio track in OP-Atom broadcast 6 channel wave (LPCM).
More info here:
I nolonger use MXF4mac by Hamburg Pro Media and their plug ins:
MXF4mac MXF Import and Codec4mac.
Codec4mac includes the J2K Codec and AVC-Intra Codec plug ins for Quicktime Pro 7.6.6. (Mac OS X 10.8.x)
Once you have unwrapped the essence out of the audio.mxf and video.mxf, your free to find better tools to convert.
An audio.mxf track can be unwraped of its essence with AmberFin MXF Desktop V1_3_0 to a LPCM .wav container. Doremi CineAsset 5.x will unwrap the video.mxf essence to a jpeg2000 j2c file image sequence.
In Wave Editor on Mac OS X, I take the LPCM 5.1 and export out to 6 mono aiff files and then drag them into DTS-HD Master Audio suite encoder to make a DTS-HD MA 5.1 track and still keep the original untouched LPCM 5.1 track remuxed into a mkv container with mkvtoolnix.
Using Doremi CineAsset 5.x, I take the video.mxf and export it as jpeg2000 image sequnce. (j2c files).
Then import that into Adobe Premier Pro CS5.5. I make sure to use nfords DCI Converter plugin to correct colorspace. (Rovi's Totalcode 6.0.3 plug in with Adobe Premier Pro CS 5.5/CS6 for Windows 7 64-bit Only will do the job as well). Also using nford's FREE j2k plug in and DCI converter plugin (http://fnordware.blogspot.com).
On Windows, you can play a (unencrypted) DCP with Stereoscopic Player. There are some Mac OS X DCP players, but they are limited to 15 seconds playback as trial programs and are way too costly for most consumers to buy. Calibrated[Q] isn't compatible with DCI DCP MXF files.
EasyDCP Player: http://www.iis.fraunhofer.de/en/bf/b...dcpplayer.html
Stereoscopic Player: http://www.3dtv.at/Index_en.aspx
Last edited by djaxle; 05-27-2013 at 12:53 AM. Reason: updated info
02-08-2013, 12:34 AM #7
02-09-2013, 11:48 AM #8
Long time no see
Something I noticed is that your encodes of the trailers are 1920x858. I think they're supposed to be squished down to 1920x800 (if you notice people are slightly elongated) sort of like the way anamorphic DVD's are supposed to work...
Thanks for the trailers though! Keep up the awesome job man!
02-09-2013, 01:19 PM #9
I may not be perfect, but I looked at the original DCP and its for example, 2048 x 858. So, I put it as 1920 x 858.
02-09-2013, 04:11 PM #10
Which would make the original aspect ratio 2.39 and then 1920x858 is 2.24...
So actually it should be something like 1920x804 to be the same aspect ratio as the original or close to it. Otherwise it's vertically stretched.
02-09-2013, 05:38 PM #11
It's hard to notice. The only thing I really noticed it on was the WB logo of all things. But then when I did a side by side comparisons I could tell the difference. That and obviously the size of the bars being smaller. Especially on a 110" 2.40:1 framed screen.
But the fix was super easy. I just used MeGui to do a 2.40:1 encode. It's just so freaken nice not to have to put up with mono sound and a watermarked picture for these trailers lol...
02-09-2013, 08:51 PM #12
Any chance you'd still have the audio for Star Trek or Pain & Gain. The mono sound on those trailers is KILLING me!!! Still can't believe this is becoming the norm. It was like one GIANT step forward with Quicktime HD and then suddenly a million giant steps back within the last year
02-11-2013, 07:07 PM #13
if ffmpegx could do the XYZ 12 color conversion and transcode to H264 for free on Mac OS X with a GUI tool.
Last edited by djaxle; 02-21-2013 at 08:46 PM.
02-16-2013, 12:48 PM #14
I learn something new, from th avid forums:
Although, a volume index isnt always needed.
There are two Print resolutions for D-Cinema, 2k (2048x1080) and 4k (4096x2160), while most projectors are native 2k, they can downgrade and display 4k, likewise 4k projectors will be able to upcode 2k to 4k.
The image must fit inside the above resolution. The Common Theatrical Formats are for a 2K projector are 1998x1080 is a (1.85:1) Flat Print , and 2048x858 is a (2.39:1) Scope print. Scope will use the whole screen, while Flat is Pillar Boxed.
There are only two allowable frame rates 24fps and 48fps (48fps is restricted to 2k images only)
The color encoding must be in X'Y'X' color space, with 12 bit color (that's 36bits, in the MSwindow's per pixel notation!)
Once you have your image setup as above then it needs to be encoded in MJPEG200 format. Quite simply each frame is independently encoded as a JPEG2000 image file
This Video Only Stream then gets put in a MXF wrapper, and is now considered a 'Track' file
Audio is PCM (.wav format) 24-bit at 48.000 kHz or 96.000 kHz that is also put in a 'Track' file. Up to 16 Channels of audio per Track to be used concurrently. Different Langues must be in different tracks.
A Video Track, and A Audio Track ( ie only one language), get grouped together into a unit called a Reel. Tracks can be reused in multiple Reels (ie, two reels use the same video, but different audio/language tracks).
A group of Reels, linked together into a Composition (Movie, Trailer, Ad, etc). The Composition is defined in a XML document called a CPL (Composition Play List). The Reels are defined in this file too.
Every File has a UUID in its meta data. Along with the CPL, you must have a PKL file (Packing List) which is another XML doc, that lists every file's UUID, and a BASE-64 SHA-1 Hash of the file to detect any corruption or error in the file that occurs after "Production".
Now At this point you have a Movie/ad/trailer as a group of files. However this is still not enough. You have to put this on some type of media the D-Cinema can read, HardDrive, CD, DVD, etc. This dependant on the media its going on, and may have to change as you move the files around.
It is likely (except for very large Hardrives) that the file will not fit on a single CD. So you have to make another XML called a Volume Index File. It must appear on the root of the file system and be named "VOLINDEX.xml". You must have this file even if there is only one Volume.
You must also create a Asset Map, This is an XML file that lists all the files on the volume with there Real Filesystem path, The Size, any offset, and the UUID of the file, and which Volume is is on. This is what links the UUID's that the Projection system uses to the Physical files on the disk. It must be on the root of the filesystem and be named "ASSETMAP.xml".
Now you have a DCP (Digital cinema Packaging) that your Projection system should read and understand just like any other movie.
02-18-2013, 09:59 PM #15
I've noticed somewhere that some was using an old MKVtoolnix (2.9.0) for their work.
MKVtoolnix has updated to 6.0.0 and it is advised to update to that version.
Millions of bugs, fixes and updates have been made since 2.x versions.
The Fast and the Furious 6 trailer doesn't have the FPS defined in the downloaded matroska container (the MKV file).
So when I converted it to 60fps (using AviSynth and InterFrame), I got the wrong results for the video.
The video looked okay, but when synched back with the audio it was incorrect.
The audio wasn't the issue; the video was working off arbitrary figures for the FPS.
I tried so many things to try and get the proper frame rate.
I discovered that the work I did on two machines were very different.
One machine I had convert the trailer to 60fps in 480p while the other machine converted the trailer to 60fps in 720p.
The 480p had turned out proper while the 720p had massive synch issues with the audio.
Running the downloaded trailer through eac3to gives a warning about there not being any FPS values.
Doing a "-check" on the MKV file with eac3to shows this in the log...
command line: eac3to "F:\Work\Trailers\Fast Furious 6 Trailer 1.mkv" -check
MKV, 1 video track, 2 audio tracks, 0:02:34, 24p
1: h264/AVC, English, 1920x804p
"Fast and Furious 6"
2: DTS Master Audio, English, 5.1 channels, 24 bits, 48kHz, -703ms
(core: DTS, 5.1 channels, 24 bits, 1509kbps, 48kHz)
3: RAW/PCM, English, 5.1 channels, 24 bits, 48kHz, -708ms
[v01] The video track doesn't contain framerate information. <WARNING>
[a03] Extracting audio track number 3...
[a02] Extracting audio track number 2...
[a03] Reading RAW/PCM...
[a03] Swapping endian...
[a03] Remapping channels...
[v01] Extracting video track number 1...
[v01] Writing new framerate "24fps" to bitstream.
[a03] The original audio track has a constant bit depth of 24 bits.
Video track 1 contains 3631 frames.
eac3to processing took 6 seconds.
However, it is not frame-accurate since the FPS values are missing. This will be apparent when doing any conversions or editing.
I indexed the downloaded MKV file with FFMS2 to use with AviSynth, and when I defined the FPS in the script, it still returned incorrect results.
Once I remuxed the h264 stream into a new MKV file with the FPS defined, it turned out properly with the audio in synch.
This is the proper way to fix it.
Please, no one say that I can convert the audio to stretch or squish it to match the converted video.
That is wrong.
This is due to the downloaded container not having the FPS info.
The MKV had to be remuxed into a brand new MKV file with the FPS info defined in the "format specific options" when the video is highlighted. In this was the simple "24p". (24000/1000progressive)
Which is what I did on the machine doing 480p.
I had forgotten that step on the machine doing the 720p which gave me incorrect encodings.
Remuxing with defined FPS fixed the proper frame rate for the 60fps conversion. The audio was in synch.
I would suggest for future uploads, please make sure to add the FPS info in the MKVtoolnix tab (when using mm.exe) to allow for frame-accurate editing for anyone who wishes to do anything. For audio, especially.
The Fast and the Furious trailer was in 24 FPS even, so just 24p would be selected. (24000/1000)
For all other trailers that are actually 23.976, you would select "24000/1001p"
P for Progressive.
I believe this was also the issue for some people saying they had audio synch issues as well.
Untested though for their circumstances, so they would have to remux the video and define the FPS themselves.