Implement external post processing
This commit is contained in:
21
README.md
21
README.md
@@ -48,3 +48,24 @@ These are the sections describing the sensors.
|
||||
* `rate=15` the refresh rate in fps to use for the sensor
|
||||
* `fmt=BGGR8` sets the pixel and bus formats used when capturing from the sensor, only BGGR8 is fully supported
|
||||
* `rotate=90` the rotation angle to make the sensor match the screen
|
||||
|
||||
# Post processing
|
||||
|
||||
Megapixels only captures raw frames and stores .dng files. It captures a 5 frame burst and saves it to a temporary
|
||||
location. Then the postprocessing script is run which will generate the final .jpg file and writes it into the
|
||||
pictures directory. Megapixels looks for the post processing script in the following locations:
|
||||
|
||||
* ./postprocess.sh
|
||||
* $XDG_CONFIG_DIR/megapixels/postprocess.sh
|
||||
* ~/.config/megapixels/postprocess.sh
|
||||
* /etc/megapixels/postprocess.sh
|
||||
* /usr/share/megapixels/postprocess.sh
|
||||
|
||||
The bundled postprocess.sh script will copy the first frame of the burst into the picture directory as an DNG
|
||||
file and if dcraw and imagemagick are installed it will generate a JPG and also write that to the picture
|
||||
directory. It supports either the full dcraw or dcraw_emu from libraw.
|
||||
|
||||
It is possible to write your own post processing pipeline my providing your own `postprocess.sh` script at
|
||||
one of the above locations. The first argument to the script is the directory containing the temporary
|
||||
burst files and the second argument is the final path for the image without an extension. For more details
|
||||
see postprocess.sh in this repository.
|
||||
|
Reference in New Issue
Block a user