Open
Bug 1331134
Opened 9 years ago
Updated 3 years ago
Standardize RTCStreamRTPStats
Categories
(Core :: WebRTC, defect, P3)
Tracking
()
NEW
| backlog | webrtc/webaudio+ |
People
(Reporter: ng, Assigned: ng)
References
Details
(Keywords: dev-doc-needed)
Our RTCStreamTrackStats implementation reports frameRateMean and frameRateStdDev, neither of which are standardized [0]. We should move to standardize them, or remove them from our RTCStreamTrackStats report.
[0] https://w3c.github.io/webrtc-stats/#msstats-dict*
|
||
Updated•9 years ago
|
backlog: --- → webrtc/webaudio+
Rank: 25
Priority: -- → P2
|
Assignee | |
Updated•9 years ago
|
Assignee: nobody → na-g
|
||
Updated•9 years ago
|
Keywords: dev-doc-needed
|
|
||
Updated•9 years ago
|
Summary: Standardize or remove frameRateMean, and frameRateStdDev in RTCStreamTrackStats → Remove frameRateMean and frameRateStdDev from RTCStreamStats
|
|
||
Comment 1•9 years ago
|
||
With framesEncoded and bytesReceived, you can compute both the frame rate and the bitrate, so none of the following non-standard attributes are needed anymore:
double bitrateMean;
double bitrateStdDev;
double framerateMean;
double framerateStdDev;
(From discussion with jib and ng in IRC just now)
Summary: Remove frameRateMean and frameRateStdDev from RTCStreamStats → Standardize RTCStreamRTPStats
|
||
Comment 2•9 years ago
|
||
How to calculate fps using framesEncoded: https://jsfiddle.net/jib1/6j072zcx/
|
||
Comment 3•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•