Improve log messages around plugin loading - #1186
Merged
Merged
Conversation
lukasIO
requested review from
MaxHeimbrock,
alan-george-lk,
ladvoc,
stephen-derosa and
xianshijing-lk
as code owners
June 24, 2026 10:13
Contributor
ChangesetThe following package versions will be affected by this PR:
|
xianshijing-lk
approved these changes
Jun 24, 2026
xianshijing-lk
left a comment
xianshijing-lk
left a comment
Contributor
There was a problem hiding this comment.
are you able to test it with agent SDK and verify it logs the proper errors ?
Merged
xianshijing-lk
pushed a commit
that referenced
this pull request
Jun 30, 2026
> [!IMPORTANT] > Merging this pull request will create these releases # webrtc-sys 0.3.36 (2026-06-30) ## Features ### Add `MaintainFramerateAndResolution` to `DegradationPreference` enum to align with WebRTC M144. - `MAINTAIN_FRAMERATE_AND_RESOLUTION` is now the recommended value (replaces deprecated `DISABLED`) - `DISABLED` is deprecated but still supported for backwards compatibility - Both values map to the same behavior: maintain framerate and resolution, dropping frames if needed ## Fixes - Fix AV1 subscriber decode when packet trailers are enabled. # libwebrtc 0.3.39 (2026-06-30) ## Features ### Improve initial video quality by setting `x-google-start-bitrate` SDP hint for all video codecs (VP8, VP9, AV1, H264, H265) and defaulting to `MaintainResolution` degradation preference. This addresses the issue where video starts blurry for several seconds before improving, by: 1. Telling WebRTC's bandwidth estimator to start at 70% of target bitrate instead of ramping up from ~300kbps 2. Preferring frame drops over resolution reduction when bandwidth is constrained The `DegradationPreference` option is now exposed via FFI for Python, C++, Unity, and Node SDKs. ### Add `MaintainFramerateAndResolution` to `DegradationPreference` enum to align with WebRTC M144. - `MAINTAIN_FRAMERATE_AND_RESOLUTION` is now the recommended value (replaces deprecated `DISABLED`) - `DISABLED` is deprecated but still supported for backwards compatibility - Both values map to the same behavior: maintain framerate and resolution, dropping frames if needed ## Fixes - Fix AV1 subscriber decode when packet trailers are enabled. # livekit-ffi 0.12.68 (2026-06-30) ## Features - Add `user_data` support to frame metadata, allowing arbitrary application-supplied bytes to be attached to a video frame via the `PTF_USER_DATA` packet trailer feature. ### Improve initial video quality by setting `x-google-start-bitrate` SDP hint for all video codecs (VP8, VP9, AV1, H264, H265) and defaulting to `MaintainResolution` degradation preference. This addresses the issue where video starts blurry for several seconds before improving, by: 1. Telling WebRTC's bandwidth estimator to start at 70% of target bitrate instead of ramping up from ~300kbps 2. Preferring frame drops over resolution reduction when bandwidth is constrained The `DegradationPreference` option is now exposed via FFI for Python, C++, Unity, and Node SDKs. ### Add `MaintainFramerateAndResolution` to `DegradationPreference` enum to align with WebRTC M144. - `MAINTAIN_FRAMERATE_AND_RESOLUTION` is now the recommended value (replaces deprecated `DISABLED`) - `DISABLED` is deprecated but still supported for backwards compatibility - Both values map to the same behavior: maintain framerate and resolution, dropping frames if needed ## Fixes - Fix AV1 subscriber decode when packet trailers are enabled. - Improve log messages around plugin loading - #1186 (@lukasIO) # livekit-protocol 0.7.10 (2026-06-30) ## Features - Add `user_data` support to frame metadata, allowing arbitrary application-supplied bytes to be attached to a video frame via the `PTF_USER_DATA` packet trailer feature. # livekit 0.7.50 (2026-06-30) ## Features - Add `user_data` support to frame metadata, allowing arbitrary application-supplied bytes to be attached to a video frame via the `PTF_USER_DATA` packet trailer feature. ### Improve initial video quality by setting `x-google-start-bitrate` SDP hint for all video codecs (VP8, VP9, AV1, H264, H265) and defaulting to `MaintainResolution` degradation preference. This addresses the issue where video starts blurry for several seconds before improving, by: 1. Telling WebRTC's bandwidth estimator to start at 70% of target bitrate instead of ramping up from ~300kbps 2. Preferring frame drops over resolution reduction when bandwidth is constrained The `DegradationPreference` option is now exposed via FFI for Python, C++, Unity, and Node SDKs. ### Add `MaintainFramerateAndResolution` to `DegradationPreference` enum to align with WebRTC M144. - `MAINTAIN_FRAMERATE_AND_RESOLUTION` is now the recommended value (replaces deprecated `DISABLED`) - `DISABLED` is deprecated but still supported for backwards compatibility - Both values map to the same behavior: maintain framerate and resolution, dropping frames if needed ## Fixes - Fix AV1 subscriber decode when packet trailers are enabled. - Improve log messages around plugin loading - #1186 (@lukasIO) Co-authored-by: knope-bot[bot] <152252888+knope-bot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Before you submit your PR
Make sure the following is true before submitting your PR:
PR description
Describe the changes in this PR. Explain what the PR is meant to solve and how to reproduce the issue in the first place.
Breaking changes
If this PR introduces breaking changes, list them here and document the rationale for introducing such a change.
MSRV
If the PR modifies the crate's MSRV (Minimum Supported Rust Version), document it here.
Testing
Ideally, unit test the code you add, but ensure you're not repeating existing test cases. Use as many already written scaffolding, utilities as possible; write your own, when needed. If external services, APIs, tokens are required (e.g., running an LK server instance), provide the necessary information. Make sure your tests perform useful, context-aware assertions and do not simply emulate "happy paths".
Async
We want the project to be runtime-agnostic, so please reuse what's already in livekit-runtime and feel free to add anything missing. It's ok to use Tokio directly, when writing unit tests, if necessary. When testing, do not use artificial delays for the state to "catch up"; instead, respect the event flow and subscribe properly using channels or other mechanisms.