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
RTCMediaStreamTrackStats.concealedAudibleSamples added. #215
Conversation
Is it OK to have the user agent decide what is considered audible? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for me. AFAIK we generally shy away from specifying quality or performance related behavior when it comes to media output. @jesup what do you think?
webrtc-stats.html
Outdated
(see <a>concealedSamples</a>) that was played out during an audible portions of the | ||
stream. Audible means that the received audio is not considered background noise or | ||
silence by the user agent. It is up to the implementation to determine what is | ||
considered background noise. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add: The value is set to undefined for user-agents that do not implement this metric.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
Discuss this at TPAC, because we do not seem to move forward on this. Especially since the metric is not standardised anywhere . @dontcallmedom @aboba @stefhak |
TPAC decision was if there is a citable reference then lets move ahead, else this PR can be closed. |
We don't have a citable reference. Sounds like a case for the incubator spec. |
Fixes #202