Has anyone tried HFR with dcpomatic?
I know that the colorspace is different, so wondering if dcpomatic
magically detect the fps and use the right colorspace.
Doing some tests, will keep updating.
Thanks!
Manuel AC
A dcp-o-matic user sent me a screenshot to get some advice on proper scaling options for his project. I noticed that the german localization on his machine is screwed - his screenshot shows english and german mixed wildly.
Any idea what could cause this? He is using Mavericks (OS X 10.10.1). Occurs with both 1.76 and 1.76.42. Second screenshot is 10.6.8 - everything okay.
Did anyone else have similiar issues with other localizations in OS X versions?
Carl - I noticed dramatically different file sizes in the various versions of DCP-o-matic for Mac - e.g. sometimes 25Mbytes, sometimes 120MBytes. The current breed is rather small. What's the reason for that?
- Carsten
Hi all,
DCP-o-matic 1.77.0 is now available from:
http://dcpomatic.com/download
This version includes:
A full 36-bit (12 bit-per-channel) colour path through DCP-o-matic
when high depth sources are used.
Updated fr_FR translation from Thierry Journet and Lilian Lefranc.
Updated de_DE translation from Carsten Kurz.
Fix for slipping audio sync on DTS-encoded audio tracks in some
cases (#352).
Fix for incorrect read of some video files from iTunes (where they
come up as being at 90,000 fps).
Fix for parts of content at presentation times less than zero
being played in certain circumstances (#418).
Fix incorrect behaviour of "Down" button (to move content later in
the list).
Fix snap on the timeline to work properly when butting bits of
content up to each other.
Fix for long hangs at 99% complete when encoding files with large
trims.
Fix for a crash when dragging things in the timeline (and possibly
at other times).
Fix for incorrect subtitle timing when sources are trimmed.
Fix for crash at 99% encoded in some cases.
Fix for over-sensitive error checking in some cases.
Fix problems with downloading projector certificates on Windows (#442).
Make a considerable number of crashes give more useful error messages.
Display sample aspect ratio for video content that declares it.
Stop Cancel in the Add Cinema dialogue creating a new
(empty-named) cinema (#449).
Add ‘Copy as name’ button to copy the ISDCF name to the editable
field in the DCP tab rather than the hack which copied it when ‘Use ISDCF
name’ was un-ticked.
Remove default scale configuration option and instead guess the
initial scale from the content's size and pixel aspect ratio.
Allow bypass of digest calculation for image sequence content.
Allow bypass of colourspace conversion (#266)
Rename “Add folder” button to “Add image sequence”
Move “Keep video in sequence” button into the timeline window.
Add Pause button for all jobs (part of #344)
Remove code to load old DVD-o-matic configurations, as it's not
well tested.
Speculative fix for hangs at the end of encodes when using 3D content.
Increase maximum allowed JPEG2000 bandwidth.
Thanks to Mike Blakesley, Carsten Kurz, David Nedrow, Thierry Journet,
Mark Rolfe, Lilian Lefranc, Manuel AC and Elad Saad.
Eight new supporters have been added since 1.76.0: thanks to Eric
Audurier, Maxime Estoppey, Patrick Haderer, Гуляев Михаил, David Nedrow,
Jerome Cohen Olivar, Richard Turner and Johannes Wilbrand.
Am 19.01.2015 um 02:52 schrieb Manuel AC:
> It occasionally went a bit over 200%, pretty low.
But did you test the runtime/fps performance with Big Buck Bunny?
- Carsten
Someone told me about his problem with trimming off the end of files. He usually does that based on the visuals (as in 'in fabulous 3D'). However, he can't hear the audio in DCP-o-matic, and his trims very often cuts of audio. Could there be a way to solve this in DCP-o-matic?
Is it very difficult to add audio monitoring to the preview function? Or splitting audio/video that has been imported interleaved?
- Carsten
Wondering if someone saw a similar problem. I'm using a dual hexacore
Xeon Macpro-tower and getting less than 1 fps. It's running OSX
10.6.8, might be relevant?
Any recent changes in dcpomatic? As long as I can remember it was way
faster a few months ago.
Thanks!
Manuel AC
Has anyone had problems using NTFS on a mac with the Tuxera driver?
I'm getting a write error at the end of the process, when the video
file is copied. Maybe it doesn't support the hardlinks tricks?
Also the performance is awful, I was concerned about the speed of the
codification, now I suspect it's NTFS fault.
Thanks!
Manuel AC
I started making a very basic TKR server, but I'm not used to work
with KDMs and all that signature thingy madness.
Can someone create a small test DCP?
I was tempted to modify the dcpomatic code myself, but compiling it in
my own! has been too long without doing that stuff :) Should try,
indeed.
I know it can be done manually adding the TKR line to the CPL,
correcting the hashes and then signing with cinemaslides.
I can do a test in a few days in a few servers with internet access
(Doremi 253522, 253523, 253524)
At my usual theater I'm still trying to figure out how to give the
servers connection properly, I don't control all the network.
Opinions, request and help accepted ;)
Manuel AC
As recently added the option to bypass the analysis for an image
sequence (http://carlh.net/mantis/view.php?id=446) can the same be
done for video files?
I was to add ti directly at mantis, but I'm never too sure what to put where.
Thanks!
Manuel AC
Hi Carl,
I have received a video in AVI container, DV codec, so, pretty standard. However, it is anamorphic, so no square pixels. Various media players on my machine detect it properly as 16:9, but DCP-o-matic 1.76.7 detects it as 720x576 (1.25:1) and squeezes it when choosing 'no scale'. No big deal to correct this manually in the scaling options, but maybe you can fix that. Since the media players display it correctly, there must be a flag the DCP-o-matic currently ignores when analyzing it.
The same happens when importing 16:9 VOBs from e.g. DVDs.
Hmm, I understand that there is some interpretation necessary. DCP-o-matic first follows Default Scale To in prefs. While that is correct, and some options chosen have to result in wrong aspect ratio scaling, I think that at least the 'no scale/no stretch' options should follow the original content AR, if it is clearly indicated in the file metadata. At least the content description should indicate that the files is flagged 16:9/anamorphic.
Aside from what the fact that in this case I can create a proper upscaled video - there is no way I could create an unscaled version of this file with the correct aspect ratio. When I choose 16:9, it get's uprezz'd, when I choose unscaled, I get a square 720/576 in a flat frame, when I choose NoStretch, I get a square 1350x1080. There is no way I can assign a 16:9 reference to this file.
I think the proper way to handle this is to find a 16:9/non-square pixel flag in the file and act accordingly, that is, display it stretched and with a 16:9/anamorphic indication.
I think that fight for all necessary yet straightfordward arranging of scaling options will never end...
- Carsten
