Proto commits in livekit/rust-sdks

These commits are when the Protocol Buffers files have changed: (only the last 100 relevant commits are shown)

2026-10-05

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

2026-09-25

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

2026-09-22

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

2026-09-18

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

2026-09-17

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Capture: clock source (#1351) Add a capture source that renders a wall clock using the GPU. This is useful for video latency measurements. Closes: BOT-549 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

The documentation is generated from this commit.

Capture: pattern source (#1350) Add a capture source that renders a test pattern using the GPU. This has two variants: - Gradient: animated color gradient - Logo: bouncing LiveKit logo These are useful during development to get a video source without extra dependencies (e.g., a GStreamer pipeline). Closes BOT-548 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

2026-09-11

Capture: scaffold for FFI (#1349) Add the scaffolding for exposing `livekit-capture` functionality over FFI. Closes BOT-547 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Fix FFI FEC option mapping Co-authored-by: chenosaurus <509698+chenosaurus@users.noreply.github.com>

2026-09-10

Expose pre-encoded video ingest through FFI (#1418)

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-09-09

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

Add pre-encoded video ingest FFI

2026-09-08

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-08-31

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-08-28

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-08-27

Expose source over FFI

Initial RTSPs (secure) support

Expose source over FFI

2026-08-25

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-08-24

Expose source over FFI

Expose source over FFI

Expose source over FFI

Expose source over FFI

Define capture protocol

2026-08-10

Merge remote-tracking branch 'origin/main' into ladvoc/livekit-capture

Clock source Also extract render infra shared with pattern source.

Logo pattern

other_sdks (#1317) Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

2026-08-08

Pattern source Supersedes shader and demo source

2026-08-07

Make demo source shader backed

other_sdks for specifying sdk info beyond client-sdk-*

2026-08-05

other_sdks

2026-08-03

Device facade

Uniform source construction - No default impls for config - Uniform constructor naming

2026-07-30

Merge remote-tracking branch 'origin/main' into ladvoc/livekit-capture

2026-07-29

Expose capture over FFI

2026-07-28

Data streams v2 (#1192) ### Overview This change introduces data streams v2, a set of major updates to data streams to add three things: 1. Single packet data streams for short (< 15kb), finite length payloads 2. DEFLATE compression, when both the sender and all receivers support compression/decompression 3. A maximum 15kb size for data stream attributes to close this as a DOS vector For information about important decisions made in data streams v2, [see the spec](https://github.com/livekit/client-sdk-js/blob/data-streams-v2/DATA_STREAMS_SPEC.md). In particular, parts 1-5 provide a good high level overview of data streams v1 + v2, what these protocol improvements are aiming to acheive, and why certain choices were made when designing the protocol. Also maybe of interest is [the corresponding web sdk pull request](https://github.com/livekit/client-sdk-js/pull/1985). These updates are fully backwards compatible - the sdk will fall back to data streams v1 whenever an old participant is in the room. There is also a significant amount of new test coverage to data streams (both v1 and v2). There were some small bugs I found along the way which I fixed as well. --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Started manual work to add protos

2026-07-27

Data track schema metadata (#1159) Adds support for associating schema metadata with a published data track and storing/retrieving schema definitions. Schema storage is built on-top of data blobs, a general purpose mechanism for storing large (in the order of KBs), arbitrary data blobs in a room: - Protocol: https://github.com/livekit/protocol/pull/1595 - SFU implementation: https://github.com/livekit/livekit/tree/raja_async_attributes Protocol additions for schema metadata: - https://github.com/livekit/protocol/pull/1553 Closes BOT-368 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

2026-07-23

feat: add temporary flag to disable advertising data streams v2 support The node and python sdks today have their own data streams implementations. If this branch were merged today, then it would mean that the new client_protocol=2 would be advertised, and these pre-existing implementations would receive data stream v2 messages, not v1 (ie, single packet data streams, compression, etc). So for now, add a flag which can be set in livekit-ffi to disable advertising the new client protocol so this can be merged. Once merged, node and python can be updated to pass this flag. Then, once data streams v2 is done on both node + python and both are updated, this flag can be removed by reverting this commit.

feat: add support for data stream trailer attributes via livekit-ffi

feat: add RoomDataStreamOptions to livekit-ffi This allows configuring the data stream max payload size value when constructing a room.

feat: add ability to override data stream sender identity This is required for the python / node sdks to adopt the standardized data stream implementation, since it uses this feature for (I think) avatars

feat: allow data stream compress option to be toggled via livekit-ffi

2026-07-17

Expose custom encoding identifiers over FFI

Expose data track fields over FFI

Expose over FFI

2026-07-10

Fix existing issues

2026-07-09

feat: allow data stream compress option to be toggled via livekit-ffi

2026-07-08

feat: allow data stream compress option to be toggled via livekit-ffi