chaptermarkers
chaptermarkers will creat chapter markers in MP4 files from a text file.
Get Started!
Here’s how to set up chaptermarkers for local environment.
1- Clone the chaptermarkers locally:
$ git clone https://github.com/cbitterfield/chaptermarkers.git
2- Install your local copy into a virtualenv. Assuming you have virtualenvwrapper installed, this is how you set up the package for local development:
$ sudo make boostrap
$ mkvirtualenv chaptermarkers
$ pip install -r requirements/dev.txt
3- How to enable/disable virtualenv
$ workon chaptermarkers
$ ...
$ deactivate
Usage:
usage: chaptermarkers [-h] [–version] [-d] [-f CHAPTERS] [-m FILENAME] [-o OUTPUT] [-t TITLE]
Chapter markers creates markers in MP4 files from friendly time marks
- optional arguments:
- -h, --help
show this help message and exit
- --version
show program’s version number and exit
- -d, --debug
Turn on Debugging Mode
- -f CHAPTERS, --chapters-file CHAPTERS
Text file with chapters in it. TimeStamp space Title
- -m FILENAME, --mpeg-video FILENAME
Movie file MP4s only – Currently no checking
- -o OUTPUT, --mpeg-video-markers OUTPUT
default is FILENAME_chapters.mp4
- -t TITLE, --title TITLE
default is My Default Movie, this is the title that will show when playing
The default value for FFMPEGCMD is /opt/local/bin/ffmpeg [MAC Ports]. If your binary is in a different location use export FFMPEG=/usr/bin/ffmpeg or whatever is appropriate for your shell Temp files are written to /tmp and are remove if successful write occurs
Credits
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unrelease]
### Added - 1.2.0 Added support for microseconds - 1.1.0 Final Version with updated documentation - 0.1.0 Initial Release
[Unrelease] TBD-link
Metadata
Release files for chaptermarkers 1.2.8
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 |
|---|---|---|---|---|
| chaptermarkers-1.2.8.tar.gz | 13.7 kB | Without provenance | Details for chaptermarkers-1.2.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chaptermarkers-1.2.8-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for chaptermarkers-1.2.8-py2.py3-none-any.whl |
Total release size: 20.7 kB
Release files / chaptermarkers-1.2.8.tar.gz
| Download URL | chaptermarkers-1.2.8.tar.gz |
|---|---|
| Size | 13.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c004c63a82cfa5c7f77233d3cece4212c144f6ad559930632b3e97d919801005
|
|
BLAKE2b-256 checksum How to use checksums |
8bf2238ef14b1b75154c9670117fc406f218f61e368f10509ff4ef21d83d5928
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.7
|
Release files / chaptermarkers-1.2.8-py2.py3-none-any.whl
| Download URL | chaptermarkers-1.2.8-py2.py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
505b19e4979f06d3225e91471abc7b1d5bae3da4882b67f20b8f54ce6db0916d
|
|
BLAKE2b-256 checksum How to use checksums |
21dfc7de40ea38492be50b08852c6391c60fb7e1e3b5ead3e12e9abdb8ae288d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.25.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/3.8.7
|
Security for chaptermarkers 1.2.8
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.