Issue metadata
Sign in to add a comment
|
Tracking bug for getUserMedia latency constraint
Reported by
tnakamura@webrtc.org,
Jul 6 2015
|
||||||||||||||||||||
Issue descriptionAs seen in the latest version of the spec: https://w3c.github.io/mediacapture-main/getusermedia.html
,
Jul 7 2015
Assigning to myself for now, bug is still available if anyone wants to beat me too it (vacation coming up)
,
Dec 7 2015
,
Dec 12 2016
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue.
,
Dec 12 2016
Guido, can you make it blocked on the Chromium bug you're using on the algorithm project?
,
Feb 17 2017
,
Sep 1 2017
Hello, we (at Soundtrap) would be interested in helping to implement this in Chromium if the work is not already underway. We helped implement the Web Audio latencyHint recently to reduce output latency and are very interested in the ability to lower the input latency as well, specifically in ChromeOS for our case. Would it be useful for us to look into setting up an initial CL around this for discussion? Thanks for any help!
,
Sep 1 2017
andrew.macpherson@: Feel free to send a CL for discussion. It would be useful for sure.
,
Sep 1 2017
Moving to assigned since I haven't started work on the latency constraint itself. Will wait for Soundtrap's WIP CL to start the discussion.
,
May 14 2018
,
Jul 18
,
Jul 18
,
Jul 26
Hi guidou@, I'd like revisit this since it looks like the constraints work is now complete. I could either upload a new patch to the old CL from last fall (https://chromium-review.googlesource.com/c/chromium/src/+/650410) or else start a new one. Would that work for you? Thanks!
,
Aug 14
,
Aug 23
,
Oct 8
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hta@webrtc.org
, Jul 6 2015