Skip to content

feat: added support for raw stats from RTCPeerConnection#37

Open
dnovicki wants to merge 1 commit intoaws:masterfrom
dnovicki:raw-stats-fn
Open

feat: added support for raw stats from RTCPeerConnection#37
dnovicki wants to merge 1 commit intoaws:masterfrom
dnovicki:raw-stats-fn

Conversation

@dnovicki
Copy link

Issue #, if available:
Currently the getStats() returns data that is translated and highly structured. This does not give client's much flexibility when compiling stats from the call.

Description of changes:
Added getStatsRaw() to enable clients to digest the raw stats from RTCPeerConnection object rather than the media tracks themselves.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Copy link

@pallab-gain pallab-gain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to be a very useful feature for users who want to build their own quality control implementation and algorithm based on the RTC stats. Thanks for exposing this.

I was wondering whether we can check iceConnectionState for 'connected' or 'completed' instead of signalingState to be 'stable' ? Because, signalingState can also be 'stable' when there is no active connection, for example in the initial state( https://www.w3.org/TR/webrtc/#rtcsignalingstate-enum ) before SDP generate, and negotiation, and in this state RTCStats doesn't provide useful stats.

RTCStats in different ice, and signaling state :
https://jsfiddle.net/pallab8077/skuomjpa/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants