audups
Command line tool for finding similar audio files using their AcoustID fingerprints
Requirements
- chromaprint (for fingerprint calculation)
- ffmpeg (to read audio files)
Note that this project is only intended to be used on Linux, support for other operating systems will not be provided.
Usage
audups /path/to/music
Compare the files in /path/to/music with themselves, printing similar ones.
You can set the threshold at which matches are printed using --threshold x, where x is a number between 0.0 and 1.0.
audups MUSIC1 MUSIC2
Compares the files in MUSIC1 to the files in MUSIC2
audups --a MUSIC1 MUSIC2 --b MUSIC3
Compares the files in MUSIC1 and MUSIC2 to the files in MUSIC3
(Note that files specified in --a are not compared with other files specified in --a)
Metadata
Release files for audups 0.1.post6
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 | |
|---|---|---|---|---|
| audups-0.1.post6.tar.gz | 9.8 kB | Without provenance | Details |
Release files / audups-0.1.post6.tar.gz
| Download URL | audups-0.1.post6.tar.gz |
|---|---|
| Size | 9.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e5f0643622a78eb7110b2cda56018462fbf74990924da57157a68a2ebc99805
|
|
BLAKE2b-256 checksum How to use checksums |
833c6ecf1ddada56c875ac9ebd0e974fc99cc43a7a6d5d09d7c641b16029e60d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.10.7
|
Security for audups 0.1.post6
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.