Please login or register. October 23, 2017, 09:25:12 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 - hdvprojection

Pages: [1] 2 3 ... 14
OpenDCP / Re: openDCP crashes
« on: May 10, 2017, 02:17:32 PM »
I forgot to follow up on this in-thread. Adding the switch "-depth 8" in the mogrify command resolves this issue. For example:
Code: [Select]
mogrify -background black -gravity center -depth 8 -extent 1998x1080 *.tiffThanks for your help Terrence.

Digital Cinema Packages / 7.1 Channel Mapping - Feature Request
« on: April 26, 2017, 01:56:04 PM »

Can the next version of OpenDCP either place the rear surrounds on channels 11 and 12 by default (with mutes in 7 through 10) or give the user the option to decide where these channels should go? I realize that there is evidently no effective "standard" for this beyond the first six channels, but the recommendation from Dolby and others is to have HI/VI in channels 7 and 8. Indeed, most theaters' sound systems are set up to expect the Dolby-recommended layout, and 7.1 DCPs created on OpenDCP do not play properly without some tinkering. Thanks.

Digital Cinema Packages / Re: Audio Format Metadata
« on: April 25, 2017, 07:48:38 PM »
I have some clarification: firstly, in case there was any confusion, ingest and Playback are not a problem. These are fully functioning DCPs. Secondly, the issues we are seeing seem to reside mostly at the TMS/LMS level. Some of these systems, like the Hollywood Software TCC3, fetch higher-level playback instructions from the CPL (higher than, say, first and last frame.) Among these is the audio format.

So, when the theater staff is composing their feature SPL, and this playlist contains DCPs of differing audio formats, the TCC3 will automatically place the appropriate format cues wherever needed.

I suppose, then, what we're really discussing here is a feature request. Can writing these optional parameters to the CPL be included in a future version of opendcp? Thanks.

Digital Cinema Packages / Re: Audio Format Metadata
« on: April 24, 2017, 07:21:05 PM »
Based on this page, I need to add the following lines to the CPL:
Code: [Select]

I'm drawing a blank as to how to do that, however. I believe I need a decent XML editor (will just a basic text editor like Mousepad do the job?) and then I need to edit the CPL length within Assetmap by the above number of characters. Do I need to recalculate hashes as well?

Also, where would the lines above go, precisely? Would it be under MainSound, at the same level as EditRate, IntrinsicDuration, etc.? Thanks.

Digital Cinema Packages / Re: Audio Format Metadata
« on: April 23, 2017, 07:10:36 PM »
So, what exactly am I doing wrong? We tested several of our spots, and compared them to lab-issued trailers. The meta:MainSoundConfiguration tag appears to be missing from our DCPs.

Digital Cinema Packages / Audio Format Metadata
« on: April 22, 2017, 03:34:55 PM »
How do I add the audio format of my DCPs to the CPL metadata. Several of the systems our exhibitors use ignore the name (they don't bother parsing out the "20", "51" or "71") and they cannot or will not simply detect the number of streams. They are looking for direction from the CPL, evidently a line like "cpl-meta:MainSoundConfiguration".

I'm not seeing options for this in OpenDCP, unless it has something to do with adding digital signatures. Is that it, or do I have to manually edit the CPL? If the latter, how would I do that?

We'd been led to believe that the Dolby 850 would automatically detect a 5.1, 7.1 or Atmos DCP and switch formats accordingly. I'm not so sure anymore. Please advise. Thanks.

General Discussion / Re: What is Dolby Atmos
« on: April 13, 2017, 02:22:35 PM »
Is Atmos integration anywhere on the horizon, perchance?

General Discussion / Re: What is Dolby Atmos
« on: April 04, 2017, 02:26:11 PM »
I've been given an Atmos-encoded audio MXF file, along with an XML that - I assume - carries the "zoning" instructions for the processors. These came along with the source video, the insinuation being that we would handle the picture part of the equation. My guess is that there's no way for me to package these using OpenDCP, but I was hoping for verbal confirmation. It doesn't seem feasible to me that I would create a standard DCP using their MXF and mine, and then just drop the extra XML in and have it work like magic.

Any suggestions? I'm thinking this project is going to land in Fotokem's lap.

Digital Workflow / Re: Getting the DCP onto an appropriate drive...
« on: February 04, 2017, 03:58:36 AM »
I'm re-reading this thread and some of my contributions, which I feel are unclear. So...

Many, if not most, or even close to all TMS/LMS systems at theaters are Windows-based. Many of these do not have the capability to read Ext2/3 out-of-the-box (I think Hollywood Software's TCC3 does, and probably Arts Alliance). This is the reason that the labs (Fotokem, Deluxe, Technicolor, etc.) send movie trailers out on thumb drives formatted NTFS, not Ext2/3. Think about this: they get the same 4GB or 8GB drives we do from the store or wherever, which are FAT32 when you buy them. They go to all of the trouble of re-formatting these drives, but NOT to Ext2/3. They go with NTFS... Why?

This has nothing to do with DCI specs, but rather with the theater/library management software. I'd be shocked to find out if there are any DCI requirements for TMS systems; they just have to be on the media and/or management network and they can do what they like. At most multiplexes the TMS/LMS is the main point of contact with the servers. Whatever you're producing will most likely be ingested from there. Make your drives NTFS-friendly, especially if we're talking about ads, trailers, shorts, etc.

With features I think it's a more fair point to make that Ext3 is the way to go. But then, the theater staff deal with features differently, too. Trailers they want to ingest and schedule at one sitting. Features, meanwhile, they plug in to ingest and then walk away for a few hours, going about their business.

OpenDCP / Re: OpenDCP adds pop at tail of audio
« on: August 23, 2016, 03:05:45 PM »
Has no one else experienced this?

OpenDCP / OpenDCP adds pop at tail of audio
« on: August 19, 2016, 04:08:18 PM »
I tried searching to see if anyone else had posted about this, but didn't see anything. I'm going back over all of my old DCPs, specifically the ones with 5.1 audio, and I'm finding - randomly - that  OpenDCP is adding a one or two frame long pop at the tail of each audio channel, always just the bottom of the waveform. Please see the attached jpegs. The pop is not present in any of the source WAVs.

Based on the common denominators of the DCPs exhibiting this flaw, I suspect it is related to duration adjustment at the packaging stage; they all had audio MXFs which were a frame or two longer than the picture MXF. Is there anything to be done about this? It looks and feels like a bug. Thanks.

General Discussion / Reds after J2k conversion
« on: May 17, 2016, 04:43:39 PM »
Has anyone else noticed a particular weakness in JPEG2000 with the color red? Maybe I'm imagining it, but whenever I have a spot or slide with an abundance of red (especially with a different color text overlay), I'm pretty much forced to max out the image bandwidth to avoid compression artifacts. I'd prefer to stick with OpenDCP's default 125MB/s, partly because of network bandwidth limitations, but the slides and ads with red are killing that. Any thoughts or experiences with this?

OpenDCP / Re: openDCP crashes
« on: January 19, 2016, 03:24:03 AM »
I don't know if ffmpeg or mogrify try to optimize the color depth if they can. If you can get me one of the troublesome frames, I can investigate.
It's mogrify that does it. I just watched it shrink all of the pure black slides down from 108kb down to about 5kb each. My guess is that OpenDCP either does not like the color space switch, or conceivably it doesn't like the very small file size (as in, it starts tripping over itself dealing with very, very small images.) No idea. Any thoughts?

OpenDCP / Re: openDCP crashes
« on: September 24, 2015, 05:41:41 PM »
Can you do just the mostly black images by themselves? What is the color depth? I noticed the image 000002.tif giving trouble in the previous crash was:

20150509014507 | DEBUG | opendcp_decoder_tif.c:69                   | opendcp_decode_tif             | opening tiff file tiff/000002.tiff
20150509014507 | DEBUG | opendcp_decoder_tif.c:85                   | opendcp_decode_tif             | tif attributes photo: 1 bps: 1 spp: 1 planar: 1

This would indicate the image is not RGB, but probably grayscale. Could you check your files and confirm?

I did, in fact, try to convert just the black frames, which also crashed. Or rather, I selected the frame from which to start (let's say #33,776 onwards) within the same tiff folder. I will try testing out just a small sampling starting with the problem frames, maybe a hundred or so, and I'll report back.

As far as the color depth changing, I'm not sure how that would happen. I always extract frames with ffmpeg, using the "RGB" switch, since almost everything I've ever worked with is YUV. Then I use mogrify (Imagemagick) to place the frames on a "compliant" flat or scope background. I have to assume that ffmpeg is going to extract all of the frames in its task the same. Could mogrify be altering something?

OpenDCP / Re: openDCP crashes
« on: September 24, 2015, 01:09:23 AM »
Happening again, and only (or mostly) on black images. As a matter of fact, I had it converting a folder full of about 35,000 tiffs (24+ minute short), and it got all the way to the end of the fade-to-black at the start of the end credits, and it refused to go any further. Why would black slides be an issue? Of course, most movies and shorts start with black, so you can imagine how far I've been getting on most projects...

Pages: [1] 2 3 ... 14