BenchmarkSTT
About
This is a command line tool for benchmarking Automatic Speech Recognition engines.
It is designed for non-academic production environments, and prioritises ease of use and relative benchmarking over scientific procedure and high-accuracy absolute scoring.
Because of the wide range of languages, algorithms and audio characteristics, no single STT engine can be expected to excel in all circumstances. For this reason, this tool places responsibility on the users to design their own benchmarking procedure and to decide, based on the combination of test data and metrics, which engine is best suited for their particular use case.
Usage examples
Returns the number of word insertions, deletions, replacements and matches for the hypothesis transcript compared to the reference:
benchmarkstt --reference reference.txt --hypothesis hypothesis.txt --diffcounts
Returns the Word Error Rate after lowercasing both reference and hypothesis. This normlization improves the accuracy of the Word Error Rate as it removes diffs that might otherwise be considered errors:
benchmarkstt -r reference.txt -h hypothesis.txt --wer --lowercase
Returns a visual diff after applying all the normalization rules specified in the config file:
benchmarkstt -r reference.txt -h hypothesis.txt --worddiffs --config conf
Further information
This is a collaborative project to create a library for benchmarking AI/ML applications. It was created in response to the needs of broadcasters and providers of Access Services to media organisations, but anyone is welcome to contribute. The group behind this project is the EBU’s Media Information Management & AI group.
Currently the group is focussing on Speech-to-Text, but it will consider creating benchmarking tools for other AI/ML services.
For general information about this project, including the motivations and guiding principles, please see the project wiki
To install and start using the tool, go to the documentation.
Metadata
Release files for benchmarkstt 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 |
|---|---|---|---|---|
| benchmarkstt-1.1.tar.gz | 36.5 kB | Without provenance | Details for benchmarkstt-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| benchmarkstt-1.1-py3-none-any.whl | Python 3 | none | any | Details for benchmarkstt-1.1-py3-none-any.whl |
Total release size: 87.9 kB
Release files / benchmarkstt-1.1.tar.gz
| Download URL | benchmarkstt-1.1.tar.gz |
|---|---|
| Size | 36.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d55cf005b1fac94279a466bff2145b8e5c7f6097160e383c1da46582482260fc
|
|
BLAKE2b-256 checksum How to use checksums |
d1413cbea4465eb19cb82363f70350757b6c28b90941244c8a9bf1db2bc9e267
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Release files / benchmarkstt-1.1-py3-none-any.whl
| Download URL | benchmarkstt-1.1-py3-none-any.whl |
|---|---|
| Size | 51.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b1ee62cc16ac593b542cfe16d0f35ce3bff26ada80b25b6f92576e68a906877a
|
|
BLAKE2b-256 checksum How to use checksums |
04e9d1e8fcde4e3a3eb656d409595eff52d0b461c7f1246a968a07b293f660cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.9.1
|
Security for benchmarkstt 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.