Go to file
Theelgirl 4affd7bf51 Speed up ffmpeg part of H.265 encoding/decoding
At the expense of a bit of video size (~5% bigger files). This will cause files previously encoded with the H.265 codec to be incompatible. Since H.265 is still an experimental feature though and hasn't been released to PyPi, this will not be a major version bump.
2021-02-26 10:55:59 -05:00
docs Update changelog 2021-02-25 10:59:48 -08:00
fvid Speed up ffmpeg part of H.265 encoding/decoding 2021-02-26 10:55:59 -05:00
.gitignore docs 2021-02-21 11:24:12 -08:00
.readthedocs.yml Update Docs 2021-02-25 10:50:49 -08:00
CHANGELOG.md Update changelog 2021-02-25 10:59:48 -08:00
LICENSE.md add license 2020-10-07 07:06:25 -07:00
README.md update README 2020-10-29 13:45:19 +03:00
requirements.txt Update requirements.txt 2021-02-25 10:53:41 -08:00
setup.py Remove unneeded lines 2020-10-28 17:10:54 +00:00

README.md

Maintenance PyPI license

Demonstration/Explanation Video

fvid is a project that aims to encode any file as a video using 1-bit color images to survive compression algorithms for data retrieval.

fvid


Installation

Requires installation of FFmpeg and libmagic first, then install using pip3

Linux/macOS

pip3 install fvid 

Windows

py -m pip install fvid 

Usage

Encoding files as videos

Linux/OSX

fvid -i [input file] -e
fvid -i [input file] --framerate 1 -e
fvid -i [input file] --password "wow fvid is cool" -e

Windows

py -m fvid -i [input file] -e
py -m fvid -i [input file] --framerate 1 -e
py -m fvid -i [input file] --password "wow fvid is cool" -e

Retrieving data from videos

Linux/OSX

fvid -i [input video] -d

Windows

py -m fvid -i [input video] -d

If the file was encoded with a non-default password, it'll prompt you to enter the password upon decoding.

How to Contribute

  1. Check for open issues or open a fresh issue to start a discussion around a feature idea or a bug here tag for issues that should be ideal for people who are not very familiar with the codebase yet.
  2. Fork the repository on GitHub to start making your changes to the master branch (or branch off of it).
  3. Write a test which shows that the bug was fixed or that the feature works as expected.
  4. Send a pull request and bug the maintainer until it gets merged and published. :)