diff options
| author | Carl Hetherington <cth@carlh.net> | 2013-10-20 22:59:08 +0100 |
|---|---|---|
| committer | Carl Hetherington <cth@carlh.net> | 2013-10-20 22:59:08 +0100 |
| commit | 1481a47361119a976fd60a4b7c9b1767b339ba5c (patch) | |
| tree | 5d6dfb501493c8df04b3b22ca28e9789a57c0e55 | |
| parent | 8b136077cc74d606e083069e2435fc5a3b100b0f (diff) | |
Some notes about resuming encodes (#215).
| -rw-r--r-- | doc/manual/dcpomatic.xml | 31 |
1 files changed, 31 insertions, 0 deletions
diff --git a/doc/manual/dcpomatic.xml b/doc/manual/dcpomatic.xml index 26b48c1af..1947b1581 100644 --- a/doc/manual/dcpomatic.xml +++ b/doc/manual/dcpomatic.xml @@ -1567,5 +1567,36 @@ to the cinema which is showing your DCP. </chapter> +<chapter> +<title>Loose ends</title> + +<para> +This chapter collects a few notes on bits of DCP-o-matic that do not fit elsewhere in the manual. +</para> + +<section> +<title>Resuming encodes</title> + +<para> +If you cancel a DCP encoding run half-way through, or your computer +crashes... fear not. DCP-o-matic takes care to ensure that, in most +cases, it can resume encoding from where it left off. When you +re-start a DCP creation, using the same settings are a previous run, +DCP-o-matic will first check that the existing picture frames are +correct, and then resume from where it left off. The checking of +existing frames does take some time, but it is much faster than +running a full re-encode. +</para> + +<para> +This resumption is achieved by writing a digest (hash) to disk for +every image frame that is written. On resumption, the existing MXF +file for image data is read and its contents checked against the +hashes. +</para> + +</section> + +</chapter> </book> |