mirror of
https://github.com/livekit/livekit.git
synced 2026-03-30 17:45:40 +00:00
When doing code changes for dynamic rid, inadventently relied on ordering of quality in track info layers to pick the highest layer if the requested quality is higher than available qualities. @cnderrauber addressed it in https://github.com/livekit/livekit/pull/3998. Just adding some more robustness behind that by doing a full search when requested quality is not available. Tested using JS SDK demo app and picking different qualities from subscriber side with adaptive streaming turned off.