You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue tracks AV1 support within LiveKit. AV1 offers higher bandwidth efficiency, improved visual quality, as well as SVC. We aim to support AV1 in the SFU and all of our SDKs. Currently Chrome is the only browser that supports AV1 SVC under a field trial (as of M104): --force-fieldtrials=WebRTC-DependencyDescriptorAdvertised/Enabled/
One of the main challenges with new codecs in an SFU is backwards compatibility. What happens when some users in the room are publishing AV1, but others aren't able to decode it?
Our solution to this is multi-codec simulcast: allowing the publisher to dynamically publish a backup codec if anyone in the room requests for it. This technique will be covered in detail in a future blog post.
This issue tracks AV1 support within LiveKit. AV1 offers higher bandwidth efficiency, improved visual quality, as well as SVC. We aim to support AV1 in the SFU and all of our SDKs. Currently Chrome is the only browser that supports AV1 SVC under a field trial (as of M104):
--force-fieldtrials=WebRTC-DependencyDescriptorAdvertised/Enabled/
One of the main challenges with new codecs in an SFU is backwards compatibility. What happens when some users in the room are publishing AV1, but others aren't able to decode it?
Our solution to this is multi-codec simulcast: allowing the publisher to dynamically publish a backup codec if anyone in the room requests for it. This technique will be covered in detail in a future blog post.
SFU
SDKs
JS
Swift
Kotlin (Android)
Flutter
React-Native
Rust based SDKs (Python, Node, Unity)
work is planned
Go
work is planned
The text was updated successfully, but these errors were encountered: