After I made my first few timelapse videos I got really bothered by the erratic small changes of exposure, which are caused by various effects: * Changes of the exposure settings (if not in full manual mode) * Uncertainties of the aperture * Shutter jitter
I was looking for an existing solution and only found expensive (O(100€)) software.
So I wrote this little (150 SLOCS) programm. The brightness of the images are adjusted to fit a rolling mean over several consecutive images.
Installation
I recommend anaconda, it comes with the heavy dependencies of this package: numpy and scikit-image
Installation of deflicker:
$ pip install deflicker
Usage
deflicker expects all your pictures in one directory. The alphabetical order has to be equivalent to the chronological order.
deflicker <inputfolder> [options]
Options
-o <dir>, --outdir=<dir> Output directory [default: deflickered]
-w <N>, --window=<N> Window size for rolling mean [default: 10]
-q, --quiet Only output errors and warnings
-f <fmt>, --format=<fmt> Output format for the scaled images [default: png]
-s <s>, --sigma=<s> Sigma for the sigma clipping
1 maintainer
Metadata
1 maintainer
Release files for deflicker 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| deflicker-0.1.1post1.tar.gz | 4.4 kB | Without provenance | Details for deflicker-0.1.1post1.tar.gz |
Release files / deflicker-0.1.1post1.tar.gz
| Download URL | deflicker-0.1.1post1.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eeba4a0e1a833e86565eb73f7fd5a993926bff830bc1ea3b557e4bd2c8a55fcb
|
|
BLAKE2b-256 checksum How to use checksums |
e2e15f0aa3d299837d397ee4d3cb9bc38d54157fc42d59c97888d4d6650d8795
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for deflicker 0.1.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
