24 Feb
2015
24 Feb
'15
11:14 p.m.
I don't really batch converter with any more options that it has now.
An advanced mastering app could be independent, but I don't think
that's in Carl's priority list.
With the option to use DCPs and MXF as sources, dcpomatic already acts
somehow as a remastering tool. When it starts reusing the hashes, a
reallly good one in fact ;)
Manuel AC
On Mon, Feb 23, 2015 at 8:02 AM, Carsten Kurz <audiovisual(a)t-online.de> wrote:
Am 23.02.2015 um 13:34 schrieb Carsten Kurz:
Hmm. What if the first step for a multi-version
capability would be a 'DCP merger'? Takes assets of two or more DCP-o-matic
encodings (or 'ANY DCPs) and merges them into a multi-version package. That way you
could have both options - separate assets could be embedded, as well as common assets
referenced by all versions?
You would create different versions of a DCP within the existing GUI, then select which
ones to throw together later? This could build up on DCP-o-matics capability to use a
single video-file for multiple encodings/CPLs.
This could work in a similar way as the existing GUI batch converter. As a matter of
fact, it could be a modified version of the batch converter, with a simple checkbox wether
to create individual DCPs or a multi version package?
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic