You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting RTCRemoteOutboundRtpStreamStats from backend.
What happened?
Only getting RTCInboundRtpStreamStats which are probably generated on front-end.
...
Based on this commit, 891d96f
I assumed that support for these stats had been implemented. Please tell me if this is really the case. If so, what could be the reason for the lack of these reports? It would be nice to permanently recieve round-trip latency numbers
The text was updated successfully, but these errors were encountered:
@icypow During my testing, audio is working fine, but video is missing. It looks like remote-outbound-rtp for video wasn't supported prior to 2024, based on the information available. See more RTCRemoteOutboundRtpStreamStats (Chrome)
Starting Chrome 125 (I didn’t find the WebRTC release notes for Chrome 125), the getStats API now returns the missing remote-outbound-rtp report for video.
@ashutoshmishraji Switched to 135 Chrome build and not recieved any reports video-kind. As it mentioned in your link I recieve both remote- and inboud- reports for audio and still just inbound- for video
Uh oh!
There was an error while loading. Please reload this page.
Your environment.
What did you do?
Connecting videostream to pion then sending it to web.
What did you expect?
Getting RTCRemoteOutboundRtpStreamStats from backend.
What happened?
Only getting RTCInboundRtpStreamStats which are probably generated on front-end.
...
Based on this commit,
891d96f
I assumed that support for these stats had been implemented. Please tell me if this is really the case. If so, what could be the reason for the lack of these reports? It would be nice to permanently recieve round-trip latency numbers
The text was updated successfully, but these errors were encountered: