Skip to main content

tatolab-rive

A Rive animation as a stream source, built the way a third party builds one: a standalone maturin wheel that depends on tatolab-stream, pyo3, tatolab-module-sdk and the consumer RHI, and on no engine crate.

  • RiveSource plays a .riv file's state machine in its own processor interpreter. On start() it lends its video output and data input to this wheel's Rust. A thread there creates a Vulkan device on the runtime's GPU through the consumer RHI's external-renderer device, builds rive-runtime's Vulkan renderer on it, and per frame draws the artboard into a texture from the node's output pool and publishes a VideoFrame naming it. No frame is copied, and Python never runs at frame cadence.
  • Config: riv_path, artboard and state_machine (the file's defaults when absent), width, height and frame_rate (1920, 1080 and 60).
  • data takes msgpack maps from view-model property path to value, applied to the artboard's default view-model instance. A path the instance lacks is logged once and skipped.

Linux only for now.

Build it

build.rs fetches rive-runtime at a pinned revision and builds it with rive-runtime's own build/build_rive.sh, together with the C++ bridge in native/. It needs git, ninja, clang, make, python3, glslangValidator, spirv-opt, nm and objcopy on PATH, and libuuid's headers (uuid-dev) for premake. Set TATOLAB_RIVE_RUNTIME_DIRECTORY to build against a checkout of your own.

Run it

streams/rive-lower-third is a camera with the lower third composited over it by tatolab-compositor's AlphaOverCompositor, encoded and exposed. With this machine's runtime running and a camera attached, put a lower third at streams/rive-lower-third/lower_third.riv (or set RIV_PATH), and set TITLE_PROPERTY_PATH and ENTRANCE_TRIGGER_PATHS in stream.py to match its view model and state machine, then:

cd streams/rive-lower-third
tatolab dev

The stream exposes H.264 at http://127.0.0.1:4446/watch/<machine>/main, and the source's thread logs its frame rate every 600 frames.

Check it

cargo fmt --all --check && cargo test --locked --lib && cargo clippy --locked --lib --all-targets -- -D warnings
uv venv --python 3.12 .venv && VIRTUAL_ENV=.venv uv pip install ../../sdk/tatolab-stream mypy
VIRTUAL_ENV=.venv uvx maturin@1.9.6 develop
.venv/bin/python -m mypy.stubtest tatolab.rive._native && uvx pyright@1.1.411

rive-runtime and the C++ projects it builds are under their own licences; see THIRD-PARTY-NOTICES.md.

Metadata

Release files for tatolab-rive 0.68.32

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for tatolab-rive 0.68.32
File Interpreter ABI Platform Actions
tatolab_rive-0.68.32-cp312-abi3-manylinux_2_28_x86_64.whl CPython 3.12 abi3 Linux glibc 2.28+ x86-64 Details for tatolab_rive-0.68.32-cp312-abi3-manylinux_2_28_x86_64.whl

Release files / tatolab_rive-0.68.32-cp312-abi3-manylinux_2_28_x86_64.whl

Download URL tatolab_rive-0.68.32-cp312-abi3-manylinux_2_28_x86_64.whl
Size 3.2 MB
Tags CPython 3.12 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
eff7bbe9b3cf13136c5b201cd4fdf7d512ffbb5882f451f5c1d88f4699bce0dc
BLAKE2b-256 checksum
How to use checksums
db5a36ef4061bfba55717b96f9692b57b50282fca81c88b6e5fd9372a3a8a48c
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-rive 0.68.32

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page