mirdata
Common loaders for Music Information Retrieval (MIR) datasets. Find the API documentation here.
This library provides tools for working with common MIR datasets, including tools for:
- downloading datasets to a common location and format
- validating that the files for a dataset are all present
- loading annotation files to a common format, consistent with the format required by mir_eval
- parsing track level metadata for detailed evaluations
Installation
To install, simply run:
pip install mirdata
Quick example
import mirdata
orchset = mirdata.initialize('orchset')
orchset.download() # download the dataset
orchset.validate() # validate that all the expected files are there
example_track = orchset.choice_track() # choose a random example track
print(example_track) # see the available data
See the documentation for more examples and the API reference.
Currently supported datasets
Supported datasets include AcousticBrainz, DALI, Guitarset, MAESTRO, TinySOL, among many others.
For the complete list of supported datasets, see the documentation
Citing
There are two ways of citing mirdata:
If you are using the library for your work, please cite the version you used as indexed at Zenodo:
If you refer to mirdata's design principles, motivation etc., please cite the following paper:
"mirdata: Software for Reproducible Usage of Datasets"
Rachel M. Bittner, Magdalena Fuentes, David Rubinstein, Andreas Jansson, Keunwoo Choi, and Thor Kell
in International Society for Music Information Retrieval (ISMIR) Conference, 2019
@inproceedings{
bittner_fuentes_2019,
title={mirdata: Software for Reproducible Usage of Datasets},
author={Bittner, Rachel M and Fuentes, Magdalena and Rubinstein, David and Jansson, Andreas and Choi, Keunwoo and Kell, Thor},
booktitle={International Society for Music Information Retrieval (ISMIR) Conference},
year={2019}
}
When working with datasets, please cite the version of mirdata that you are using (given by the DOI above) AND include the reference of the dataset, which can be found in the respective dataset loader using the cite() method.
Contributing a new dataset loader
We welcome contributions to this library, especially new datasets. Please see contributing for guidelines.
3 maintainers
Metadata
3 maintainers
Release files for mirdata 1.0.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 | |
|---|---|---|---|---|
| mirdata-1.0.0.tar.gz | 204.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mirdata-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 468.7 kB
Release files / mirdata-1.0.0.tar.gz
| Download URL | mirdata-1.0.0.tar.gz |
|---|---|
| Size | 204.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d196c27c6c92f1a332020d95d396a81dd037b6a9eda160254731cfcc015bbbe
|
|
BLAKE2b-256 checksum How to use checksums |
18625e73697833a8f25dfd1f76f97bfc67da2b2e19f5e15f353aa6f97f87608c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / mirdata-1.0.0-py3-none-any.whl
| Download URL | mirdata-1.0.0-py3-none-any.whl |
|---|---|
| Size | 263.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c082a51a162ace9776949eb0f5e0c7850b51edd411735333fb5951922dec3952
|
|
BLAKE2b-256 checksum How to use checksums |
5cc2934b0a273b2a68b625b418e4bd240502e4bc85c68c5486abb3fc1b460970
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for mirdata 1.0.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.
