tatolab-webrtc
WHIP publish and WHEP play for Tatolab streams, as an extension wheel:
Rust inside, two ordinary @node classes as the binding.
New to Tatolab? Install the Tatolab app first. This package adds two nodes to a stream project; the Tatolab runtime, which comes with the app, is what runs them. See Install Tatolab and the Quickstart.
In a stream project:
uv add tatolab-webrtc
It installs from PyPI with the tatolab-stream package it depends on.
from tatolab.webrtc import WhepPlayer, WhipPublisher
Both read and write media frames — hang's legacy container, a QUIC varint timestamp in
microseconds and then the Annex-B access unit or Opus packet — with a keyframe opening a group.
WhipPublisher takes one fan-in input, tracks — each inbound link becomes one RTP track,
video or audio by the codec its upstream port's catalog entry names. WhepPlayer writes
encoded_video and encoded_audio, and states each port's catalog entry — the codec string,
the coded extent, the channel count and the OpusHead — from the stream itself.
Both sit on the encoded side of the codec blocks: H264Encoder / OpusEncoder upstream of
the publisher, H264Decoder / OpusDecoder downstream of the player.
See WebRTC (WHIP and WHEP) for full examples and how a session behaves.
1 maintainer
Metadata
1 maintainer
Release files for tatolab-webrtc 0.55.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tatolab_webrtc-0.55.4-cp310-abi3-manylinux_2_28_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| tatolab_webrtc-0.55.4-cp310-abi3-macosx_15_0_arm64.whl | CPython 3.10 | abi3 | macOS 15.0+ ARM64 | Details |
Total release size: 11.5 MB
Release files / tatolab_webrtc-0.55.4-cp310-abi3-manylinux_2_28_x86_64.whl
| Download URL | tatolab_webrtc-0.55.4-cp310-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
05c894ccac0fe59b80629bb3516ef1283816e3a1305eb6e4f62400a5c72696c9
|
|
BLAKE2b-256 checksum How to use checksums |
4deb72c0d8b86e54eb5d1d9bab9d0de7088ed45832328540c711a8233b282401
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tatolab_webrtc-0.55.4-cp310-abi3-macosx_15_0_arm64.whl
| Download URL | tatolab_webrtc-0.55.4-cp310-abi3-macosx_15_0_arm64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.10 abi3 macOS 15.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3773666b3217b325e3aa9a818ed74483c65164e369a9eac18df126e5830eda9a
|
|
BLAKE2b-256 checksum How to use checksums |
051956535963f7a8937101ec267d5e20c68dfb88780bc1f70a9ce5b2e8c745f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tatolab-webrtc 0.55.4
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.
