22 Feb
2015
22 Feb
'15
5:57 p.m.
On Sun, 22 Feb 2015, Andrew Levine wrote:
Hi there,
can anyone explain these messages to me?
Fri Feb 20 10:33:51 2015: Job: Computing image digest
DCP-o-matic is starting to compute the digest for the video MXF in the DCP
it has just made.
Fri Feb 20 11:31:54 2015: Job: Computing audio
digest
Similar for the audio MXF.
Fri Feb 20 11:33:35 2015: Wrote 46158 FULL,
143758 FAKE, 26 REPEAT; 25 pushed to disk
DCP-o-matic wrote 46158 frames to disk, 143758 were already created on a
previous run, so did not need to be encoded and written.
26 were duplicated frames. This is usually due to a discontinuity in the
content, or the need to make differences between audio and video length by
adding black at the end of the DCP.
25 frames were pushed out to disk and recovered during the encoding. This
is when the queue of frames waiting to be written to disk becomes too big
because a particular frame is being awaited. e.g. if 23 is written to
disk, then 25,26,27,28...105 all become available, they must be queued in
RAM because 24 has to be written to the MXF after 23. If this queue gets
too big some of it is written to a temporary file on disk.
Regards,
Carl