DCP File Possibly Not Created Correctly

[PhillipSerafin]

My Team and I were able to ingest the DCP into the projector finally but noticed that the film has moments where it flickers to a green and black screen for a second then continues playing (It did this a number of 10 times during the screening). Is there any way to prevent this when creating the DCP? I was told by a projectionist that this is due to the DCP being mixed down incorrectly but I am unsure on what I could do differently to prevent it.. Maybe there is something I overlooked, I am open to trying any viable thesis.

[carl]

Ouch - my guess would be either some corruption during the transfer (quite unlikely) or a data rate that's close to the limit. Can you verify your DCP with the DCP-o-matic player (load it, go to Tools -> Verify...) and see what it says?

[Carsten]

Can you play these broken segments with DCP-o-matic player and check for anomalies? You could also perform a verification in the player (latest 2.16. or 2.18.5). That should tell you wether there is something wrong with the DCP.

On which media has this DCP been created and transported to the cinema server?

As Carl says, I have seen this happening with Doremi servers when the J2K datarate was set too high. Is this a 4K DCP? Can you find out what exact type of playback server has been used - Doremi, Dolby, GDC, Sony...
Note that projector and server are different devices and brands.

[IoannisSyrogiannis]

Is this post related to the same DCP which you tried to troubleshoot ingestion for in the following thread?
https://dcpomatic.com/forum/viewtopic.php?p=13001

edit: It might be that the DCP was not created correctly. When we are talking, though, about DCP-o-matic, which is used by a lot of people to create DCPs, the rarity of your problem is probably connected with and a result of its use. So, in order to provide any useful help, the fellow forum users will need to know as much as possible about what were the specifics/parameters of the creation. Solely the failed outcome won't suffice.

[PhillipSerafin]

Can you play these broken segments with DCP-o-matic player and check for anomalies? You could also perform a verification in the player (latest 2.16. or 2.18.5). That should tell you wether there is something wrong with the DCP.

On which media has this DCP been created and transported to the cinema server?

As Carl says, I have seen this happening with Doremi servers when the J2K datarate was set too high. Is this a 4K DCP? Can you find out what exact type of playback server has been used - Doremi, Dolby, GDC, Sony...
Note that projector and server are different devices and brands.

I will try this. The server is Doremi, I've been told about the J2K but not sure where to find anything regarding that in this process. For some reason the DCP I created wouldn't open up on my end anymore (Through DCP O Matic) which is very odd. So I will render out another DCP but this time instead of using Apple ProRes I will render as JPEG2000 which is essentially the same thing since they both turn the file into an MXF, correct me if I am wrong about that (Still learning as I go).

[PhillipSerafin]

Is this post related to the same DCP which you tried to troubleshoot ingestion for in the following thread?
https://dcpomatic.com/forum/viewtopic.php?p=13001

edit: It might be that the DCP was not created correctly. When we are talking, though, about DCP-o-matic, which is used by a lot of people to create DCPs, the rarity of your problem is probably connected with and a result of its use. So, in order to provide any useful help, the fellow forum users will need to know as much as possible about what were the specifics/parameters of the creation. Solely the failed outcome won't suffice.

Yes, so the solution was that DCP O Matic had a new update that I was unaware of until I visited the site. Once I updated the software, the film ingested perfectly into the projector.

[PhillipSerafin]

Can you play these broken segments with DCP-o-matic player and check for anomalies? You could also perform a verification in the player (latest 2.16. or 2.18.5). That should tell you wether there is something wrong with the DCP.

On which media has this DCP been created and transported to the cinema server?

As Carl says, I have seen this happening with Doremi servers when the J2K datarate was set too high. Is this a 4K DCP? Can you find out what exact type of playback server has been used - Doremi, Dolby, GDC, Sony...
Note that projector and server are different devices and brands.

I will try this. The server is Doremi, I've been told about the J2K but not sure where to find anything regarding that in this process. For some reason the DCP I created wouldn't open up on my end anymore (Through DCP O Matic) which is very odd. So I will render out another DCP but this time instead of using Apple ProRes I will render as JPEG2000 which is essentially the same thing since they both turn the file into an MXF, correct me if I am wrong about that (Still learning as I go).

Another update, I was able to get the player to work and everything on my end looks good. I also rendered out a JPEG 2000 and it came out way more contrasted than it is supposed to be so I can use that one.

[IoannisSyrogiannis]

Is this post related to the same DCP which you tried to troubleshoot ingestion for in the following thread?
https://dcpomatic.com/forum/viewtopic.php?p=13001

edit: It might be that the DCP was not created correctly. When we are talking, though, about DCP-o-matic, which is used by a lot of people to create DCPs, the rarity of your problem is probably connected with and a result of its use. So, in order to provide any useful help, the fellow forum users will need to know as much as possible about what were the specifics/parameters of the creation. Solely the failed outcome won't suffice.

Yes, so the solution was that DCP O Matic had a new update that I was unaware of until I visited the site. Once I updated the software, the film ingested perfectly into the projector.

The mismatching of the hash check during insgest was a result of a dated DCP-o-matic version? Nope.

You have got it correctly the second time, transferring from project folder to the cinema server, and that's great, but your explanation is not valid.
If you want to avoid hash check errors in ingesting, make sure that the very same files created by the program reach the cinema server.

[PhillipSerafin]

Is this post related to the same DCP which you tried to troubleshoot ingestion for in the following thread?
https://dcpomatic.com/forum/viewtopic.php?p=13001

edit: It might be that the DCP was not created correctly. When we are talking, though, about DCP-o-matic, which is used by a lot of people to create DCPs, the rarity of your problem is probably connected with and a result of its use. So, in order to provide any useful help, the fellow forum users will need to know as much as possible about what were the specifics/parameters of the creation. Solely the failed outcome won't suffice.

Yes, so the solution was that DCP O Matic had a new update that I was unaware of until I visited the site. Once I updated the software, the film ingested perfectly into the projector.

The mismatching of the hash check during insgest was a result of a dated DCP-o-matic version? Nope.

You have got it correctly the second time, transferring from project folder to the cinema server, and that's great, but your explanation is not valid.
If you want to avoid hash check errors in ingesting, make sure that the very same files created by the program reach the cinema server.

Very odd that when I updated the software it started ingesting every single time consistently.We have ingested it a number of 4 different times on multiple projectors since then and have been successful (There are no more errors on the file according to the projector). When putting the file into DCP O Matic Player, there were no errors there either. But when screening the film there are several one second flickers of green and black. A very odd situation.

[Carsten]

You need to get different issues straight. File corruption may occur and will usually result in the DCP being rejected by the server during ingest. You won't see glitches or green flash frames, because the Doremi will not play the file at all. playback issues like those you mention will usually be caused by the J2K datarate being too high. This is a 100% correct DCP, but the classic Doremi servers are not able to play DCPs with data rates approaching the formal DCI limit.

When writing a DCP, DCP-o-matic will perform the same data integrity check as the Server does during ingest. However, data corruption may still occur during writing the DCP, or when transferring it to the server - bad disks, bad cables, software issues, drivers, etc. These are usually caught by the servers hash check during ingest.