This derives from my PhD thesis: Deng, J., Large Vocabulary Automatic Chord Estimation from Audio Using Deep Learning Approaches. PhD thesis, Department of Electrical and Electronic Engineering, The University of Hong Kong, 2016
However the code of this work is written in matlab (https://github.com/tangkk/tangkk-mirex-ace). So I try to port those code into python. But this is by no means a direct porting. It is meant to be minimalist version of ACE, which keeps only the algorithmic gist of the original work.
Compared with the original version which supports sevenths chords and inversions, this piece of code currently only supports maj and min triads, and it has much more elegant (only a few lines of) feature extraction and segmentation codes, which leverages librosa and hmmlearn.
1 maintainer
Metadata
1 maintainer
Release files for pyace 0.1.1
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 |
|---|---|---|---|---|
| pyace-0.1.1.tar.gz | 11.4 kB | Without provenance | Details for pyace-0.1.1.tar.gz |
Release files / pyace-0.1.1.tar.gz
| Download URL | pyace-0.1.1.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
865216f32aabeaa66eada205b03cabde32d01137dd1a3cc05e1c377f1cc7dbf4
|
|
BLAKE2b-256 checksum How to use checksums |
84f5379d9f221e6c65d67687423677b00696d35a51e85931bc91614fc2b87372
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pyace 0.1.1
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.
