AutoDITag
A Tool to automatically rename and tag mp3 files
Meant to be used to create playlist files and corresponding tagged mp3 files, that can be used in DanceInterpreter
Installation and Usage
Requires Python 3.6+, mutagen and argparse
Pip
pip install auto-di-tag
auto-di-tag -f PATH_TO_DESCRIPTOR_FILE -d PATH_TO_MUSICFOLDER -n PLAYLISTNAME
Manual
git clone https://github.com/klassenserver7b/AutoDITag.git
cd AutoDITag
pip install -r requirements.txt
python3 auto_di_tag.py -f PATH_TO_DESCRIPTOR_FILE -d PATH_TO_MUSICFOLDER -n PLAYLISTNAME
How to create a descriptorfile
License
This Project is Licensed under the GNU GENERAL PUBLIC LICENSE Version 3. Therefore there is NO WARRANTY for anything regarding this code
Help Menu
usage: AutoDITag [-h] -f FILE -d DIR -n NAME
Automatically rename and tag your dance playlist
options:
-h, --help show this help message and exit
-f FILE, --file FILE Your txt file containing the playlist
-d DIR, --dir DIR The directory of the mp3 files to process
-n NAME, --name NAME The name of the Playlist. eg: Schulball 08.05.2024
see https://github.com/klassenserver7b/AutoDITag
Metadata
Release files for auto-di-tag 0.3.2
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 | |
|---|---|---|---|---|
| auto_di_tag-0.3.2.tar.gz | 9.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| auto_di_tag-0.3.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.4 kB
Release files / auto_di_tag-0.3.2.tar.gz
| Download URL | auto_di_tag-0.3.2.tar.gz |
|---|---|
| Size | 9.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
417ec3f8e219231f25ace3a2f8e6974ba8bfa11d625627ca491106076e545c2a
|
|
BLAKE2b-256 checksum How to use checksums |
a3ea8261f29247ef23c30c3ca2e23bf69b5e8ba54ee5bf489e53f8f3e395c3f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2025.
Transparency logRelease files / auto_di_tag-0.3.2-py3-none-any.whl
| Download URL | auto_di_tag-0.3.2-py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f22b57e70f6a354aa4f47982d66e02a81d709be034341e9b6c987acd336e2f26
|
|
BLAKE2b-256 checksum How to use checksums |
071e940193c310962d51a302bd0a314217d23b4f28bff09a3b331890fa9fa28b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2025.
Transparency logSecurity for auto-di-tag 0.3.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for auto_di_tag-0.3.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 1, 2025.
Transparency logA 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.