RWave
A utility that handle audio for Python.
Usage
Simple Example
import rwave
# Load audio file
wave, fs = rwave.read_wave('wave file path')
# Write audio file
# (wave file path, wave data, fs)
rwave.write_wave('wave file path', wave, 16000)
# Nomalize wave data
rwave.nomalize(wave)
# => audio data normalized to 0~1
# Convert sampling rate (16000->8000)
wave, fs = rwave.convert_fs(wave, 16000, 8000)
# Convert audio length (->5.0s)
wave, fs = rwave.convert_fs(wave, 16000, 5.0)
# Convert to MFCC
mfcc = rwave.to_mfcc('wave file path', 16000)
Installation
$ pip install rwave
Contributing
Bug reports and pull requests are welcome on GitHub at https://github.com/AjxLab/RWave.
1 maintainer
Metadata
1 maintainer
Release files for rwave 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rwave-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for rwave-0.1.2-py3-none-any.whl |
Release files / rwave-0.1.2-py3-none-any.whl
| Download URL | rwave-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7cd9d731153166d881ab16e260e4a837ebef1e426d136bf691666da2fdf5c7f5
|
|
BLAKE2b-256 checksum How to use checksums |
a832056683fb0d8574ed2ebf3a588dd20f8c31523377b6162c680ea04296797e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.7.5
|
Security for rwave 0.1.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.
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.
