Please login or register. January 24, 2019, 02:18:51 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Terrence Meiczinger

Pages: [1] 2 3 ... 38
OpenDCP / Re: MPEG2-Interop still supported ?
« on: June 16, 2018, 10:08:16 PM »
Yes, OpenDCP still supports MPEG2. However, it had not been tested for several releases.

Digital Cinema Packages / Re: 3D stereoscopic DCP bitrates
« on: June 23, 2017, 09:00:34 PM »
While each "frame" might still be read sequentially by the digital server, they must be processed twice as fast. A 24fps 3D picture needs to process the content at 48fps in order to be able to get the images to to projector at the same time. So, rather than think of it as left/right, think of it as single stream of data which gets processed into separate channels. The stream can't exceed 250mb/s (500mb/s for newer systems) and the frame rate or number of channels within it isn't really relevant.

OpenDCP / Re: Sound in and out of sync with Sony projectors
« on: May 24, 2017, 09:35:03 AM »
I seem to recall (from a few years ago) the standard JPEG2000 export in Resolve does not use EasyDCP and is not DCI compliant. This may not be the case anymore, but something to consider.

OpenDCP / Re: Sound in and out of sync with Sony projectors
« on: May 23, 2017, 04:32:32 PM »
1. Do you know the make/model of the digital server?
2. Your bandwidth is way higher than you need and some servers (especially older DoRemi's) can have issues with that. You only need around 75mb/s for 2K 24fps. This is the most common source of sync issues that I have seen.
3. DaVinci Resolve may not be creating DCI compliant J2K images.

OpenDCP / Re: add xml digital signatures
« on: May 15, 2017, 02:12:18 PM »
It allows the server to validate the integrity of the DCP and the identity of the creator. In most cases, especially when not using KDMs it is unnecessary.

Digital Cinema Packages / Re: Audio Format Metadata
« on: April 24, 2017, 11:02:36 PM »
SMPTE 429-16:2014 is about OPTIONAL metadata intended for human readable consumption. This is for content management purposes, allowing sorting, searching, filtering, cataloging, etc. In the future, it will reduce the role of the Digital Cinema Naming Convention. The server does not use it to determine the number of channels in the audio format. The truth is in the MXF file and that is what the server will use. Check your MXF files in EasyDCP Player. It may be there is an issue with the MXF file and some servers can deal with it, but the newer ones are more strict about it. There could be a bug in OpenDCP or the server itself. It wouldn't be the first time for either. Unfortunately, without access or testing time on an 850 or debug logs, there isn't much to go on. If you can get more information, that would be helpful.

Digital Cinema Packages / Re: Audio Format Metadata
« on: April 23, 2017, 06:59:03 PM »
The servers do no parse anything from the title or name. The MainSoundConfiguration and other Meta-data are currently optional. The information regarding the audio format is contain within the MXF file.

OpenDCP / Re: Title Generator - Feature Request
« on: April 14, 2017, 03:07:07 PM »
There is no specification for title naming and the DCNC in not a standard. It's meant to be human readable only and not for consumption by servers, so it should never be cause of a DCP failure. Adding the NULL option makes sense tho.

General Discussion / Re: What is Dolby Atmos
« on: April 14, 2017, 02:56:54 PM »
No, perhaps when multi-dimensional audio is a full spec.

General Discussion / Re: What is Dolby Atmos
« on: April 05, 2017, 11:49:25 AM »
This is out of the scope of OpenDCP at this point. I don't have an ATOMS system to test against and I'm not even sure the specs are openly published.

OpenDCP / Re: Best place for 23.976 to 24 conversion for DCP
« on: March 30, 2017, 02:39:36 PM »
A DCP just has a number of frames and a frame rate. If you export your original material at 23.976 and create the DCP at 24fps, the number of frames stay the same, but it is played back at a slightly faster rate and will have a shorter duration. To compensate, you need to speed up your audio and adjust the pitch accordingly.

OpenDCP / Re: Chinese Translation
« on: March 29, 2017, 12:22:43 PM »
OpenDCP uses the Qt framework and any language that supports can be added. You need to create the translation file which then can be imported and added to the build process.

OpenDCP / Re: Best place for 23.976 to 24 conversion for DCP
« on: March 29, 2017, 12:17:48 PM »
I think most people just export the frames as 23.976 and adjust the audio to compensate.

OpenDCP / Re: Mastering in Rec. ITU-R BT.1886
« on: March 29, 2017, 12:10:42 PM »
I have not had a chance to dig into this and what it would take. If it's a matter of adding an additional transfer matrix, then it shouldnt be too difficult. If an entirely different transfer function than it becomes a bit more work.

OpenDCP / Re: opendcp_mxf audio
« on: March 10, 2017, 07:46:21 AM »
The wrapping is based on the MXF files. It will auto-detect how the MXF files were created and generate the DCP accordingly.

Pages: [1] 2 3 ... 38