Hi everyone,
Just have a general question about the verification process of the DOM Player.
It is awesome to verify the integrity of the DCP and the compliance of the file and metadata to SMPTE and IOP standards.
I was wondering if anyone could elaborate a little more about the differences between the DOM verification and the one done by ClairMeta (https://github.com/Ymagis/ClairMeta) another open source tool I recently discovered (and wondering if I should try to install as a complement of DOM)... don't know if the developers are familiar with it.
Also, I was wondering if there was any plan to develop other verification tools, specifically bandwidth graphical representation (or graphical video bitrate analysis) to check if some part of the stream exceed the spec entered while creating the DCP (like in easyDCP player or in this free tool which sadly require to send the DCP over the net but seems to rely on ClairMeta : https://www.d-cine.net/free-dcp-quality ... nce-tools/).
Anyway, thanks a lot for this amazing tool !!
All the best,
Alex
Question about DCP verification process
-
Carsten
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Question about DCP verification process
Usually, if you create DCPs with DCP-o-matic, there is little need to perform verification, as DCP-o-matic tries hard to create correct DCPs. A hash check may be advisable after e.g. you transferred a DCP to a distribution drive that you want to send away.
If you receive DCPs from questionable sources often, you should probably install all verification tools that you can get a hand on.
Clairmeta is certainly a good tool and well maintained. The trouble is - even if a DCP is formally correct, it doesn't mean that some distribution or mastering company won't complain about certain aspects of the DCP that are formally correct, but doesn't fit their company workflow habits.
Currently, there is an interesting issue about Dolby DSS200/CAT862 servers exhibiting display anomalies with mainstream content released recently (MI:7) - no verification tool was triggered, because there seems to be a very specific compatibility issue between some recent J2K encoder software update and the CAT862 J2K decoder. This is the first occurrence I know of since DCP went wide 15 years ago.
- Carsten
If you receive DCPs from questionable sources often, you should probably install all verification tools that you can get a hand on.
Clairmeta is certainly a good tool and well maintained. The trouble is - even if a DCP is formally correct, it doesn't mean that some distribution or mastering company won't complain about certain aspects of the DCP that are formally correct, but doesn't fit their company workflow habits.
Currently, there is an interesting issue about Dolby DSS200/CAT862 servers exhibiting display anomalies with mainstream content released recently (MI:7) - no verification tool was triggered, because there seems to be a very specific compatibility issue between some recent J2K encoder software update and the CAT862 J2K decoder. This is the first occurrence I know of since DCP went wide 15 years ago.
- Carsten