Closed nlef closed 5 months ago
For camera with resolution 2592x1944
one frame takes up 20 MB on disk
A catalog of timelapses for long prints can take up a lot of space.
It’s probably worth trying to use archiving with fast algorithms as an optional option
Added the ability to compress raw data the size of one frame was reduced to 8.5 MB I think this is an acceptable trade-off between performance and disk space.
The main idea is to save raw pixel arrays received from the camera when creating a timelapse. In the current implementation there is a double conversion
It is proposed to remove unnecessary conversions, while leaving the ability to save lapse images for additional processing through additional configuration parameters