I am a uber-noob user,
sorry if this question is too obvious, but I've searched the forum and have looked at the manual and I don't seem to find a satisfactory answer.I've recently made a couple of DCPs and when I run the "DCP verification" in the DCP-o-matic 2 Player it gives me this same 3 warnings for both DCPs.
What do these warnings mean and how can I repair them? I understand (maybe wrongfully) that these are "warnings" and not "errors", so maybe it's not a situation critical enough to the point of rendering my DCP unplayable... I don't have access to a DCP projector right now, so I haven't been able to test it yet (other than that, the DCP seems to play fine in the DCP-o-matic 2 Player). If an xml is malformed on line 0, is this something I can repair manually? Should I try repacking the DCP? (without reencoding to jpeg2000, reusing the mxf). I would also like to know more about the nature and meaning of these errors.
I'm attaching 3 of the xml files in one of my DCPs. Given that it gives me the same warnings in both DCPs, I understand that it's exactly the same issue in both of them. The only xml I'm not attaching is VOLINDEX, because it doesn't seem to be affected (not mentioned in the warnings), and also because the maximum number of files allowed to attach in a post on this forum is 3.
I'm using DCP-o-matic version 2.15.102 on a Windows 7 machine.
The reason I'm using the test version instead of the stable 2.14.40 is, in short, that this test version has a new function that lets the user interpret the color range of the input file.
I had the same problem as this user (apparent clipping in the lowest and highest levels on input) viewtopic.php?f=2&t=198 but in my case, rendering in full rgb instead of rec.709 didn't solve the issue. I don't know, it may be related with the way ffmpeg interprets the file on input, because the crushing in blacks can already be clearly seen in the preview image in DCP-o-matic. In the test version, this issue was solved by selecting "jpeg 0-255" in the range option. In version 2.14.40 I've had this same problem in files using DNxHD 4444 compression (both in rec.709 and full range rendered files, as I said) and also with Blackmagic RGB 10-bit uncompressed (r210) files. But well, that's another story.
Thanks for your attention, and thanks for this great piece of software. Again, I'm just a noob user, I've recently began to use DCP-o-matic in order to make the DCP for a short animated film that I've directed and that I have to send to film festivals. It's probably the only time I'll be using it in years (I don't plan to make any more DCPs of my works as this is the only one that I have to send to film festivals), but I have to say I'm amazed at how "mature" DCP-o-matic seems to be, congrats!
TL;DR
DCP verification in the DCP-o-matic gives me warnings of malformation in 3 xml files. "The XML in filename is malformed on line 0". Is this something I should worry about? Cheers.