W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > February 2017

Re: [webrtc-stats] Unclear which framerate "framePerSecond" represents

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Feb 2017 12:52:04 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-277671597-1486385523-sysbot+gh@w3.org>
How about?

> Only valid for video. It represents the nominal FPS value, 
pre-degradation. This is the configured framerate for this track 
attachment to the RTCPeerConnection. For local tracks this is limited 
by constraints (MediaTrackConstraintSet.frameRate, see 
[[!GETUSERMEDIA]]) and encoding parameters 
(RTCRtpEncodingParameters.maxFramerate, see [[!WEBRTC]]). For remote 
tracks this is the max framerate that the remote endpoint can receive 
as announced in the remote description ("a=framerate", see 
[[RFC4566]]). If there is no configured limit this value is undefined.

Should we also include if there are known implementation or device 
limitations then this may be set for local tracks as well? E.g. camera
 can't output more than 30 fps or the webrtc implementation doesn't 
support more than 60 fps. Or should that count as a "degradation" 
since it wasn't configured by the app?

GitHub Notification of comment by henbos
Please view or discuss this issue at 
using your GitHub account
Received on Monday, 6 February 2017 12:52:11 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:39 UTC