my profile | my password | search | faq & rules | forum home

» Film-Tech Forum ARCHIVE   » Operations   » Digital Cinema Forum   » DCP-o-Matic: Problem creating 5.1 VF (Page 1)

This topic comprises 2 pages: 1  2

Author Topic: DCP-o-Matic: Problem creating 5.1 VF Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 05-27-2016 11:59 AM                        I am creating a DCP that will play in two theaters: we can do ProLogic matrixing from a 2.0 TV mix in one (using a DMA8+), but not the other. The source file is 2.0. I've made an OV DCP from the source file, and am now trying to make a VF containing audio that uses the "upmix to 5.1" feature, to play in the non-ProLogic house. After rendering the OV, I start a new project, import the OV DCP as a folder, and check "refer to existing DCP" in the image tab on the content side, but not the audio. On the DCP side I change the processor option in the audio tab to 5.1 upmix A, and then, without changing anything else, tell it to render the DCP. It then says "Encoding image data" (which is odd, because it shouldn't have to touch the image data - I'm just trying to add new audio to play with an existing MXF video file), creates a PCM MXF file in the DCP project folder, which grows to a certain size, and then DCP-o-Matic hangs forever (still saying "encoding image data"). I've just tried it with an 87-minute DCP, and it's now been hung two days, and has not tried to write anything to the MXF file for well over a day (going by the "last modified" stamp in the file properties). It only took 13 hours to render the OV. I've also tried this with two other (much shorter) DCPs and got the same result, so I'm not dealing with a specific issue with this source file or DCP. I'm using version 2.7.4 under Ubuntu 14.04.4 LTS, 64-bit. Am I doing something stupid, or have I hit a bug with DCP-o-Matic? Thanks in advance.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 05-27-2016 01:06 PM                     MXF handling has been improved in recent versions, and VF is still fairly new. Try again with the current 2.8.4 release. You are right that it should have worked the way you describe it. You can use the trim feature to test small segments of the footage so you don't have to wait so long for it to complete. - Carsten  |  IP: Logged Manny Knowles "What are these things and WHY are they BLUE???" Posts: 4247 From: Bloomington, IN, USA Registered: Feb 2002 posted 05-28-2016 12:58 PM                     Definitely test out that up-mix in its entirety before releasing that DCP. I got unacceptable results using the up-mix feature. Rampant steering of sibilants into the surrounds. This problem was not observed when the 2.0 was decoded by our DMA8plus, so I'm not inclined to blame the content. Not sure what (Windows) version of DCP-o-Matic I was using, but it was within the last 6-8 months.  |  IP: Logged Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 05-28-2016 01:33 PM                        Agreed completely - it's not as good as what a DMA8+ or the matrix processor in the AP20 can do, the main issue being, as you say, higher dialogue frequencies bleeding into the surrounds. However, in the house I want to play this DCP in, it's better than the echo you get from playing a 2.0 TV mix as is, especially for someone sitting significantly off-center. And the movie I'm dealing with has very little dialogue, so for this particular title it should be OK. Haven't gotten around to updating DCP-o-Matic on the machine I use for DCP rendering (it's not normally connected to the Internet), but am hoping to in the next day or two - thanks to Carsten for the suggestion.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 05-29-2016 06:29 AM                     I love the DTS Neo:6 Upmixer that is available in the AP20 for stereo sources. Unfortunately, it doesn't seem to be available as a software solution for common computer platforms. You may need to test DCP-o-matics different upmixing functions, they are still experimental and currently Carl does not really endorse them as the best available, but is collecting user feedback. The main function is still to create a center dialog mix from stereo sources. - Carsten  |  IP: Logged Leslie Hartmier Expert Film Handler Posts: 100 From: Edmonton, Alberta, Canada Registered: Jul 2012 posted 05-31-2016 01:53 PM                     As Carsten mentioned, if possible, you should upgrade to 2.8.0 or 2.8.4 - there are a myriad of improved functions.  |  IP: Logged Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 05-31-2016 06:02 PM                        I've done that, am now on 2.8.0, and then tried creating a 5.1 VF from a 90-second trailer as a test, before starting the 87-minute feature again. It created the trailer VF successfully in under a minute, which I've tested and played OK on a DCP server (ingested OV and VF, then played the VF). This is where things get curious. I then started the 87-minute feature rendering again. It began rendering at 0003hrs on Monday morning, and is still saying "Encoding image data" as I write, just under 40 hours later. However, it has been writing to the audio MXF file in the project folder continuously, throughout that time. The audio file in the 2.0 OV is 1.5GB. As the VF will have six channels rather than two, then common sense suggests that the 5.1 audio file should be around 4.5 GB. It's been growing slowly but steadily since the render started, and is now at 2.0GB. At this rate, the process should finish some time on Friday. What I can't understand is why rendering the OV took well under a day for both image and sound, yet creating another audio track looks like taking around 5 days. Furthermore, given the time it took to create the upmix for the trailer, it should have finished with this feature in under an hour.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 05-31-2016 07:12 PM                     Hi Leo: --- http://dcpomatic.com/release-notes.php?v=2.8.6 This release has the following changes: Updated fr_FR translation from Thierry Journet. Updated uk_UA and ru_RU translations from Igor Voytovich. Updated nl_NL translation from Rob van Nieuwkerk. Support for a wider range of audio file types including MP3. Hopefully fix strange colour fringing on subtitles when burning them into existing DCP content (#752). Reduce CPU usage for the preview. Fix incorrect date when using copy-as-name (#869). Add free-text notes field to cinemas and screens. Request confirmation before resetting preferences (#867). Use CPL title for KDM AnnotationTexts. Keep audio plot and video waveform dialogues always on top (#756, #820). Add Cancel button to custom colour conversion dialogue (#880). Provide option to abort more operations that require films to be saved (#847). Various fixes to text subtitles muxed into video files. Add hint on high audio levels (#822). Use up-to-date version of FFmpeg. Fix progress updates when making a VF using new audio. Change some uses of the word ‘frame’ to ‘sample’ when talking about audio (#814). Add speculative Rec 1886/2020 presets. Disallow referencing of Interop DCPs in SMPTE films, and vice versa (#804). Fix missing words in properties windows (#874). --- - Carsten  |  IP: Logged Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 05-31-2016 07:45 PM                        quote: Carsten Kurz Fix progress updates when making a VF using new audio. Hmm ... I'm on 3.8.0 (the latest stable version available for download). 41 hours after starting the DCP creation process, it's still saying "Encoding image data: 0%," but the size of the audio PCM MXF file it's created so far suggests that it's in fact around 40% done. I'm reluctant to install 4.8.6 right now, because it would mean cancelling this process and losing almost two days of rendering time. Assuming that it does manage to conclude the creation of this VF successfully, I'll update to 3.8.6, and see if anything changes trying another DCP of a similar length.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 06-01-2016 06:34 AM                     Normally, creating a VF from a previous encoded OV should only take a couple of minutes. I have no idea what is going on on your system. If you have enough time to wait, then wait. If not, cancel it and restart with 2.8.6 You should also send your logs to Carl, but it sounds as if you are suffering from the bug mentioned in the 2.8.6 release notes. The headline above the DCP-o-matic test-release notes suggest that these are not stable versions. As a matter of fact, they do contain bug fixes for the release version just as many as new experimental features. Basically, the risc for a release version to contain an issue seems to be on par with most test versions. At least you should always check the changelog to see wether there is something that concerns you. Releaseversion does not mean it doesn't contain severe bugs. They may just not have been reported before. I do admit it may be easier to switch between versions on a connected machine. On a windows machine, it's matter of a minute or so to install a previous or next version. - Carsten  |  IP: Logged Carl Hetherington Film Handler Posts: 93 From: York, North Yorkshire, England Registered: Jul 2012 posted 06-01-2016 08:47 AM                        quote: Leo Enticknap It then says "Encoding image data" (which is odd, because it shouldn't have to touch the image data - I'm just trying to add new audio to play with an existing MXF video file) Fixed in the current test version, thanks. The extreme slowness is very odd. As Carsten says, this operation should be very quick. I will create a big DCP now and see if I can reproduce the problem. The last few hundred lines of the "log" file in your project might be informative (carl@dcpomatic.com)  |  IP: Logged Leo Enticknap Film God Posts: 7474 From: Loma Linda, CA Registered: Jul 2000 posted 06-01-2016 03:36 PM                        Many thanks, Carl. The MXF file only grew by 200MB overnight (from 2.0 gigs to 2.2). I'm going to give it until the end of the week and then give up on this version, and will email you the log files whatever the outcome, then update it to 2.8.6.  |  IP: Logged Carsten Kurz Film God Posts: 4340 From: Cologne, NRW, Germany Registered: Aug 2009 posted 06-01-2016 04:05 PM                     Leo, you could capture the current log file just as well and send it to Carl. - Carsten  |  IP: Logged Carl Hetherington Film Handler Posts: 93 From: York, North Yorkshire, England Registered: Jul 2012 posted 06-01-2016 06:42 PM                        Having looked at it I think it's just a bad inefficiency in reading of existing DCP audio. I wouldn't bother with 2.8.6 as I think it will be just as bad. 2.8.7 should fix it in the next day or so.  |  IP: Logged Carl Hetherington Film Handler Posts: 93 From: York, North Yorkshire, England Registered: Jul 2012 posted 06-02-2016 10:30 AM                        I believe things should go a lot faster with 2.8.7, if you want to try that: Test download page  |  IP: Logged

All times are Central (GMT -6:00)

This topic comprises 2 pages: 1  2

Printer-friendly view of this topic

Hop To: Select a Forum: Category: Operations -------------------- Digital Cinema Forum Film Handlers' Forum Large Format Forum Ground Level Feature Info, Trailer Attachments & REAL Credit Offsets Category: Community -------------------- Film-Yak Film Handlers' Movie Reviews The Afterlife Bob Maar's Joke-A-Thon Category: Classified -------------------- Equipment and Supplies Wanted/For Sale Help Wanted/Seeking Employment Category: System -------------------- Software Beta Testing Forum

The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion and agrees to release the authors from any and all liability.