22 Feb
2015
22 Feb
'15
12:31 a.m.
Carl,
have you thought about how multi-version capability could be implemented into DCP-o-matic?
I understand that currently for most people it only makes sense for timed-text which is
only in 2.x, but I guess one could still think about ways how to implement it?
- Carsten
22 Feb
22 Feb
11:59 p.m.
Hi Carsten,
On Sun, 22 Feb 2015, Carsten Kurz wrote:
have you thought about how multi-version capability
could be implemented
into DCP-o-matic? I understand that currently for most people it only
makes sense for timed-text which is only in 2.x, but I guess one could
still think about ways how to implement it?
I have thought about it a bit. It seems to me that the user interface is
the hardest part: how to represent which content should end up in which
version.
It's possible that a single DCP-o-matic "Film" should always represent a
single CPL, and that there should be some way to link them together to
generate multi-CPL DCPs.
On the other hand, perhaps DCP-o-matic "Film" should be a DCP, or a set of
CPLs. Then you could have multiple playlists in DCP-o-matic which
generate multiple CPLs in the DCP.
Maybe there should be a "Content" tab, in which the content is set up
(crop, scale, audio gain, etc.), then one or more "Playlist" tabs, where
content is arranged into playlists, then a "DCP" tab which sets up the DCP
which will contain the playlists.
Alternatively, maybe we can have multiple "Content" tabs with the ability
to copy content between each one (which will re-use the same stuff in the
DCP).
Any thoughts are welcome. I think it's important that creating a
single-playlist DCP is just as easy after any changes as before.
Best regards,
Carl
23 Feb
23 Feb
12:11 a.m.
Just a brief thought on this...
It seems to me that the biggest annoyance of making multiple versions
isn't so much the restriction of a single CPL per DCP, but that the
time-consuming encoding of the video MXF file has to be done anew each time.
Perhaps it'd be possible to allow the user to add already encoded
audio/video MXF files in the same way as they add e.g. a Quicktime? In
that case the first version DCP could be created in the usual way, and
then all versions after created using the existing MXF without having to
repeat the JPEG2000 compression again. This would allow a much faster
method to create e.g. different versions of the same film with audio in
different languages.
Yes, it'd be even better to be able to create DCPs with multiple
playlists, but if that's a difficult feature to implement, perhaps
adding the above would be a quick fix to make versioning easier in the
meantime?
Just a thought...
Jim
On 22/02/2015 23:59, Carl Hetherington wrote:
Hi Carsten,
On Sun, 22 Feb 2015, Carsten Kurz wrote:
have you thought about how multi-version
capability could be implemented
into DCP-o-matic? I understand that currently for most people it only
makes sense for timed-text which is only in 2.x, but I guess one could
still think about ways how to implement it?
I have thought about it a bit. It
seems to me that the user interface is
the hardest part: how to represent which content should end up in which
version.
It's possible that a single DCP-o-matic "Film" should always represent a
single CPL, and that there should be some way to link them together to
generate multi-CPL DCPs.
On the other hand, perhaps DCP-o-matic "Film" should be a DCP, or a set of
CPLs. Then you could have multiple playlists in DCP-o-matic which
generate multiple CPLs in the DCP.
Maybe there should be a "Content" tab, in which the content is set up
(crop, scale, audio gain, etc.), then one or more "Playlist" tabs, where
content is arranged into playlists, then a "DCP" tab which sets up the DCP
which will contain the playlists.
Alternatively, maybe we can have multiple "Content" tabs with the ability
to copy content between each one (which will re-use the same stuff in the
DCP).
Any thoughts are welcome. I think it's important that creating a
single-playlist DCP is just as easy after any changes as before.
Best regards,
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
12:26 a.m.
Hi Jim,
This is possible with the version 2 branch of DCP-o-matic:
http://dcpomatic.com/v2
It can take video MXFs and copy their encoded data into new DCPs without a
transcoding step. That certainly speeds up the creation of multi-version
DCPs.
Any testing of v2 is welcome.
Best regards,
Carl
On Mon, 23 Feb 2015, Jim Dummett wrote:
Just a brief thought on this...
It seems to me that the biggest annoyance of making multiple versions isn't so
much the restriction of a single CPL per DCP, but that the time-consuming
encoding of the video MXF file has to be done anew each time.
Perhaps it'd be possible to allow the user to add already encoded audio/video
MXF files in the same way as they add e.g. a Quicktime? In that case the first
version DCP could be created in the usual way, and then all versions after
created using the existing MXF without having to repeat the JPEG2000
compression again. This would allow a much faster method to create e.g.
different versions of the same film with audio in different languages.
Yes, it'd be even better to be able to create DCPs with multiple playlists,
but if that's a difficult feature to implement, perhaps adding the above would
be a quick fix to make versioning easier in the meantime?
Just a thought...
Jim
On 22/02/2015 23:59, Carl Hetherington wrote:
Hi Carsten,
On Sun, 22 Feb 2015, Carsten Kurz wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
have you thought about how multi-version
capability could be implemented
into DCP-o-matic? I understand that currently for most people it only
makes sense for timed-text which is only in 2.x, but I guess one could
still think about ways how to implement it?
I have thought about it a bit. It
seems to me that the user interface is
the hardest part: how to represent which content should end up in which
version.
It's possible that a single DCP-o-matic "Film" should always represent a
single CPL, and that there should be some way to link them together to
generate multi-CPL DCPs.
On the other hand, perhaps DCP-o-matic "Film" should be a DCP, or a set of
CPLs. Then you could have multiple playlists in DCP-o-matic which
generate multiple CPLs in the DCP.
Maybe there should be a "Content" tab, in which the content is set up
(crop, scale, audio gain, etc.), then one or more "Playlist" tabs, where
content is arranged into playlists, then a "DCP" tab which sets up the DCP
which will contain the playlists.
Alternatively, maybe we can have multiple "Content" tabs with the ability
to copy content between each one (which will re-use the same stuff in the
DCP).
Any thoughts are welcome. I think it's important that creating a
single-playlist DCP is just as easy after any changes as before.
Best regards,
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
1:40 a.m.
Hi Carl.
Thanks for your reply. I wasn't aware of that. You beat me to it!
I haven't had a look at v2 yet - the last project I did, stability was
the paramount concern, so I didn't want to go bleeding edge. But I'll
give it a go when I next have a batch of DCPs to make.
Incidentally, does v2 address the colour space conversion issues that
I've heard reported can occur in v1.x? (though it looks pretty damn good
to me)
Many thanks,
Jim
On 23/02/2015 00:26, Carl Hetherington wrote:
Hi Jim,
This is possible with the version 2 branch of DCP-o-matic:
http://dcpomatic.com/v2
It can take video MXFs and copy their encoded data into new DCPs without a
transcoding step. That certainly speeds up the creation of multi-version
DCPs.
Any testing of v2 is welcome.
Best regards,
Carl
On Mon, 23 Feb 2015, Jim Dummett wrote:
Just a brief thought on this...
It seems to me that the biggest annoyance of making multiple versions isn't so
much the restriction of a single CPL per DCP, but that the time-consuming
encoding of the video MXF file has to be done anew each time.
Perhaps it'd be possible to allow the user to add already encoded audio/video
MXF files in the same way as they add e.g. a Quicktime? In that case the first
version DCP could be created in the usual way, and then all versions after
created using the existing MXF without having to repeat the JPEG2000
compression again. This would allow a much faster method to create e.g.
different versions of the same film with audio in different languages.
Yes, it'd be even better to be able to create DCPs with multiple playlists,
but if that's a difficult feature to implement, perhaps adding the above would
be a quick fix to make versioning easier in the meantime?
Just a thought...
Jim
On 22/02/2015 23:59, Carl Hetherington wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Hi Carsten,
On Sun, 22 Feb 2015, Carsten Kurz wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
have you thought about how multi-version
capability could be implemented
into DCP-o-matic? I understand that currently for most people it only
makes sense for timed-text which is only in 2.x, but I guess one could
still think about ways how to implement it?
I have thought about it a bit. It
seems to me that the user interface is
the hardest part: how to represent which content should end up in which
version.
It's possible that a single DCP-o-matic "Film" should always represent a
single CPL, and that there should be some way to link them together to
generate multi-CPL DCPs.
On the other hand, perhaps DCP-o-matic "Film" should be a DCP, or a set of
CPLs. Then you could have multiple playlists in DCP-o-matic which
generate multiple CPLs in the DCP.
Maybe there should be a "Content" tab, in which the content is set up
(crop, scale, audio gain, etc.), then one or more "Playlist" tabs, where
content is arranged into playlists, then a "DCP" tab which sets up the DCP
which will contain the playlists.
Alternatively, maybe we can have multiple "Content" tabs with the ability
to copy content between each one (which will re-use the same stuff in the
DCP).
Any thoughts are welcome. I think it's important that creating a
single-playlist DCP is just as easy after any changes as before.
Best regards,
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
12 Mar
12 Mar
12:15 a.m.
Incidentally, does v2 address the colour space
conversion issues that I've
heard reported can occur in v1.x? (though it looks pretty damn good to me)
There are a few problems with the colour space conversion in both v1 and
v2 that we are working on at the moment. If it looks good to you, carry
on :) Both v1 and v2 have fairly similar code for conversions at present.
Best regards,
Carl
Many thanks,
Jim
On 23/02/2015 00:26, Carl Hetherington wrote:
Hi Jim,
This is possible with the version 2 branch of DCP-o-matic:
http://dcpomatic.com/v2
It can take video MXFs and copy their encoded data into new DCPs without a
transcoding step. That certainly speeds up the creation of multi-version
DCPs.
Any testing of v2 is welcome.
Best regards,
Carl
On Mon, 23 Feb 2015, Jim Dummett wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Just a brief thought on this...
It seems to me that the biggest annoyance of making multiple versions
isn't so
much the restriction of a single CPL per DCP, but that the time-consuming
encoding of the video MXF file has to be done anew each time.
Perhaps it'd be possible to allow the user to add already encoded
audio/video
MXF files in the same way as they add e.g. a Quicktime? In that case the
first
version DCP could be created in the usual way, and then all versions after
created using the existing MXF without having to repeat the JPEG2000
compression again. This would allow a much faster method to create e.g.
different versions of the same film with audio in different languages.
Yes, it'd be even better to be able to create DCPs with multiple
playlists,
but if that's a difficult feature to implement, perhaps adding the above
would
be a quick fix to make versioning easier in the meantime?
Just a thought...
Jim
On 22/02/2015 23:59, Carl Hetherington wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Hi Carsten,
On Sun, 22 Feb 2015, Carsten Kurz wrote:
> have you thought about how multi-version capability could be
> implemented
> into DCP-o-matic? I understand that currently for most people it only
> makes sense for timed-text which is only in 2.x, but I guess one could
> still think about ways how to implement it?
I have thought about it a bit. It seems to me that the user interface
is
the hardest part: how to represent which content should end up in which
version.
It's possible that a single DCP-o-matic "Film" should always represent a
single CPL, and that there should be some way to link them together to
generate multi-CPL DCPs.
On the other hand, perhaps DCP-o-matic "Film" should be a DCP, or a set
of
CPLs. Then you could have multiple playlists in DCP-o-matic which
generate multiple CPLs in the DCP.
Maybe there should be a "Content" tab, in which the content is set up
(crop, scale, audio gain, etc.), then one or more "Playlist" tabs, where
content is arranged into playlists, then a "DCP" tab which sets up the
DCP
which will contain the playlists.
Alternatively, maybe we can have multiple "Content" tabs with the
ability
to copy content between each one (which will re-use the same stuff in
the
DCP).
Any thoughts are welcome. I think it's important that creating a
single-playlist DCP is just as easy after any changes as before.
Best regards,
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
23 Feb
23 Feb
12:34 p.m.
Am 23.02.2015 um 01:11 schrieb Jim Dummett:
Perhaps it'd be possible to allow the user to add
already encoded audio/video MXF files in the same way as they add e.g. a Quicktime? In
that case the first version DCP could be created in the usual way, and then all versions
after created using the existing MXF without having to repeat the JPEG2000 compression
again. This would allow a much faster method to create e.g. different versions of the same
film with audio in different languages.
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.
- Carsten
1:02 p.m.
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
24 Feb
24 Feb
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
25 Feb
25 Feb
3:30 p.m.
Am 25.02.2015 um 00:14 schrieb Manuel AC via DCPomatic:
I don't really batch converter with any more
options that it has now.
What I mean is that the GUI options to support versioning are complex to design. A
possible 'easy' solution would be to leave the dcp-o-matic GUI as it is, and shift
the versioning functionality into the batch converter or a separate 'DCP merger'.
You would create your DCPs in different versions in the main app, then resort to the batch
converter to create/merge these into multiversion packages, with common assets as much as
possible. One benefit would also be that the main application GUI does not pick up more
complexity for the average user not needing versioning.
- Carsten
7:15 p.m.
On Wed, Feb 25, 2015 at 10:30 AM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
> or a separate 'DCP merger'.
We agree. I have been feeling for some time that dcpomatic does too
many things, it even has a timeline!! So, you make think about keep
adding things like versioning to the actual GUI, and maybe proposing
an independent downsized application. This goes completely against a
DIY spirit of understanding what you are doing, but a more restricted
set of options will help the newbies. Anyways, most of the time the
options are the same, the sources are the same and I will be happy to
have a "single-click" version of DCP-o-matic for myself :)
Manuel AC
14 Mar
14 Mar
9:46 p.m.
On Wed, 25 Feb 2015 14:15:38 -0500
Manuel AC via DCPomatic <dcpomatic(a)carlh.net> wrote:
On Wed, Feb 25, 2015 at 10:30 AM, Carsten Kurz via
DCPomatic
<dcpomatic(a)carlh.net> wrote:
Hi all,
It's certainly an interesting idea. I'll look at it when I get around
to looking at multi-version. I have a vague feeling that it's possible
to integrate multi-version fairly cleanly into the main application
(without getting in the way of most users who don't want it). But I
could be wrong, and a separate merger program is a nice idea.
Best regards,
Carl
> or a separate 'DCP merger'.
We agree. I have been feeling for some time that dcpomatic does too
many things, it even has a timeline!! So, you make think about keep
adding things like versioning to the actual GUI, and maybe proposing
an independent downsized application. This goes completely against a
DIY spirit of understanding what you are doing, but a more restricted
set of options will help the newbies. Anyways, most of the time the
options are the same, the sources are the same and I will be happy to
have a "single-click" version of DCP-o-matic for myself :)
12 Mar
12 Mar
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?
3698
days inactive
3718
days old
12 comments
4 participants
participants (4)
-
Carl Hetherington -
Carsten Kurz -
Jim Dummett -
Manuel AC