Honestly, I did not test it myself so far, but, if a CLI verify is needed, maybe use Clairmeta - as it verifies a lot deeper?

Hi,

Looking at the source it is evident DCP-o-matic have some unique verification checks among the free inspection tools (dcp_inspect, Clairmeta and DOM). Specifically the DOM verifier is a more or less complete implementation of the requirements of RDD52.

The other two tools have none or few checks in the j2k code stream for example. The DOM verifier does all code stream checks as specified in RDD52.

I really encourage further development of the verifier functionality in DOM. It is very useful!

It is also very beneficial to have different open tools implementing DCP verification in slightly different ways, it helps make all of them better in the long run.

Best,
Mattias

@carl we can package dcpverify from libdcp (see branch) but the tricky part is how it finds its tags directory; all the logic to find that is in dcpomatic; linux uses LINUX_SHARE_PREFIX (which is broken in packages, perhaps? prefix vs destdir); windows/mac use relative paths from the main executable. This stuff could be put into libdcp; the directory_containing_executable method is trivial on boost > 1.61.0.

dcpomatic wscript uses --install-prefix, which is why it works, but which should probably be --destdir

I wasn't aware RDD52 is already in the player verification. I know Carl was working on adding more functionality.

Quite a bit of it is there now, 0001798 has some (vague!) details. I'm hoping to get it more or less complete before 2.16.0.

Ah, okay, I saw this, but thought it was in DCP-o-matic main in order for created DCPs to follow RDD52 constraints and issue warnings, etc.

Indeed, that was the initial idea but then it seemed to make sense to add it to the verifier; this has taken quite a while though!

A new tool dcpomatic2_verify is packaged on Windows, Mac and (hopefully!) Linux in 19210abafb6e5963760951f8b115ac9ee69cfcf3 which will be in 2.15.136