This release is a pre-release and may not be stable for production use.
# SSP - Speech Signal Processing module
SSP is released under the Gnu GPL version 3. See the file COPYING for details.
To install SSP, something like this ought to work: `sh mkdir lib cd lib git clone git@github.com:idiap/ssp.git export PYTHONPATH=~/lib `
Then in some working directory `sh ln -s ~/lib/ssp/bin/pitch.py ln -s ~/lib/ssp/bin/codec.py `
Then you can say `sh pitch.py test.wav # Graphical view of what's going on codec.py -h codec.py -r 22050 -p EM1.wav EM1.lf0 `
Otherwise, see the wiki at https://github.com/idiap/ssp/wiki
– [Phil Garner](http://www.idiap.ch/~pgarner) June 2013
Metadata
Release files for ssp 0.1a9
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 |
|---|---|---|---|---|
| ssp-0.1a9.zip | 32.6 kB | Without provenance | Details for ssp-0.1a9.zip |
Release files / ssp-0.1a9.zip
| Download URL | ssp-0.1a9.zip |
|---|---|
| Size | 32.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2954b2d762391732173b26d196b8d28b873df078d219a44b281936c3c450c7c
|
|
BLAKE2b-256 checksum How to use checksums |
30114148d028e9ce33aecbfecc66a9e38ea878c1e6f8364be5dffc1ce1d47eed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ssp 0.1a9
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.