Raja Subramanian 6b55742564 Use available layers in optimal allocation. (#1445) ...

Addressing edge case where a layer stopped before bitrate could be
measured. Purely bit rate based change deduction missed this as
the before and after did not have bit rates.

Use available layers to look for changes, especially currently
forwarding layer going away.

Also, simplifying bits. Only in the optimal allocation path,
these things are required. When congested, bitrate is always needed.
So, for optimal path, just look at available layer changes and adjust.

Don't need to look for bitrate based layer changes. Clean up that code.

2023-02-19 11:41:40 +05:30

..

clientconfiguration

publish new codec when subscriber needed (#762)

2022-06-16 18:16:34 +08:00

config

Remove deprecated ingress rpc (#1439)

2023-02-17 11:40:38 -08:00

logger

Slight tweaks to subscription manager logging (#1345)

2023-01-29 11:45:47 -08:00

routing

Update to go-redis v9. Fixed Redis cluster support (#1415)

2023-02-12 22:22:21 -08:00

rtc

Use available layers in optimal allocation. (#1445)

2023-02-19 11:41:40 +05:30

service

finish timed version migration (#1443)

2023-02-18 12:08:08 -08:00

sfu

Use available layers in optimal allocation. (#1445)

2023-02-19 11:41:40 +05:30

telemetry

Bump up interval for sending telemetry stats to 30 seconds (#1430)

2023-02-16 15:53:58 -05:00

testutils

Expose Participant.IsPublisher to differentiate pubs from subs (#643)

2022-04-21 22:15:01 -07:00

utils

finish timed version migration (#1443)

2023-02-18 12:08:08 -08:00