meetwave-stream (Python)
Live text while people speak (English, Spanish, Portuguese, Russian; German, French and Italian as a preview), and the full transcript (with speakers and names on those tiers, in any language) right after you stop.
pip install meetwave-stream
Python 3.10+; the only dependency is websockets.
import asyncio
import os
import meetwave_stream
def show(final):
print(final["start"], final["text"])
async def main(chunks):
session = meetwave_stream.connect(api_key=os.environ["MEETWAVE_API_KEY"], tier="text", language="en")
session.on("final", show)
for pcm in chunks: # 16 kHz mono 16-bit little-endian PCM, any chunk size
session.send(pcm)
result = await session.stop()
print(result.transcript["text"])
- Send audio as soon as you have it. The first connection after a quiet period can take up to 15 s; the client keeps every word (up to 60 s) and sends it when the server is ready.
- A dropped connection is resumed on its own (6 attempts, 0.5 s to 8 s apart) from the last audio the server stored. Nothing is billed twice and no final is repeated.
- Events:
ready,partial,final,warning(low balance),reconnecting,error,closed. - Call
send,stopandclosefrom the event loop that runs the session.
Tiers and languages
| tier | at stop |
|---|---|
text |
the transcript (English: joined live text, in seconds) |
speakers |
the transcript with speakers |
names |
the transcript with speakers and their names |
Every tier has the same live text. It depends on language:
| language | live text |
|---|---|
en, es, pt, ru |
yes |
de, fr, it |
yes, preview: rougher than the transcript at stop |
any other code, or "auto" |
none; the transcript at stop |
The client names the language in the connection address too (.../v1/stream/ru), so the
first text comes sooner.
Outside English, live text writes numbers as words; the transcript at stop has digits. Billing is per second of audio at the tier's price.
Metadata
Release files for meetwave-stream 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 |
|---|---|---|---|---|
| meetwave_stream-0.1.0.tar.gz | 12.5 kB | Without provenance | Details for meetwave_stream-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meetwave_stream-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for meetwave_stream-0.1.0-py3-none-any.whl |
Total release size: 22.4 kB
Release files / meetwave_stream-0.1.0.tar.gz
| Download URL | meetwave_stream-0.1.0.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0bf7f784f1dcb80c57d9f6d5f94dbffb04b6d20e2a8e8c3af89e531050d42a9
|
|
BLAKE2b-256 checksum How to use checksums |
ebb2d68077f4860081eb290a72e9074a652b84559c7281bd226a2c9753d95994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Release files / meetwave_stream-0.1.0-py3-none-any.whl
| Download URL | meetwave_stream-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d9505712c2812488c7db9cba1624f6f6e00c184fe119433848694aa53cf45739
|
|
BLAKE2b-256 checksum How to use checksums |
a843000ec1c5c6dc1ef807648b52584916fb53eca2c164533a767c2585927451
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.0
|
Security for meetwave-stream 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.