The audio-dataset-converter-visualization library is an extension to audio-dataset-converter with plugins for visualizing audio data.
Examples can be found here:
https://github.com/waikato-llm/audio-dataset-converter-examples
Changelog
0.1.0 (2025-10-31)
switched to kasperl library for base API and generic pipeline plugins
0.0.3 (2025-07-10)
new grouping support added to writers via the –split_group option
0.0.2 (2025-03-14)
switched to underscores in project name
added placeholder support to: to-mel-spectrogram, to-mfcc-spectrogram, to-stft-spectrogram
0.0.1 (2024-07-05)
initial release
Metadata
Release files for audio-dataset-converter-visualization 0.1.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 | Actions |
|---|---|---|---|---|
| audio_dataset_converter_visualization-0.1.0.tar.gz | 7.5 kB | Without provenance | Details for audio_dataset_converter_visualization-0.1.0.tar.gz |
Release files / audio_dataset_converter_visualization-0.1.0.tar.gz
| Download URL | audio_dataset_converter_visualization-0.1.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
045defe1af42cae2b151d2e49d0fcc0c7020ab6ca7eda055c94d232970744902
|
|
BLAKE2b-256 checksum How to use checksums |
2fa5507d44272fed1e47a61b5666e939e44b3812e9d807dca0907c648fcf2ba5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.3
|
Security for audio-dataset-converter-visualization 0.1.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.