Closed Bug 1726984 Opened 3 years ago Closed 3 years ago

getUserMedia request with 1080p (Full HD) returns 720p (HD) at best

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

Firefox 91
Desktop
macOS
defect

Tracking

()

RESOLVED DUPLICATE of bug 1681334

People

(Reporter: github, Unassigned)

References

()

Details

(Keywords: parity-chrome)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.159 Safari/537.36

Steps to reproduce:

  1. Setup OBS to output video with 1920x1080 resolution and start OBS Virtual Cam or use any device capable to output Full HD
  2. Open https://jsfiddle.net/ArmorDarks/e2rzuygL/81/ which uses getUserMedia to request video with 1080p as a height constrain
  3. Select OBS Virtual Cam or your Full HD capable device
  4. Check the log above video - the video track will be of HD resolution even if Full HD was specified in constraints.
  5. Check the strict checkbox. That will add exact value to the height of constraint to try force Full HD.
  6. That will result in OverconstrainedError complaining about height though OBS virtual cam capable of outputting Full HD.

Actual results:

Video track settings are always of HD resolution at best, and if strict 1920x1080 is specified, it always results in OverconstrainedError even though the device clearly supports Full HD.

Expected results:

Video track should be in Full HD if the device supports that resolution.

That issue is present in Firefox, but not in Chrome

Has STR: --- → yes
Component: Untriaged → WebRTC: Audio/Video
Keywords: parity-chrome
Product: Firefox → Core

Any ideas here?

Flags: needinfo?(jib)

Thanks for the report Sergii. Are you experiencing this symptom on Mac or Windows? Or both?

What error message do you see if you run https://jsfiddle.net/jib1/9u0r6Lab/show ?

With my Logitech BRIO,

  1. when I run this fiddle on Windows, it works fine (I get 1920 x 1080).
  2. when I run this fiddle on macOS, I get AbortError: Starting videoinput failed, even though it works in Chrome.
Flags: needinfo?(jib) → needinfo?(github)

(In reply to Jan-Ivar Bruaroey [:jib] (needinfo? me) from comment #2)

  1. when I run this fiddle on macOS, I get AbortError: Starting videoinput failed, even though it works in Chrome.

Update on mac: I couldn't find a regression range for that error, and after I restarted my Nightly (it updated) I could no longer reproduce it. Now I get OverconstrainedError: Constraints could be not satisfied. instead, and ahead of the prompt.

Works fine on Windows and properly produces Full HD, but doesn't on Mac (both Catalina and Big Sur)

The error message was specified in my original post: OverconstrainedError: Constraints could be not satisfied. (constraint: height)

Flags: needinfo?(github)
OS: Unspecified → macOS
Hardware: Unspecified → Desktop

Changing severity to match bug 1451394.

Severity: -- → S3
Priority: -- → P2
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.