21 Mar
2017
21 Mar
'17
1:20 p.m.
Just to say that dcp_inspect is a fantastic tool. It's caught a lot of
oddities for us in DCPs provided by filmmakers/distributors for film
festivals, and is also invaluable for hash-checking.
I've also noticed that all DCPs made with DCP-o-matic (v1.x branch)
result in this same warning in EasyDCP Player, but like you I'm just
using the demo version so it doesn't reveal the specifics. I've always
assumed the warning probably relates to the DCP naming convention (you
also often get warnings in dcp_inspect due to this if some fields in the
naming like studio aren't filled in). But we've never had a single DCP
created with DCP-o-matic fail to play in a cinema (yet!)
Wolfgang, I didn't know you were on this list. I don't know if
dcp_inspect is still in active development, but I have a PR open for a
small change if you'd be willing to merge:
https://github.com/wolfgangw/backports/pull/64
Jim
On 20/03/2017 19:39, Wolfgang Woehl via DCPomatic wrote:
You could use dcp_inspect (1) for a thorough
examination and
validation of DCPs.
It will catch a lot of issues. And for feedback on the ones it might
not I'd be grateful.
Thanks, Wolfgang
(1) https://github.com/wolfgangw/digital_cinema_tools_distribution/wiki
Am 20.03.2017 um 16:00 schrieb cjflynn--- via DCPomatic
<dcpomatic(a)carlh.net <mailto:dcpomatic@carlh.net>>:
Shanu
Could you please tell the version number of DCP-o-Matic that you
used, which got that error? If I have that version, I can try a DCP
and see if I get the same results.
C J
Cinema Test Tools <http://cinematesttools.com>
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic On Mar 20, 2017, at 02:25 000AM, Carl
Hetherington via DCPomatic
<dcpomatic(a)carlh.net <mailto:dcpomatic@carlh.net>> wrote:
Hi Shanu,
It could be. I guess there's no way to be sure. Someone else on
the list
might have an idea... Sorry I can't be more help.
All the best,
Carl
On Sun, 19 Mar 2017, Shanu Novic wrote:
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net <mailto:DCPomatic@carlh.net>
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic Thanks for your reply.
I just created a DCP using DCP-o-matic, but when I try to play it
with easyDCP trial version, it gives me warnings.
It says "Issues have been detected. For a full report, please
license the commercial edition with issue report enabled", so I
don't know what the exact
issue is.
Do you think it's the XML one that's listed under FAQ on your website?
Does it always happen with DCPs created using DCP-o-matic?
On Tue, Mar 14, 2017 at 7:56 PM, Carl Hetherington <cth(a)carlh.net
<mailto:cth@carlh.net>> wrote:
On Tue, 14 Mar 2017 16:34:41 +0900
Shanu Novic via DCPomatic <dcpomatic(a)carlh.net
<mailto:dcpomatic@carlh.net>> wrote:
> Hello everyone,
Hi Shanu,
> I had a quick question.
>
> What's the difference between DCP-o-matic and Davinci Resolve (without
> using easyDCP plugin) in terms of how they convert source material
> into
> jpeg2000 (XYZ color space)?
>
> My master video is Apple Prores HQ.
>
> Basically, I have used Davinci Resolve (without using easyDCP
> plugin) and
> openDCP to make a DCP in the past, and I was successful, but Davinci
> Resolve crashes randomly sometimes these days, so I wanted to give
> DCP-o-matic a shot.
I'm afraid I don't know what Resolve does. In theory they
should be
the same, since there is a pretty-well defined mathematical
operation
that should be followed to convert video to XYZ.
Someone else on the list might know...
> I guess I can just do a test conversion with DCP-o-matic and check the
> result with my eyes, but I thought it wouldn't hurt to ask...
That would be a good starting point, I think.
All the best,
Carl
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net <mailto:DCPomatic@carlh.net>
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic