22 Mar
2016
22 Mar
'16
7:26 p.m.
Hi all.
Is it possible to "re-pack" an existing DCP without re-encoding the video?
I have a couple of DCPs which have problems with the sound so I'd like
to make a new DCP using the existing DCP video MXF and replace just the
audio tracks.
I think this came up before and I thought it was supported in DCPomatic
2. But I tried it in v2.7.1 and couldn't work out how to do it.
Importing the J2K MXF file works fine, but with colour conversion set to
"none", when it came to make the DCP, from the slowness of the process
it appeared that the video was being re-encoded rather than copied.
Did I use the wrong options, or is this not supported in DCP-o-matic at
present?
Any help much appreciated...
Jim
22 Mar
22 Mar
11:10 p.m.
Hi, Jim. As far as I know, DoM creates new DCP from existing one just by copying original
mxf-files, and generates new xml-files for new DCP (ASSETMAP, VOLINDEX, etc.). DoM will
re-encode DCP-content only if new DCP has some changes, e.g. additional video-content, or
new sound. In case of sound it will re-encode only mxf_audio, mxf_video will be just
copied. To make new DCP from existing, you need to add into your project folder of
existing DCP (not separate files from it). On "video" mark checkbox "refer
to existing DCP" or something like that (sorry, don't remember, on audio tab turn
off audio track by uncheking green boxes on channels, than add your correct audio file,
change gain if needed, and then Make DCP in "Jobs" menu. Hope this fill help
you!
Regards, Igor.
22 марта 2016, 21:27:26, от "Jim Dummett via DCPomatic" < dcpomatic(a)carlh.net
>:
Hi all.
Is it possible to "re-pack" an existing DCP without re-encoding the video?
I have a couple of DCPs which have problems with the sound so I'd like
to make a new DCP using the existing DCP video MXF and replace just the
audio tracks.
I think this came up before and I thought it was supported in DCPomatic
2. But I tried it in v2.7.1 and couldn't work out how to do it.
Importing the J2K MXF file works fine, but with colour conversion set to
"none", when it came to make the DCP, from the slowness of the process
it appeared that the video was being re-encoded rather than copied.
Did I use the wrong options, or is this not supported in DCP-o-matic at
present?
Any help much appreciated...
Jim
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
Regards, Igor Voytovich
23 Mar
23 Mar
12:37 p.m.
Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer to
existing DCP" checkbox. I'll give it a go later and let you know how I
get on.
Many thanks,
Jim
On 22/03/2016 23:10, Игорь wrote:
Hi, Jim.
As far as I know, DoM creates new DCP from existing one just by
copying original mxf-files, and generates new xml-files for new DCP
(ASSETMAP, VOLINDEX, etc.). DoM will re-encode DCP-content only if new
DCP has some changes, e.g. additional video-content, or new sound. In
case of sound it will re-encode only mxf_audio, mxf_video will be just
copied. To make new DCP from existing, you need to add into your
project folder of existing DCP (not separate files from it). On
"video" mark checkbox "refer to existing DCP" or something like that
(sorry, don't remember, on audio tab turn off audio track by uncheking
green boxes on channels, than add your correct audio file, change gain
if needed, and then Make DCP in "Jobs" menu. Hope this fill help you!
Regards, Igor.
22 марта 2016, 21:27:26, от "Jim Dummett via DCPomatic"
<dcpomatic(a)carlh.net <mailto:dcpomatic@carlh.net>>:
Hi all.
Is it possible to "re-pack" an existing DCP without re-encoding the video?
I have a couple of DCPs which have problems with the sound so I'd like
to make a new DCP using the existing DCP video MXF and replace just the
audio tracks.
I think this came up before and I thought it was supported in DCPomatic
2. But I tried it in v2.7.1 and couldn't work out how to do it.
Importing the J2K MXF file works fine, but with colour conversion set to
"none", when it came to make the DCP, from the slowness of the process
it appeared that the video was being re-encoded rather than copied.
Did I use the wrong options, or is this not supported in DCP-o-matic at
present?
Any help much appreciated...
Jim
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net <mailto:DCPomatic@carlh.net>
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
Regards, Igor Voytovich
28 Mar
28 Mar
5:24 p.m.
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer to
existing DCP" checkbox. I'll give it a go later and let you know how I get on.
I think that is possible, but it creates a version file. That means, you have to ingest
the original DCP with it to make the version with the adjusted sound playable. So,
technically, it solves your problem, but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF file without recoding
in some earlier version, and I thought it was still possible.
I think there was a recent question on the DCP-o-matic Forum towards this, and Carl
admitted that current versions of DCP-o-matic are not as smart dealing with existing MXFs
as previous versions used to be. So, if all you want to do is to replace the sound, it may
be better to use an older version of DCP-o-matic. Which one, I don't know, maybe Carl
knows where that changed?
- Carsten
5:38 p.m.
We recently remade a DCP to add a subtitle track from an srt file.
Surprisingly it worked! and fast. The "refer to existing DCP" checkbox
wasn't even checked and it just did a repackaging.
I still thought that dom was unable to reuse the MXF sound, but looks
like it's working now.
On Mon, Mar 28, 2016 at 1:24 PM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
--
http://akadcp.com/
https://www.facebook.com/akadcp
Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer to
existing DCP" checkbox. I'll give it a go later and let you know how I get on.
I think that is possible, but it creates a version file. That means, you have to ingest
the original DCP with it to make the version with the adjusted sound playable. So,
technically, it solves your problem, but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF file without
recoding in some earlier version, and I thought it was still possible.
I think there was a recent question on the DCP-o-matic Forum towards this, and Carl
admitted that current versions of DCP-o-matic are not as smart dealing with existing MXFs
as previous versions used to be. So, if all you want to do is to replace the sound, it may
be better to use an older version of DCP-o-matic. Which one, I don't know, maybe Carl
knows where that changed?
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
5:51 p.m.
Am 28.03.2016 um 19:38 schrieb Manuel AC via DCPomatic:
We recently remade a DCP to add a subtitle track from
an srt file.
Surprisingly it worked! and fast. The "refer to existing DCP" checkbox
wasn't even checked and it just did a repackaging.
I still thought that dom was unable to reuse the MXF sound, but looks
like it's working now.
Hmm, I guess Carl should clarify this for us then. The forum post I was referring to was
this:
http://dcpomatic.com/forum/viewtopic.php?f=2&t=254
Maybe Carl didn't want to express that re-using an existing MXF without recoding is
impossible with current versions, but just that it doesn't work properly under all
conditions.
E.g. it could be a problem if you try to re-use a SMPTE MXF within a new Interop package
(I know Carl is working on this particular issue already).
Manuel and Jim - which versions are you using?
- Carsten
6:08 p.m.
Latest version.
Always SMPTE.
The original DCP was coming from Qube.
Other DCP's are not recognized. Couldn't find a pattern, and also this
is not an usual procedure for us.
I though the warping of the MXF is different for each standard. If I
can reuse an Interop MXF without rewarping would be good news :)
On Mon, Mar 28, 2016 at 1:51 PM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Am 28.03.2016 um 19:38 schrieb Manuel AC via DCPomatic:
--
http://akadcp.com/
https://www.facebook.com/akadcp
We recently remade a DCP to add a subtitle track
from an srt file.
Surprisingly it worked! and fast. The "refer to existing DCP" checkbox
wasn't even checked and it just did a repackaging.
I still thought that dom was unable to reuse the MXF sound, but looks
like it's working now.
Hmm, I guess Carl should clarify this for us then. The forum post I was referring to was
this:
http://dcpomatic.com/forum/viewtopic.php?f=2&t=254
Maybe Carl didn't want to express that re-using an existing MXF without recoding is
impossible with current versions, but just that it doesn't work properly under all
conditions.
E.g. it could be a problem if you try to re-use a SMPTE MXF within a new Interop package
(I know Carl is working on this particular issue already).
Manuel and Jim - which versions are you using?
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
6:19 p.m.
Am 28.03.2016 um 20:08 schrieb Manuel AC:
I though the warping of the MXF is different for each
standard. If I
can reuse an Interop MXF without rewarping would be good news :)
They sure are different. Still DCP-o-matic allowed/allows to mix them, and your server may
or may not like this. Recently, an indie documentary has been distributed in germany with
a mixture of SMPTE and IOP VFs within the same package. I guess it is also still possible
to create a SMPTE VF referring to an IOP OV or vice versa with DOM. Carl told me he would
work on a solution/check.
The VF feature is still experimental, so you have to make sure you get some things right
yourself.
I also thought that at some point it would be a good idea to move the SMPTE/IOP selection
into preferences instead of under the DCP tab. To some people, it may appear that
SMPTE/IOP is 'just another' parameter of a DCP. But of course it is a much more
fundamental choice.
I know some (like you ;-) ) would probably already opt to remove the IOP option
completely, but so far, DCP-o-matic still can't create encrypted SMPTE DCPs for
(some?) Sony systems, so I think that is too early. For compatibility reasons, the IOP
should stay with us for quite a while, I guess.
- Carsten
6:34 p.m.
Uhmmm recompile to take out IOP and default to my "own" standard
SMPTE-F32 (reels <4gb) hehehe
Lots of subtitles and 25 and 30 fps, IOP is certainly not my friend, indeed.
Rewarping an IOP-MXF to SMPTE-MXF without recoding would be
interesting for some projects in the near future.
Manuel AC
On Mon, Mar 28, 2016 at 2:19 PM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Am 28.03.2016 um 20:08 schrieb Manuel AC:
--
http://akadcp.com/
https://www.facebook.com/akadcp
I though the warping of the MXF is different for
each standard. If I
can reuse an Interop MXF without rewarping would be good news :)
They sure are different. Still DCP-o-matic allowed/allows to mix them, and your server
may or may not like this. Recently, an indie documentary has been distributed in germany
with a mixture of SMPTE and IOP VFs within the same package. I guess it is also still
possible to create a SMPTE VF referring to an IOP OV or vice versa with DOM. Carl told me
he would work on a solution/check.
The VF feature is still experimental, so you have to make sure you get some things right
yourself.
I also thought that at some point it would be a good idea to move the SMPTE/IOP selection
into preferences instead of under the DCP tab. To some people, it may appear that
SMPTE/IOP is 'just another' parameter of a DCP. But of course it is a much more
fundamental choice.
I know some (like you ;-) ) would probably already opt to remove the IOP option
completely, but so far, DCP-o-matic still can't create encrypted SMPTE DCPs for
(some?) Sony systems, so I think that is too early. For compatibility reasons, the IOP
should stay with us for quite a while, I guess.
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic 
6:40 p.m.
On Mon, 28 Mar 2016 19:24:14 +0200
Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
Hi all,
It's not a version thing. If you import a full DCP to DoM and leave
"refer to existing" unchecked it will re-wrap the video without
transcoding. You can add some new sound, un-map the DCP's sound and
the result will be the DCP's video (re-wrapped, not transcoded) and the
new sound. Similarly you can add subs if you like.
The problem is with importing MXFs individually. This will always
result in transcoding, and will not work for sound MXFs. That is what
needs to be fixed.
If you just import the whole DCP (with "Add folder...") everything
should be ok.
Kind regards.
Carl
Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer
to existing DCP" checkbox. I'll give it a go later and let you know
how I get on.
I think that is possible, but it creates a version file. That means,
you have to ingest the original DCP with it to make the version with
the adjusted sound playable. So, technically, it solves your problem,
but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF
file without recoding in some earlier version, and I thought it was
still possible.
6:42 p.m.
With rewarping you mean repackaging, without touching the MXF files?
Or actual rewarping if the standard has changed?
Thanks!
Manuel AC
On Mon, Mar 28, 2016 at 2:40 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
On Mon, 28 Mar 2016 19:24:14 +0200
Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
--
http://akadcp.com/
https://www.facebook.com/akadcp
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
Hi all,
It's not a version thing. If you import a full DCP to DoM and leave
"refer to existing" unchecked it will re-wrap the video without
transcoding. You can add some new sound, un-map the DCP's sound and
the result will be the DCP's video (re-wrapped, not transcoded) and the
new sound. Similarly you can add subs if you like.
The problem is with importing MXFs individually. This will always
result in transcoding, and will not work for sound MXFs. That is what
needs to be fixed.
If you just import the whole DCP (with "Add folder...") everything
should be ok.
Kind regards.
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer
to existing DCP" checkbox. I'll give it a go later and let you know
how I get on.
I think that is possible, but it creates a version file. That means,
you have to ingest the original DCP with it to make the version with
the adjusted sound playable. So, technically, it solves your problem,
but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF
file without recoding in some earlier version, and I thought it was
still possible.
9:19 p.m.
Hi Manuel,
It always re-wraps, i.e. extracts the J2K data and uses it to create a new
MXF. So it should re-wrap interop to SMPTE if you ask it. I haven't
tested that personally though.
Cehers,
Carl
On Mon, 28 Mar 2016, Manuel AC via DCPomatic wrote:
With rewarping you mean repackaging, without touching
the MXF files?
Or actual rewarping if the standard has changed?
Thanks!
Manuel AC
On Mon, Mar 28, 2016 at 2:40 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
On Mon, 28 Mar 2016 19:24:14 +0200
Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
--
http://akadcp.com/
https://www.facebook.com/akadcp
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
Hi all,
It's not a version thing. If you import a full DCP to DoM and leave
"refer to existing" unchecked it will re-wrap the video without
transcoding. You can add some new sound, un-map the DCP's sound and
the result will be the DCP's video (re-wrapped, not transcoded) and the
new sound. Similarly you can add subs if you like.
The problem is with importing MXFs individually. This will always
result in transcoding, and will not work for sound MXFs. That is what
needs to be fixed.
If you just import the whole DCP (with "Add folder...") everything
should be ok.
Kind regards.
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic Hi Igor.
Thanks, that's really helpful. Don't know how I missed the "refer
to existing DCP" checkbox. I'll give it a go later and let you know
how I get on.
I think that is possible, but it creates a version file. That means,
you have to ingest the original DCP with it to make the version with
the adjusted sound playable. So, technically, it solves your problem,
but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF
file without recoding in some earlier version, and I thought it was
still possible. 
31 Mar
31 Mar
7:14 p.m.
Hi,
A feature that would be really, really useful is to be able "cut" out
a single CPL and make a full DCP from it. I.e. to be able to import a
full DCP with one or more CPL:s or a full DCP + a supplemental package
and then select only the CPL of interest and rewrap it to a
self-containing DCP consisting only of this Composition. In other
words, to generate new PKL, VOLINDEX and ASSETMAP files referencing
only the compositions you want, but leave all asset files and CPL:s
unchanged.
This would be useful for festivals because you would like to eliminate
the possibility of chosing the wrong CPL to project.
Dolby servers do exactly this. They generate a new, self contained DCP
for every CPL that is ingested. You can take a look in the
"generatedPackages" folder if you log in over ftp. To be able to do
this directly in DCP-o-matic would be a real killer feature for me.
Best,
Mattias
On Mon, Mar 28, 2016 at 11:19 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Hi Manuel,
It always re-wraps, i.e. extracts the J2K data and uses it to create a new
MXF. So it should re-wrap interop to SMPTE if you ask it. I haven't
tested that personally though.
Cehers,
Carl
On Mon, 28 Mar 2016, Manuel AC via DCPomatic wrote:
--
-mattias
With rewarping you mean repackaging, without
touching the MXF files?
Or actual rewarping if the standard has changed?
Thanks!
Manuel AC
On Mon, Mar 28, 2016 at 2:40 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic On Mon, 28 Mar 2016 19:24:14 +0200
Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
--
http://akadcp.com/
https://www.facebook.com/akadcp
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
> Hi Igor.
>
> Thanks, that's really helpful. Don't know how I missed the "refer
> to existing DCP" checkbox. I'll give it a go later and let you know
> how I get on.
I think that is possible, but it creates a version file. That means,
you have to ingest the original DCP with it to make the version with
the adjusted sound playable. So, technically, it solves your problem,
but in a sort of unpractical way.
I remember that DCP-o-matic was able to re-use an existing video MXF
file without recoding in some earlier version, and I thought it was
still possible.
Hi all,
It's not a version thing. If you import a full DCP to DoM and leave
"refer to existing" unchecked it will re-wrap the video without
transcoding. You can add some new sound, un-map the DCP's sound and
the result will be the DCP's video (re-wrapped, not transcoded) and the
new sound. Similarly you can add subs if you like.
The problem is with importing MXFs individually. This will always
result in transcoding, and will not work for sound MXFs. That is what
needs to be fixed.
If you just import the whole DCP (with "Add folder...") everything
should be ok.
Kind regards.
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
1 Apr
1 Apr
1:45 a.m.
To my knowledge dom doesn't (yet) support DCPs with more than one CPL.
Dom actually rewrap new MXFs for everything, that it's an interesting
behavior in many cases but a bit overkill for your case. I'm also
looking into creating some kind of basic CPL editor, and yes it's
mainly for festivals. Mixed standards are an issue, but dom already
take care of that ;)
That Dolby thing smells bad coding. Instead of properly managing the
references just copy everything!! One of the uses I have for multiple
CPLs is saving espace for things like a preshow with multiple
variants, or sometimes having 2 or even 3 subtitled versions of the
same film just in case.
I'll be sure to avoid Dolby servers for festivals, it's hard enough to
manage the limited ingest space.
Carl, how hard would be to integrate a CPL editor? I would be more
than happy to propose an interface and work out the different
situations that may be presented as source and goal. Rewraping
abilities are already there, also the libraries for the CPL creation
and the rest of the packaging. I wanted an online editor but if I can
avoid al the parsing job, better.
Manuel AC
On Thu, Mar 31, 2016 at 3:14 PM, Mattias Mattsson via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Hi,
A feature that would be really, really useful is to be able "cut" out
a single CPL and make a full DCP from it. I.e. to be able to import a
full DCP with one or more CPL:s or a full DCP + a supplemental package
and then select only the CPL of interest and rewrap it to a
self-containing DCP consisting only of this Composition. In other
words, to generate new PKL, VOLINDEX and ASSETMAP files referencing
only the compositions you want, but leave all asset files and CPL:s
unchanged.
This would be useful for festivals because you would like to eliminate
the possibility of chosing the wrong CPL to project.
Dolby servers do exactly this. They generate a new, self contained DCP
for every CPL that is ingested. You can take a look in the
"generatedPackages" folder if you log in over ftp. To be able to do
this directly in DCP-o-matic would be a real killer feature for me.
Best,
Mattias
On Mon, Mar 28, 2016 at 11:19 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
--
http://akadcp.com/
https://www.facebook.com/akadcp
Hi Manuel,
It always re-wraps, i.e. extracts the J2K data and uses it to create a new
MXF. So it should re-wrap interop to SMPTE if you ask it. I haven't
tested that personally though.
Cehers,
Carl
On Mon, 28 Mar 2016, Manuel AC via DCPomatic wrote:
--
-mattias
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic With rewarping you mean repackaging, without
touching the MXF files?
Or actual rewarping if the standard has changed?
Thanks!
Manuel AC
On Mon, Mar 28, 2016 at 2:40 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic On Mon, 28 Mar 2016 19:24:14 +0200
Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
>
> Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
>
> > Hi Igor.
> >
> > Thanks, that's really helpful. Don't know how I missed the "refer
> > to existing DCP" checkbox. I'll give it a go later and let you know
> > how I get on.
>
> I think that is possible, but it creates a version file. That means,
> you have to ingest the original DCP with it to make the version with
> the adjusted sound playable. So, technically, it solves your problem,
> but in a sort of unpractical way.
>
> I remember that DCP-o-matic was able to re-use an existing video MXF
> file without recoding in some earlier version, and I thought it was
> still possible.
Hi all,
It's not a version thing. If you import a full DCP to DoM and leave
"refer to existing" unchecked it will re-wrap the video without
transcoding. You can add some new sound, un-map the DCP's sound and
the result will be the DCP's video (re-wrapped, not transcoded) and the
new sound. Similarly you can add subs if you like.
The problem is with importing MXFs individually. This will always
result in transcoding, and will not work for sound MXFs. That is what
needs to be fixed.
If you just import the whole DCP (with "Add folder...") everything
should be ok.
Kind regards.
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
http://akadcp.com/
https://www.facebook.com/akadcp
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
1:58 a.m.
In my opinion, wether done by Carl or someone else, that should be done as a external app,
not within the DOM GUI. It's a very different task, and I fear the DOM GUI will become
too complicated with other functions being added.
There is also a long pending request to create ProRes/single image sequences/Proxies from
DCPs with a simple GUI, e.g. to use them as frame accurate proxies for subtitle work. That
would also better be handled by a separate dedicated application.
- Carsten
2:12 a.m.
Am 01.04.2016 um 03:45 schrieb Manuel AC via DCPomatic:
That Dolby thing smells bad coding. Instead of properly managing the
references just copy everything!! One of the uses I have for multiple
CPLs is saving espace for things like a preshow with multiple
variants, or sometimes having 2 or even 3 subtitled versions of the
same film just in case.
I'll be sure to avoid Dolby servers for festivals, it's hard enough to
manage the limited ingest space.
There is probably a lot of bad coding in Dolbys, but not to the extent you suggest -
Dolbys do handle references properly. They create virtual packages with new asset maps and
packing lists, but of course then reference the same files in their asset directories.
They do not waste space by duplicating media assets just to create independent DCPs/CPLs.
They just double the metadata for each CPL, so it LOOKs like an individual CPL/OV.
But our Sony does something like that when exporting DCPs to external media. When you
select a VF-CPL, it exports a full DCP, including all assets that originally were
contained in it's OV DCP. That is handy as long as the intention of the export is to
save exactly this version - e.g. a dubbed 7.1 version. You can ingest this single export
on any other server, and it will include all the necessary files to play this CPL.
Unfortunately, if you want to export multiple versions, THAT will create a full set of
media assets for every exported version. So instead of having maybe 150GB for the OV + 12
for german + 12 for french as on the original distribution media, you will end up with
twice as much for both versions exported.
I still prefer it to be this way - as my intention is, if I export a CPL, it is to save
exactly this version for later re-ingest and playout.
I don't want to end up a couple of weeks later with only an unplayable VF because I
missed to export the necessary OV as well...
- Carsten
3:25 a.m.
Thanks Carsten, that makes a lot more sense. I'm not a big fan of Dolby indeed.
Agreed that interface wise Dom may end up looking better as a suite of
tools. The interest is reusing the "guts" of it.
I don't really like the idea of having separate apps, but maybe this
can help to bring some programmers to the project, that could "play"
without touching the core Dom.
Don't have any experience managing open source programming projects,
it makes sense?
Thanks!
Manuel AC
On Thu, Mar 31, 2016 at 10:12 PM, Carsten Kurz via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Am 01.04.2016 um 03:45 schrieb Manuel AC via DCPomatic:
--
http://akadcp.com/
https://www.facebook.com/akadcp
That Dolby thing smells bad coding. Instead of properly managing the
references just copy everything!! One of the uses I have for multiple
CPLs is saving espace for things like a preshow with multiple
variants, or sometimes having 2 or even 3 subtitled versions of the
same film just in case.
I'll be sure to avoid Dolby servers for festivals, it's hard enough to
manage the limited ingest space.
There is probably a lot of bad coding in Dolbys, but not to the extent you suggest -
Dolbys do handle references properly. They create virtual packages with new asset maps and
packing lists, but of course then reference the same files in their asset directories.
They do not waste space by duplicating media assets just to create independent DCPs/CPLs.
They just double the metadata for each CPL, so it LOOKs like an individual CPL/OV.
But our Sony does something like that when exporting DCPs to external media. When you
select a VF-CPL, it exports a full DCP, including all assets that originally were
contained in it's OV DCP. That is handy as long as the intention of the export is to
save exactly this version - e.g. a dubbed 7.1 version. You can ingest this single export
on any other server, and it will include all the necessary files to play this CPL.
Unfortunately, if you want to export multiple versions, THAT will create a full set of
media assets for every exported version. So instead of having maybe 150GB for the OV + 12
for german + 12 for french as on the original distribution media, you will end up with
twice as much for both versions exported.
I still prefer it to be this way - as my intention is, if I export a CPL, it is to save
exactly this version for later re-ingest and playout.
I don't want to end up a couple of weeks later with only an unplayable VF because I
missed to export the necessary OV as well...
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
9 a.m.
Am 01.04.2016 um 05:25 schrieb Manuel AC via DCPomatic:
Thanks Carsten, that makes a lot more sense. I'm
not a big fan of Dolby indeed.
Agreed that interface wise Dom may end up looking better as a suite of
tools. The interest is reusing the "guts" of it.
I don't really like the idea of having separate apps, but maybe this
can help to bring some programmers to the project, that could "play"
without touching the core Dom.
Once I also had the idea that the exact opposite of what Mattias suggested could be useful
- a CPL merger, that would take all assets of multiple CPLs and merge them into a packet,
creating OVs and VFs as necessary. I also hoped that would help to keep the DOM GUI clean
from most of the logistics of dealing with multiple CPLs for the OV and VF business.
- Carsten
6:57 p.m.
Carl, how hard would be to integrate a CPL editor? I
would be more
than happy to propose an interface and work out the different
situations that may be presented as source and goal. Rewraping
abilities are already there, also the libraries for the CPL creation
and the rest of the packaging. I wanted an online editor but if I can
avoid al the parsing job, better.
I think it would be ok from a technical point of view, the trick would be
integrating its user interface in such a way that it doesn't bloat
DoM too much (or at all) and doesn't make the basic case (file->new, add
content, make dcp) any harder.
The "refer to existing" buttons are really a hack in lieu of "proper"
CPL
management, I think ... but I don't know what that managements should look
like.
Any discussion / suggestions are welcome.
Kind regards,
Carl
Manuel AC
On Thu, Mar 31, 2016 at 3:14 PM, Mattias Mattsson via DCPomatic
<dcpomatic(a)carlh.net> wrote:
Hi,
A feature that would be really, really useful is to be able "cut" out
a single CPL and make a full DCP from it. I.e. to be able to import a
full DCP with one or more CPL:s or a full DCP + a supplemental package
and then select only the CPL of interest and rewrap it to a
self-containing DCP consisting only of this Composition. In other
words, to generate new PKL, VOLINDEX and ASSETMAP files referencing
only the compositions you want, but leave all asset files and CPL:s
unchanged.
This would be useful for festivals because you would like to eliminate
the possibility of chosing the wrong CPL to project.
Dolby servers do exactly this. They generate a new, self contained DCP
for every CPL that is ingested. You can take a look in the
"generatedPackages" folder if you log in over ftp. To be able to do
this directly in DCP-o-matic would be a real killer feature for me.
Best,
Mattias
On Mon, Mar 28, 2016 at 11:19 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
--
http://akadcp.com/
https://www.facebook.com/akadcp
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
Hi Manuel,
It always re-wraps, i.e. extracts the J2K data and uses it to create a new
MXF. So it should re-wrap interop to SMPTE if you ask it. I haven't
tested that personally though.
Cehers,
Carl
On Mon, 28 Mar 2016, Manuel AC via DCPomatic wrote:
--
-mattias
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic With rewarping you mean repackaging, without
touching the MXF files?
Or actual rewarping if the standard has changed?
Thanks!
Manuel AC
On Mon, Mar 28, 2016 at 2:40 PM, Carl Hetherington via DCPomatic
<dcpomatic(a)carlh.net> wrote:
> On Mon, 28 Mar 2016 19:24:14 +0200
> Carsten Kurz via DCPomatic <dcpomatic(a)carlh.net> wrote:
>
>>
>> Am 23.03.2016 um 13:37 schrieb Jim Dummett via DCPomatic:
>>
>> > Hi Igor.
>> >
>> > Thanks, that's really helpful. Don't know how I missed the
"refer
>> > to existing DCP" checkbox. I'll give it a go later and let you
know
>> > how I get on.
>>
>> I think that is possible, but it creates a version file. That means,
>> you have to ingest the original DCP with it to make the version with
>> the adjusted sound playable. So, technically, it solves your problem,
>> but in a sort of unpractical way.
>>
>> I remember that DCP-o-matic was able to re-use an existing video MXF
>> file without recoding in some earlier version, and I thought it was
>> still possible.
>
> Hi all,
>
> It's not a version thing. If you import a full DCP to DoM and leave
> "refer to existing" unchecked it will re-wrap the video without
> transcoding. You can add some new sound, un-map the DCP's sound and
> the result will be the DCP's video (re-wrapped, not transcoded) and the
> new sound. Similarly you can add subs if you like.
>
> The problem is with importing MXFs individually. This will always
> result in transcoding, and will not work for sound MXFs. That is what
> needs to be fixed.
>
> If you just import the whole DCP (with "Add folder...") everything
> should be ok.
>
> Kind regards.
> Carl
>
> _______________________________________________
> DCPomatic mailing list
> DCPomatic(a)carlh.net
> http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
http://akadcp.com/
https://www.facebook.com/akadcp
_______________________________________________
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
3314
days inactive
3324
days old
18 comments
6 participants
participants (6)
-
Carl Hetherington -
Carsten Kurz -
Jim Dummett -
Manuel AC -
Mattias Mattsson -
Игорь