Cancellation of encoding and further restarting results in a corrupted DCP

[scorpio81]

Hi everyone!
Recently we have encountered the following problem (on DOM 2.7.1). If encoding process is cancelled and then restarted again (no settings changed) it results in a corrupted DCP. Server just freezes (tested on Dolby DSS200) at any timecode presumably before cancellation point, but if I skip behind that point playback continues normally.
My mate projectionist told me that if the name of DCP was changed prior to restarting then this new DCP would be playable from start to end.
So it follows the question. How can I stop encoding, shut down my notebook, take it to my working place and restart encoding to get playable DCP? Should I pause and then shut down? Or what?
Oh, by the way, in all cases encoding took place on main machine and several encode servers. Could this be an issue?

[carl]

Hi, that shouldn't happen ... is the problem easy to reproduce for you?

[scorpio81]

My first attempt to reproduce problem was successful.
The encoding process was cancelled at 4% progress, then restarted in about 10 or 20 seconds. As I wrote I changed nothing, just restarted (Make DCP). Verification of already encoded frames passed and encoding continued as always.
Tested DCP on DSS200 server - it is playable from 5th second, before that point playback freezes.
Zipped Log file is attached. If you need any other file - just let me know.

[carl]

Are you ok to install a test version with some more debugging code in it?

[scorpio81]

Sure I'm ok. Test version 2.8.1?

[carl]

Let me make you one up with some more debugging. I'll put up a message when it's ready.

[scorpio81]

Ok, I'm waiting.
Meanwhile I'll give you more information.
EasyDCP Player+ Demo 1.3.1 refuses to play DCP too. It gives me error message "Reading from MXF file failed. Frame at specified position contains unsupported essense".
If DCP is re-wrapped with new name (using previously encoded video and audio) and ingested to Dolby, Dolby marks it with red frame icon which means "unsupported" and refuses to play it completely.

[scorpio81]

Just checked my test encoding re-wrapped - no red frame symbol but still playable from 5th second.
Analyzed mxf files.
In original DCP hash of j2c file is different from one in PKL.
In re-wrapped DCP hash of j2c file is the same as in original DCP and in new PKL. But new pcm file has hash different from original pcm file but equals that in new PKL.

[carl]

Please could you reproduce with this version and send the logs again?

[scorpio81]

Here you go.
Quite strange, but the 1st try gave me normal DCP - checked it on DSS200. So I deleted the folder completely and gave it a 2nd try. The DCP was unplayable. More of that, EasyDCP Player informed me that audio and video had different durations.