Re: [webrtc-stats] Stat for how many adaptation changes occur for a video track

It does provide some value. Since it is monotonically increasing, it 
is helpful in catching specific issues that happen in between polling 
intervals, especially to catch if there is a rapid switching between 
different resolutions which would be hard to detect otherwise (besides
 user complaints).

We use it in conjunction with an instantaneous (currently active) 
adaptation "reason" that is reported by chrome in multiple variables:

Which help us define which limitation caused the change (we also have 
several that are defined in the app layer that we merge). I assume 
other implementations of webrtc will have reasons for adapting the 
video down, but they may not map identically with the ones Chrome 
uses.  Having the overall googAdaptationChanges would also allow for 
detecting things that may not make it into the spec from other 

All told, the absolute measure is not as useful as the reason values 
though if I had to choose one. I see the discussion on the reasons is 

GitHub Notification of comment by icydragons
Please view or discuss this issue at 
using your GitHub account

Received on Thursday, 23 February 2017 02:34:09 UTC