I mentioned before that I like the way DCP-o-matic shows the essential processing options below the content tab, so that there is a quick overview about what happens during the conversion with regard to scaling, aspect ratio, audio, etc.
Wondering wether we could add a full set of these details below the DCP tab - as there is more than enough space there, and some of the DCP tab options are relevant to these. Also, the DCP tab should normally be the final stage before one hits 'Jobs -> Create DCP', so I think it would be good to have an overview over all essential processing there before one finally hits 'Make DCP. One could even an another 'Make DCP' button there.
In a later release, I also think it would be more useful to include the 'tips' or hints there, possibly behind the specific parameter causing the warning/hint. I think 'Tips' will be easily missed as it has to be called manually.
e.g. something like:
Content frame rate is 25 fps -> Warning Icon, Click and 'Your DCP frame rate 25fps may cause problems...' appears.
Same for audio issues, DCP bandwith, etc. This would add to my idea from above for a full overview of most essential aspects of the DCP creation.
And: I brought this up earlier, but Carl has a different opinion on this: I still think the scaling method should go under the content tab and has to be settable content-specific. I don't think it makes sense to have a choice of different scaling methods, but only 'global'. The only reason to choose different scaling methods should be content-related. Another reason: Scaling method is not a DCI/DCP specific parameter, unlike all other parameters under the DCP tab.
- Carsten
Am 25.01.2015 um 20:40 schrieb Manuel AC:
> Sorry, colorspace it's certainly not it, but something is different in
> the color encoding, similar or the same as in 3D.
> Or maybe is just the server who sends the image differently?
> It's definitely a different color setting in the projector.
'Classic' server-side media blocks with HD-SDI connections towards the projector use a different transmission colorspace for 3D (because Dual-Link HD-SDI can not do 48fps in full 12Bit xyz/4:4:4). Thus for 3D, these systems use 10Bit YCbCr over HD-SDI between Server and projector, so the projector needs a special input format for 3D.
But HFR in the strict sense of HFR-3D does not work on these systems anyway, HFR-3D (96/120Hz playout frame rate) does not work over HD-SDI at all.
Only IMB/IMS Systems support HFR-3D, and the IMB systems does not suffer the bandwith limitation as HD-SDI, so, 3D on IMB systems use xyz/4:4:4 as well as 2D/24fps.
But for all those formats and signals, the storage/DCP format is always yxz. And that is what DCP-o-matic does.
You may in fact be after playing 48fps 2D, so to say, 2D-HFR. And you may have found an 48fps YCbCr format on the projector. But that is meant to be used with 'classic' 3D on HD-SDI systems. Technweise, the DCP storage format is always xyz, not matter what frame rate or 2D/3D. The transmission format between server and mediablock/projector can ALWAYS be different, but that is nothing DCP-o-matic has to deal with. You configure suitable output/input formats on server and projector to deal with that.
- Carsten
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
