DCP rejected due to Guardbit value

[worldofcrap]

Hi guys,

I just had an IOP trailer sent to Deluxe, who rejected it because of the MXF’s guardbit value. “The guardbit value is something we’ve started to validate within every picture MXF which is now part of the DCI spec.

2K image must be encoded with a guardbit value of 1
4K image must be encoded with a guardbit value of 2”

I have no idea what this is. Anyone else have any issues with this?

[carl]

It is a detail of the JPEG2000 encoding. DCP-o-matic should do the right thing in versions from the last year or so.

Did you make the DCP with DCP-o-matic? If so, what version?

[worldofcrap]

Yes, this was made yesterday with ver 2.14.54 git 89b5a8f65a. Not current, but not super old.

[carl]

Right, sadly too old to have this fix - if you install the current stable version and re-make the DCP it should have the correct guard bits. I would suggest deleting the DCP and the "video" folder from inside your project to make sure that the video MXF is re-created.

[worldofcrap]

Brilliant. Thanks so much!

[Carsten]

BTW - current versions of DCP-o-matic player also check this during validation. Formally, it should not be an issue for Interop features, only SMPTE but, once these companies start QC something that has not been created by themselves, they just love to find something to complain about


- Carsten

[worldofcrap]

I have definitely noticed that!! Thanks for the info!

[angrydcp]

Hi! Do you know if there is a way to find this guarbit number in metadata or some place to check if there is correct? To make sure before validations.

Thanks in advance!!

[carl]

If you run the DCP-o-matic validation it should give an error if the guard bit value is wrong. It's not easy to see by manual inspection of the files.

[angrydcp]

Great! Thankyou!