12 Mar
2015
12 Mar
'15
12:43 a.m.
On Mon, 23 Feb 2015, Carsten Kurz wrote:
Am 23.02.2015 um 13:34 schrieb Carsten Kurz:
Thanks for your suggestions and thoughts. It could work, indeed. It
would be a bit of a shame if one was trying to create a multi-DCP with a
complicated video setup (so you had to do the setup several times). I'm
hopeful there's a way of making DCP-o-matic cope with multi-version
without complicating the UI for single-version. I'll hope to get onto
this soon; I have been a bit tied up with other things.
With best regards,
Carl
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?