getDisplayMedia() doesn't downscale by source pixel ratio by default
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
People
(Reporter: jib, Assigned: pehrsons)
References
(Depends on 3 open bugs)
Details
The spec says: "The user agent SHOULD downscale by the source pixel ratio by default, unless otherwise directed by applied constraints."
I.e. on Retina macs where window.devicePixelRatio is 2, we should halve the width and height of unconstrained capture.
STRs:
Expected result (Chrome):
- 1536 x 960
Actual result (Firefox):
- 3072 x 1920
| Reporter | ||
Updated•4 years ago
|
| Reporter | ||
Updated•4 years ago
|
| Reporter | ||
Comment 1•4 years ago
|
||
We're seeing performance issues with 4K, so we should up-prioritize this.
| Reporter | ||
Comment 2•4 years ago
|
||
With https://jsfiddle.net/jib1/pc8yedw6/ (Click Go & share Entire Screen) I see this difference on my 2019 MBP with macOS 10.15.7 (19H1030):
- Firefox (1536 x 960): Framerate: ~8
- Chrome (1536 x 960): Framerate: ~29
That fiddle already downscales to 1536 x 960 using constraints, which suggests that fixing this bug likely won't help, and that the underlying problem is likely deeper, as suggested in bug 1703522 comment 4.
| Reporter | ||
Updated•4 years ago
|
Updated•8 months ago
|
| Assignee | ||
Comment 3•6 months ago
|
||
This shouldn't be too hard to fix, and makes the resizeMode handling complete in bug 1286945.
| Assignee | ||
Comment 4•3 months ago
•
|
||
A tad bit more complicated than I thought, because the libwebrtc capturers only tag frames with the appropriate scaling number on Windows.
| Assignee | ||
Updated•3 months ago
|
Description
•