Raja Subramanian 710e06b7da Tweak screen share stream tracker. (#683) ...

* Tweak screen share stream tracker.

Screen share uses extremely low frame rate when content is static.
This leads to stream tracker changes and layer switches.
Use a longer measurement interval for screen share tracks.
Setting it to 4 seconds. The screen share frame rate is
approx. 1 fps and with two temporal layers, it should get
a frame every 2 seconds or so in every layer. But, that
does not work. Even three second measurement window was
reporting 0 rate. So, it is getting clumped. 4 seconds works
fine.

Also modifying the bit rate availability change to trigger
on a temporal layer becoming available or going away.

With these changes, on a local test, not seeing any unnecessary
PLIs from client and hence no unnecessary key frames from publisher.

* Fix test

2022-05-13 10:18:18 +05:30

..

clientconfiguration

Code inspection (#581)

2022-03-30 13:49:53 -07:00

config

Update WebRTC and DTLS with security fixes (#678)

2022-05-10 18:27:16 -07:00

logger

Use common logging init functions (#633)

2022-04-20 00:15:11 -07:00

routing

Add back region when hydrating ParticipantInit. (#648)

2022-04-24 09:07:33 -07:00

rtc

Update WebRTC and DTLS with security fixes (#678)

2022-05-10 18:27:16 -07:00

service

Skip loading of participant before writing messages to them. (#654)

2022-04-24 23:09:06 -07:00

sfu

Tweak screen share stream tracker. (#683)

2022-05-13 10:18:18 +05:30

telemetry

Keep track of retransmissions in NodeStats (#677)

2022-05-10 15:25:24 -07:00

testutils

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

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

utils

Do not post close callback in ops queue if not started. (#649)

2022-04-24 11:40:22 +05:30