Proto commits in livekit/rust-sdks

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

Commit:672d0e2
Author:lukasIO
Committer:lukasIO

Add Room::prepare_connection Like prepareConnection in the JS SDK, prepare_connection fetches the region list of a LiveKit Cloud project before connecting, and keeps it fresh with keep_fresh in a task. The next SignalClient::connect to the same project stops that task, dials the first cached region, and the session's own refresh takes over. If that region fails, it is marked failed and the other regions are tried, as in JS. The prepare refresh has three ends: a connect to the host, a later prepare for the host, which replaces it, or a 401 from the region endpoint, which comes once the token expires. The WebSocket opens its own TCP and TLS connection, so unlike JS this does not warm DNS or TLS for the signal connection. The FFI room surface gets PrepareConnectionRequest. The core-modules surface is unchanged: Swift and Android run their own prepareConnection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Commit:fdba8c6
Author:Ryan Gaus
Committer:GitHub

docs(livekit-ffi): drop the data track co-ownership and dependency comments

The documentation is generated from this commit.

Commit:dc71678
Author:Ryan Gaus
Committer:GitHub

docs(livekit-ffi): document data track co-ownership across the FFI surfaces A local data track unpublishes when its last owner drops it. Once a C ABI track handle has been taken up over UniFFI, the handle map and the UniFFI side co-own the track, so dropping the handle alone no longer unpublishes it. Say so on the proto handles and where the handle map stores the tracks, and add the livekit-ffi changeset for the data track work.

Commit:4990474
Author:Alan George

Remove GStreamer audio playout

Commit:b29a7e3
Author:Alan George
Committer:Alan George

feat(capture): add GStreamer audio capture and playout Add fixed 10 ms PCM audio capture and mixed remote-track playout through GStreamer. Separate audio and video source modules while sharing pump lifecycle and frame-count results, with FFI support, documentation, and tests.

Commit:b4ef012
Author:Jacob Gelman

Expose error code over FFI

Commit:9cbb67e
Author:cloudwebrtc

Align publisher FEC options with FECProtection mode and level Replace the FecProtection level enum with a { mode, level } struct that mirrors FECProtection in the LiveKit protocol, exposing the adaptive and minimum modes alongside fixed protection. Update the FFI message, node bindings, example, and docs to match.

Commit:6047beb
Author:Alan George

feat(capture): add GStreamer audio capture and playout Add fixed-format PCM audio capture and mixed remote-track playout through GStreamer, with shared capture lifecycle controls, audio statistics, FFI messages, and tests.

Commit:0937521
Author:cnderrauber
Committer:cnderrauber

Add PrewarmedConnection to open the signalling connection ahead of connect A PrewarmedConnection is a TCP (+TLS for wss/https) connection to the LiveKit server opened before Room::connect. Passed as RoomOptions::prewarmed_connection, the first signal connect only performs the WebSocket upgrade over it, with the same URL, query and headers as a normal connect. - livekit-net: PrewarmedConnection::{connect, is_alive, close}. Used at most once; a watcher task notices a server close or reset. A dead connection, one opened for another host, or an upgrade that fails or exceeds 1.5s (reached only on a silent drop) falls back to a fresh dial; HTTP error statuses are returned as-is. Not used with HTTP(S)_PROXY or a host-registered transport. - livekit-signaling / livekit: SignalOptions/RoomOptions::prewarmed_connection, used by the first open_transport attempt only. - livekit-ffi: PrewarmRequest/PrewarmCallback returning an owned handle, PrewarmedConnectionAliveRequest, and RoomOptions.prewarmed_connection_handle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Commit:b0fe69d
Author:Alan George

Merge remote-tracking branch 'origin/ladvoc/livekit-capture' into alan/capture-audio Co-authored-by: Cursor <cursoragent@cursor.com> # Conflicts: # Cargo.lock # Cargo.toml # libwebrtc/src/native/video_frame.rs # libwebrtc/src/video_frame.rs # livekit-capture/Cargo.toml # livekit-capture/README.md # livekit-capture/src/encoded/h26x.rs # livekit-capture/src/encoded/mod.rs # livekit-capture/src/encoded/pump.rs # livekit-capture/src/error.rs # livekit-capture/src/lib.rs # livekit-capture/src/pixel/pump.rs # livekit-capture/src/primitive.rs # livekit-capture/src/pump.rs # livekit-capture/src/renderer.rs # livekit-capture/src/sources/clock.rs # livekit-capture/src/sources/gstreamer.rs # livekit-capture/src/sources/mod.rs # livekit-capture/src/sources/pattern.rs # livekit-ffi-node-bindings/proto/ffi_pb.d.ts # livekit-ffi-node-bindings/proto/ffi_pb.js # livekit-ffi/Cargo.toml # livekit-ffi/protocol/capture.proto # livekit-ffi/protocol/ffi.proto # livekit-ffi/src/room_apis/conversion/capture.rs # livekit-ffi/src/room_apis/server/capture.rs # livekit-ffi/src/room_apis/server/requests.rs # webrtc-sys/include/livekit/video_frame_buffer.h # webrtc-sys/src/dmabuf_video_frame_buffer.cpp # webrtc-sys/src/video_encoder_factory.cpp # webrtc-sys/src/video_frame_buffer.cpp # webrtc-sys/src/video_frame_buffer.rs

Commit:2358db6
Author:Alan George

feat(capture): add bidirectional GStreamer audio Co-authored-by: Cursor <cursoragent@cursor.com>

Commit:2d62c80
Author:shijing xian

Report the final drop total at end of stream A stream can lose frames after the last one it managed to forward, and `dropped_frames` only rode on frame events, so those losses had nothing to arrive on. A track that overflows and then ends -- or a participant that leaves rather than republishing -- left them invisible, which is exactly the case the counter exists for. `VideoStreamEOS` now carries the total too. Also widens the changeset: bumping libwebrtc requires bumping its dependents.

Commit:532bfc8
Author:shijing xian

Surface dropped video frames to the application A decoded video frame can be dropped after `framesDecoded` counts it and before the application sees it, with every WebRTC stat reading zero: `framesDecoded` counts it and `framesDropped` does not. `NativeVideoStream` already counted these, but the count was only ever written -- it reached an application as a log line on the first drop and every hundredth after it. `VideoFrameReceived` now carries `dropped_frames`, and `NativeVideoStream::dropped_frames()` exposes the same counter to Rust. The total is kept per FFI stream rather than per `NativeVideoStream`. A participant stream holds one handle while the participant swaps tracks and builds a fresh `NativeVideoStream` for each, so reporting that stream's own counter would restart at zero mid-stream and a client diffing successive events would see the count go backwards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Commit:8c35899
Author:shijing xian
Committer:shijing xian

Surface dropped video frames and reuse frame conversion buffers A decoded video frame can be dropped after `framesDecoded` counts it and before the application sees it, with every WebRTC stat reading zero. Three changes make that visible and make it less likely. `VideoFrameReceived` gains `dropped_frames`, the cumulative count of frames `NativeVideoStream` discarded because the FFI forwarding task fell behind the WebRTC sink. The count already existed but was only ever written: it reached an application as a log line on the first drop and every hundredth after it. `NativeVideoStream::dropped_frames()` exposes the same counter to Rust. The libwebrtc log sink dropped each message's severity and logged everything at `Debug`, so libwebrtc warnings and errors were filtered out by default in every binding. Severity is now mapped through. Verbose and info stay noisy and move to `Trace` and `Debug`; warning and error become visible. Frame conversion drew a fresh frame-sized buffer per frame and freed it when the binding released the handle. A 1628x1920 I420 frame is 4.5 MB, so a 30 fps stream churned 134 MB/s of short-lived allocations that large, and the Windows heap sends anything over ~512 KB straight to `VirtualAlloc`, decommitting it on free. `cvt` now writes into a buffer the caller owns, and each stream keeps its own set to hand back. A buffer may only be written while nothing else holds it, and `Arc` is what knows: the FFI handle map holds a clone for as long as the binding has the frame, so a strong count of 1 means the buffer came back. `Arc::get_mut` turns "is the binding done?" into a question the borrow checker answers, rather than one the code has to get right. Nothing depends on the binding releasing promptly -- when no buffer is free the stream adds one, up to a cap, past which it allocates per frame as before. A stream therefore keeps one buffer for a binding that copies and releases immediately, and two for a zero-copy binding holding the current frame while the next arrives. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Commit:2c0bdbe
Author:David Chen

cleanup API, enable FEC by default, per-track protection disabled by default

Commit:4789840
Author:Grant Smith

Correct the single_peer_connection default in room.proto When unset, the FFI keeps RoomOptions::default(), which is true. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Commit:0f640f0
Author:Grant Smith

Declare livekit_ffi_initialize and livekit_ffi_dispose in livekit_ffi.h The shipped header declared only request and drop_handle, so a C/C++ client couldn't initialize the library from it. Also fix the ffi.proto comment that said initialization is an InitializeRequest; it's the C function livekit_ffi_initialize. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Commit:fec3da9
Author:David Chen

Merge origin/main into dc/feature/fec

Commit:ecea208
Author:Ryan Gaus

docs(livekit-ffi): drop the data track co-ownership and dependency comments

The documentation is generated from this commit.

Commit:188346e
Author:Ryan Gaus

docs(livekit-ffi): document data track co-ownership across the FFI surfaces A local data track unpublishes when its last owner drops it. Once a C ABI track handle has been taken up over UniFFI, the handle map and the UniFFI side co-own the track, so dropping the handle alone no longer unpublishes it. Say so on the proto handles and where the handle map stores the tracks, and add the livekit-ffi changeset for the data track work.

Commit:08d46a0
Author:Ryan Gaus

fix(data-streams): limit open incoming streams per participant Each incoming data stream holds receiver-side state until its trailer arrives or the sender disconnects. Cap each remote participant at 500 concurrently open streams by default and drop headers beyond that with an error log. The limit is configurable via RoomDataStreamOptions, the FFI RoomDataStreamOptions, and the core-modules incoming managers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Commit:71219b9
Author:Alan George
Committer:GitHub

livekit-capture: Join capture pumps instead of emitting a source event (#1547) ## Summary - Replace the one-shot `CaptureSourceEvent` with `JoinCaptureRequest`, which waits for the pump thread to exit and returns its terminal result. - Automatically join running pump when dropped if not explicitly joined. Stacked on #1526. --------- Co-authored-by: Jacob Gelman <3182119+ladvoc@users.noreply.github.com> Co-authored-by: Cursor <cursoragent@cursor.com>

The documentation is generated from this commit.

Commit:539909b
Author:Jacob Gelman
Committer:GitHub

Move drop handling into capture crate

The documentation is generated from this commit.

Commit:c994417
Author:Alan George
Committer:GitHub

Refactor after sync

Commit:992ad7f
Author:Ryan Gaus
Committer:GitHub

Remove transitional use_legacy_data_streams parameter (#1575) Removes the `use_legacy_data_streams` / `use_legacy_client_implementation` migration flag, which no client SDK uses anymore. ## History 1. The flag was added in #1192 (Data streams v2) as a temporary migration aid: when set, a client capped `ClientInfo.client_protocol` at `DATA_STREAM_RPC`, so it did not advertise data streams v2 support. 2. The Python and Node SDKs set it while they still had their own Python/JS data streams implementations. Without it, remote clients would have used v2-only behavior toward clients that couldn't handle it. 3. Both SDKs then switched to the Rust data streams implementation via the FFI, so they no longer needed the flag. 4. Nothing sets it anymore and this was never a user facing feature (hidden from docs, never promoted, and a user would not really want to set it anyway) so it can be removed now that it has served it's transitional purpose. ## Changes - **livekit-ffi**: Note that I have opted to keep `RoomDataStreamOptions.use_legacy_client_implementation` in `room.proto` but is marked `[deprecated = true]`. Its comment says no client SDK uses it and the FFI ignores it, and keeping it stops field number 2 from being reused. The node bindings are regenerated. - **livekit**: removes the hidden `RoomDataStreamOptions::with_legacy_client_implementation` builder. - **livekit-signaling**: removes the hidden `SignalOptions::use_legacy_data_streams` field and the `advertised_client_protocol()` helper. Both join paths now always send `CLIENT_PROTOCOL_VERSION` (data streams v2). - A changeset bumps `livekit`, `livekit-signaling`, `livekit-api`, `livekit-capture` and `livekit-ffi` by a patch version each. The removed Rust items were `#[doc(hidden)]`. --------- Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Commit:64ae483
Author:Ryan Gaus

livekit-ffi: keep use_legacy_client_implementation as a deprecated field Restore the proto field instead of reserving it, marked deprecated and documented as unused by any client SDK and ignored by the FFI. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Commit:c09b43b
Author:Ryan Gaus

livekit-ffi: remove RoomDataStreamOptions.use_legacy_client_implementation No FFI consumer sets this anymore. Reserve field 2 and its name so the tag is not reused, and regenerate the node bindings. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Commit:a264a5e
Author:Jacob Gelman
Committer:Alan George

Move drop handling into capture crate

Commit:4507954
Author:Alan George
Committer:Alan George

Refactor after sync

Commit:d2e6f5c
Author:Jacob Gelman
Committer:GitHub

Expose capture error kind over FFI (#1561) Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Commit:28117e4
Author:Jacob Gelman

Move drop handling into capture crate

Commit:a6b3123
Author:Alan George
Committer:Alan George

Refactor after sync

Commit:4ba7498
Author:Alan George

Refactor after sync

Commit:7ddce46
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:5464c95
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:032de97
Author:Jacob Gelman

Negotiated format in FFI result

Commit:78d34f2
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:3541079
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:265f797
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:c51a899
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:3dba05a
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:7146e66
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:35d7655
Author:Jacob Gelman
Committer:GitHub

Capture: GStreamer source (#1353) Add a capture source that ingests encoded video from a GStreamer pipeline. Closes BOT-551 --------- Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

Commit:3cedbcf
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:6b9a360
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:b688681
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:75c65aa
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:95efe74
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:f22fab4
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:cc00533
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:883c869
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:30c81e2
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:3281b83
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:76897b3
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:fe302a2
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:8f6b787
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:4f0bfdf
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:d685302
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:d362334
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:cc2f830
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:00009db
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:2ad91b1
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:c274a9e
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:25931c7
Author:Jacob Gelman
Committer:GitHub

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>

Commit:9548606
Author:Jacob Gelman
Committer:GitHub

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>

Commit:d1889d9
Author:Jacob Gelman
Committer:GitHub

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>

Commit:edf9beb
Author:copilot-swe-agent[bot]
Committer:GitHub

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

Commit:42d6bc5
Author:stavied
Committer:GitHub

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

Commit:35a5f13
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:8b6108a
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:fd12e9e
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:d4d8ed1
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:4484e65
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:091e5e9
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:8c80dcc
Author:Jacob Gelman
Committer:Jacob Gelman

Define capture protocol

Commit:cce63f0
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:2ba8827
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:34f24d5
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:773cb79
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:71408b4
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:f6c876e
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:28ee5a0
Author:Jacob Gelman
Committer:Jacob Gelman

Define capture protocol

Commit:5bebd80
Author:Stephen DeRosa
Committer:Stephen DeRosa

Add pre-encoded video ingest FFI

Commit:bec5f7e
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:0c011f8
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:66a4d3f
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:53d1f97
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:22dd432
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:b0254bc
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:c0e56fb
Author:Jacob Gelman
Committer:Jacob Gelman

Define capture protocol

Commit:79d9150
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:dc1d302
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:fa71164
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:a08da1f
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:ed34653
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:a2dd0ed
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:2c4fdec
Author:Jacob Gelman
Committer:Jacob Gelman

Define capture protocol

Commit:108a96e
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI

Commit:2a7437c
Author:Jacob Gelman
Committer:Jacob Gelman

Initial RTSPs (secure) support

Commit:081a53b
Author:Jacob Gelman
Committer:Jacob Gelman

Expose source over FFI