A CLI that beautifies your (old) music files, automatically adds metatags based on fingerprinting, filename and metadata.
Home-page: https://github.com/kkoomen/omnitagger Author: Kim Koomen Author-email: koomen@protonmail.com License: MIT Description: # omnitagger
[](https://pypi.python.org/pypi/omnitagger) [](https://codeclimate.com/github/kkoomen/omnitagger)
Omnitagger is a CLI tool for beautifying your music files and adding metadata automatically to your files. It provides fingerprint lookup via [acoustid](https://github.com/beetbox/pyacoustid). Wether this is specified or not: after that it will check for the artist - title.{mp3,flac,ogg} format. If that pattern isn’t found either, it will check the directory the file is in, since it is a common case that when you download an album, the structure is:
` artist-name/ ├── title.mp3 ├── title.mp3 ├── title.mp3 └── title.mp3 `
If that isn’t an options either, it will skip the file and continue to the next one. For more information on how omnitagger works, visit the [How it works](https://github.com/kkoomen/omnitagger/wiki/How-it-works) page on the wiki.
# Installation
NOTE: If you have python 3.7+ installed, you won’t be able to use the fingerprint module. This due to it needs the Chromaprint module and this one is not compatible yet with Python 3.7+.
$ pip install omnitagger
Download the [Chromaprint](https://beets.readthedocs.io/en/v1.4.7/plugins/chroma.html#installing-the-library) library.
# Documentation Visit the [documentation](https://github.com/kkoomen/omnitagger/wiki/Documentation) on the wiki for further details on how to use omnitagger.
# The purpose of omnitagger The purpose of omnitagger was a personal issue we all can relate to in the early days: You download an album or song using a YouTube converter (or oldschool Limewire/Frostwire back in those days) and the names do look horrible. Names with numbers in front of it while it is already in the metatags, underscores instead of spaces… you get it. This was an issue me and a friend of mine always had and I suddenly had the idea to create a python script to make from an ugly and horrible-looking filename a good-looking filename with metatags set correctly automatically. Once I had the idea I kept building and building and sometimes even rebuilding the whole script to make it better and more efficient.
# License
MIT.
Keywords: music,beautifier,mp3,ogg,flac,local,tagger Platform: UNKNOWN Classifier: Intended Audience :: Developers Classifier: Development Status :: 5 - Production/Stable Classifier: Environment :: Console Classifier: License :: OSI Approved :: MIT License Classifier: Operating System :: POSIX Classifier: Programming Language :: Python :: 3.0 Classifier: Programming Language :: Python :: 3.1 Classifier: Programming Language :: Python :: 3.2 Classifier: Programming Language :: Python :: 3.3 Classifier: Programming Language :: Python :: 3.4 Classifier: Programming Language :: Python :: 3.5 Classifier: Programming Language :: Python :: 3.6
Metadata
Release files for omnitagger 2.1.5
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 |
|---|---|---|---|---|
| omnitagger-2.1.5.tar.gz | 8.1 kB | Without provenance | Details for omnitagger-2.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnitagger-2.1.5-py3-none-any.whl | Python 3 | none | any | Details for omnitagger-2.1.5-py3-none-any.whl |
Total release size: 17.6 kB
Release files / omnitagger-2.1.5.tar.gz
| Download URL | omnitagger-2.1.5.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8c18d7a13d3eb8864c8bad3ced2dff0bb73f91899380ec50e27894b2fb87d3b9
|
|
BLAKE2b-256 checksum How to use checksums |
f4a53c09472f9107e63c9f2aef9b59a54f9692321aa19db71adb000cab9e5119
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.5
|
Release files / omnitagger-2.1.5-py3-none-any.whl
| Download URL | omnitagger-2.1.5-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4521c8759c019ea8c5874bbcc70f892339850e712d4577ebf95dc2c15c05d6ad
|
|
BLAKE2b-256 checksum How to use checksums |
4a6b969f02889939eda869771a17f46909daf6a22b304886447a780e5cbb889e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/40.0.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.6.5
|
Security for omnitagger 2.1.5
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.