Project flashcam
FLASk powered Hybrid webCAM
IN DEVELOPMENT
Why
Because any idea can be implemented in the code without a dependence on a closed source. And there are few ideas implemented by now.
Start
Production web interface:
export PATH=$PATH:$HOME/.local/bin
export DISPLAY=:0
killall -9 gunicorn
$( sleep 5;flashcam ask;)&
flashcamg
Just run on local network, force a port 8000
export PATH=$PATH:$HOME/.local/bin
flashcam flask -n 8000 # -p 00.0-usb-0:1.3:1.0
Select a camera
If there are two or more connected, try flashcam ls and select a
proper IDpath like flashcam flask -p 00.0-usb-0:1.3:1.0.
It is possible to run with two cameras, but with local network mode and pay attention to MJPG pixelformat and using different ports.
When config is already fine-tuned for something else
Deactivate blur, accumulate, threshold, telegram, set basic resolution, another port:
flashcam flask -p clock -a 10 -b 3 -r 640x480 -n 5000 -j False -t 0 -a 0 -b 1
Config
Located at $HOME/.config.flashcam/cfg.conf it allows to setup
basically everything.
A lot of options is possible to set and override from commandline.
Basic scenarios
Just use
Probably the option 'PIXELFORMAT':'MJPG' to read physical camera as
mjpg is fine.
High quality
When trying e.g. for astrophotography, you may prefer
'PIXELFORMAT':'YUYV' to read camera without artifacts. While it works
for 640x480, this may not be possible for higher resolution.
Motion detection
Technical details
- web.py module is the one that is called by gunicorn and provides
the interface. See frames(), where Camera() class (defined in
real
camera.py) is called first.
Development with pip and uv
Definitely things turned to uv and uvx from astral.sh{.verbatim}
requirements.txt is now kept actual, own venv works (uv venv;
uv pip install -r requirements.txt) and setup should contain correct
info too - uvx flashcam flask -p win_rain.jpg works.
This is a big deal because of PEP668.
Usage
See README.howto.org
Some references that may or may not be related
https://markhedleyjones.com/projects/calibration-checkerboard-collection
1 maintainer
Metadata
1 maintainer
Release files for flashcam 1.13.20
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 |
|---|---|---|---|---|
| flashcam-1.13.20.tar.gz | 2.6 MB | Without provenance | Details for flashcam-1.13.20.tar.gz |
Release files / flashcam-1.13.20.tar.gz
| Download URL | flashcam-1.13.20.tar.gz |
|---|---|
| Size | 2.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c051e59a73ac2c8d562b6a331a696bfd5053b8ef47939fc9d86d0a5c99c101b6
|
|
BLAKE2b-256 checksum How to use checksums |
e6225d9fc20d01392b76cbee4ae70a523e36c4e20b984b48f33d689332c1a98d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for flashcam 1.13.20
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.
