Mementoizer
A python library to Memento-ize videos.
Meaning, cut the video up into scenes, pass the first half through a black-and-white filter, and interleave them.
Created for NaMoGenMo 2022. For an example, see: https://www.youtube.com/watch?v=vkgGLhG3ccI
The original film for comparison can be viewed here: https://en.wikipedia.org/wiki/File:The_Memphis_Belle_-_A_Story_of_a_Flying_Fortress.webm
Installation
Mementoizer can be installed from PyPI:
pip install mementoizer
Usage
Command-line usage:
mementoize <video-filename>
Programmatic usage:
from mementoizer import mementoize
mementoize(video_filename, ...)
Options
--skip-start Number of seconds to ignore for cutting purposes at the beginning of the video file. For example, skipping intro credits. Default: 0
--skip-end Number of seconds to ignore for cutting purposes at the end of the video file. For example, skipping end credits. Default: 0
--min-scene-length Minimum number of seconds to count as a scene. If a cut is detected less than this many seconds after a previous one, it is disregarded. Default: 120 seconds
--threshold Parameter for tuning cut detection. Must be a float between 0 and 1. Typical values for normal shot detection are 0.4-0.6. Since we are trying to detect scene boundaries rather than plain shots, it's set a little higher by default. Default: 0.7
--overlap Number of seconds to overlap between clips (chronologically). You will see this many seconds repeated to connect the previous scene to the one you are watching now. Default: 4
--cuts Manually specify cut times, in seconds after the start of the video. If this is provided, cut detection is skipped. --skip-start, --skip-end, and --min-scene-length are still applied. Values should be comma-separated integers.
NOTE: the resulting video will start at the first timestamp you provide. So you must start the list with 0 if you don't want to skip the first scene.
--verbose Print out the cut times detected (or supplied if --cuts is specified).
--dry-run Print detected cut timstamps and exit. Do not write or modify any files.
Metadata
Release files for mementoizer 0.0.3
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 |
|---|---|---|---|---|
| mementoizer-0.0.3.tar.gz | 3.5 kB | Without provenance | Details for mementoizer-0.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mementoizer-0.0.3-py3-none-any.whl | Python 3 | none | any | Details for mementoizer-0.0.3-py3-none-any.whl |
Total release size: 7.0 kB
Release files / mementoizer-0.0.3.tar.gz
| Download URL | mementoizer-0.0.3.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b2d7453614c3557d5260f040f39e63997b6666963f37caf50d214a2082e079f
|
|
BLAKE2b-256 checksum How to use checksums |
c738b9f3eb8a2c45ede4031d3caf26a61250fa42f80b54bb959db21d94f7dfb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / mementoizer-0.0.3-py3-none-any.whl
| Download URL | mementoizer-0.0.3-py3-none-any.whl |
|---|---|
| Size | 3.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
337726205478286e39a5b34e434089f8a877feef566e0a674dc3d300ff6ae33b
|
|
BLAKE2b-256 checksum How to use checksums |
d848cc3e7a9848e2edb012f694ff1619bd0337906f4712fc0b9fc65e7b5dc0eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for mementoizer 0.0.3
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.