| Age | Commit message (Collapse) | Author |
|
When checking existing image data go from the end backwards until
a good hash is found rather than from the start forwards until
a bad hash is found. This is a lot quicker for long files but
may miss a corrupted frame somewhere (however unlikely this is).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
images that are kept around in memory before pushing to disk.
|
|
to the DCP.
|
|
|
|
|
|
files.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
so it can be overwritten, even on Windows.
|
|
writing to do already.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
movement with still-image DCPs (#130).
|
|
|
|
|
|
back to the GUI.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|