BetteRED
Introduction
bettered automatically transcodes a given path of flac files to mp3 files based on desired quality (MP3 V0 or MP3 320) and creates a corresponding torrent file with a specified announce url.
bettered uses Moe to initialize and read the configuration, and the plugin moe_transcode to handle the transcoding logic.
Installation:
1. Install bettered from PyPI
I recommend using pipx to install bettered.
$ pipx install bettered
If you don't care about having bettered and it's dependencies (mainly Moe) in an isolated environment, you can just install normally with pip as well.
$ pip install bettered
2. Install mktorrent
mktorrent must be built from source unless your package manager includes >=v1.1
$ git clone https://github.com/Rudde/mktorrent.git
$ cd mktorrent
$ sudo make install
3. Install ffmpeg
https://ffmpeg.org/download.html
Run ffmpeg -h to ensure it's in your path.
4. Configure
Your configuration file should exist in "~/.config/bettered/config.toml" and should look like the following:
enable_plugins = ["transcode"]
[transcode]
transcode_path = "~/transcode"
[bettered]
torrent_file_path = "~/torrents"
announce_url = "https://flacsfor.me/213/announce"
[move]
album_path = "{album.artist} - {album.title} ({album.year})"
transcode_path is where the transcoded albums will be placed.
torrent_file_path is where the .torrent files will be places
announce_url your announce url for your tracker of choice.
album_path is the format of the album path. This will also have the bitrate automatically appended. See the Moe docs for more information on customizing this value.
5. Run
bettered -h
Contributing:
1. Fork the repository and create a feature/bug fix branch
2. Install development requirements
$ poetry install
3. Hack away
4. Lint your code
$ pre-commit run -a
5. Submit a pull request
Metadata
Release files for bettered 1.1.0
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 |
|---|---|---|---|---|
| bettered-1.1.0.tar.gz | 16.1 kB | Without provenance | Details for bettered-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bettered-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for bettered-1.1.0-py3-none-any.whl |
Total release size: 32.1 kB
Release files / bettered-1.1.0.tar.gz
| Download URL | bettered-1.1.0.tar.gz |
|---|---|
| Size | 16.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62e897abf2f43301d97af54911d1de087c7c919001593a16226e6928a74775ce
|
|
BLAKE2b-256 checksum How to use checksums |
ce04a003cc6fd1bb814a772b063fb1a08bf8e4671d1d418adafa3348da7ee6ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.10.6 Linux/5.15.79.1-microsoft-standard-WSL2
|
Release files / bettered-1.1.0-py3-none-any.whl
| Download URL | bettered-1.1.0-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38b10f53531a43c2f2ddf8591f559c757637a87037d55599723dd8371c8a1c01
|
|
BLAKE2b-256 checksum How to use checksums |
fae4646fd2f3c2ee49f7475936f0483125447f793a897966c6f30db83da712d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.2.2 CPython/3.10.6 Linux/5.15.79.1-microsoft-standard-WSL2
|
Security for bettered 1.1.0
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.