Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why no Jitter for RTCOutboundRTPAudioStream? #228

Closed
djalmaaraujo opened this issue Jun 20, 2017 · 3 comments
Closed

Why no Jitter for RTCOutboundRTPAudioStream? #228

djalmaaraujo opened this issue Jun 20, 2017 · 3 comments

Comments

@djalmaaraujo
Copy link

Hello, I would like to know why the SPECS is not adding Jitter to RTCOutboundRTPStreamStats objects?

Chrome used to have this implemented in special flags, but always reliable for Inbound or Outbound.

I know this project is not related to chrome, but I would like to know how it's possible to get the jitter for RTCOutboundRTPStreamStats objects in this case?

Thanks.

@vr000m
Copy link
Contributor

vr000m commented Jun 27, 2017

The jitter for the outbound stream, i.e., the metric reported in the RTCP Receiver Report (RR), is available in the related remote object.

http://rawgit.com/w3c/webrtc-stats/master/webrtc-stats.html#dom-rtcremoteinboundrtpstreamstats since it inherits from RTCReceivedRTPStreamStats

AFAICT, Chrome does not currently implement any remote objects.

@djalmaaraujo
Copy link
Author

@vr000m Thanks for your answer. In Chrome 58+ with the new Spec implementation, I can only find jitter in the inbound, unfortunately. Thanks for your attention on this.

These are the options available in chrome 58+:

"RTCCodec_InboundAudio_0"
"RTCCodec_InboundAudio_103"
"RTCCodec_InboundAudio_104"
"RTCCodec_InboundAudio_105"
"RTCCodec_InboundAudio_106"
"RTCCodec_InboundAudio_110"
"RTCCodec_InboundAudio_111"
"RTCCodec_InboundAudio_112"
"RTCCodec_InboundAudio_113"
"RTCCodec_InboundAudio_126"
"RTCCodec_InboundAudio_13"
"RTCCodec_InboundAudio_8"
"RTCCodec_InboundAudio_9"
"RTCCodec_OutboundAudio_110"
"RTCCodec_OutboundAudio_111"
"RTCIceCandidatePair_PPgO5Gu9_4lcBLYP7"
"RTCIceCandidate_4lcBLYP7"
"RTCIceCandidate_PPgO5Gu9"
"RTCInboundRTPAudioStream_2241787686"
"RTCMediaStreamTrack_local_audio_e5f39725-
"RTCMediaStreamTrack_remote_audio_a0_2241787686"
"RTCMediaStream_local_ePzpEYoCX3TjptkSjzUUH51zzByZFz4ieQt4"
"RTCMediaStream_remote_N8yj0WGDixhoP1cMPMBS8IDWuJtEO1zs"
"RTCOutboundRTPAudioStream_262070451"
"RTCPeerConnection"
"RTCTransport_audio_1"

@henbos
Copy link
Collaborator

henbos commented Jul 12, 2017

Chrome currently does not implement any remote objects but they're in the spec. I filed a webrtc bug https://crbug.com/webrtc/7979 to track this, I think we can close this one?

@henbos henbos closed this as completed Jul 12, 2017
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

No branches or pull requests

3 participants