W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2014

Re: Monitoring A/V sync issues and frame drops

From: Varun Singh <vsingh.ietf@gmail.com>
Date: Wed, 20 Aug 2014 11:26:28 +0300
Message-ID: <CAEbPqrzvdnswM2YK7dqO=FAp+XujuwexXjDjjNtH5Y1qMjHbHg@mail.gmail.com>
To: Dee Cee <deeprcee@gmail.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>

Since you are discussing about chrome, there are some additional stats
appended with a `goog` identifier in getStats() which may help (e.g.,
frame playout time in ms compare that to the frame rate).

There are additional stats discussed in the wiki
(https://www.w3.org/2011/04/webrtc/wiki/Stats) but AFAIK they are not
yet implemented by any browser. From those metrics, there are a few
that may help with discerning A/V sync -- for example framesDropped,
which are typically dropped from the jitter buffer because they will
not make the intended playout time.


On Tue, Aug 19, 2014 at 11:27 PM, Dee Cee <deeprcee@gmail.com> wrote:
> Hi,
> We have a small application that uses webrtc to setup a call for video chat.
> Is there a good way to measure A/V sync issues, frame drops and audio
> glitches from webrtc code ?
> I looked into chrome://webrtc-internal but did not find a suitable graph.
> Thanks
> Dee

Received on Wednesday, 20 August 2014 08:27:15 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:00 UTC