New issue
Advanced search Search tips

Issue 704277 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Tab capture always starts on max resolution and then scales down

Project Member Reported by niklase@chromium.org, Mar 22 2017

Issue description

Chrome Version: 57
OS: all

Forked off from https://bugs.chromium.org/p/chromium/issues/detail?id=700955.

When starting a tab capture session using chooseDesktopMedia and getUserMedia you always get the max resolution (from constraints) for the first 2 seconds, and then it scales down to the native tab resolution. This isn't strictly violating the spec, but it's undesirable since you often end up with an oversampled imaged with padding added and have to deal with resolution changes. 

 

Comment 1 by m...@chromium.org, Mar 22 2017

Labels: -Type-Bug -Pri-2 M-58 Pri-1 Type-Bug-Regression
It's a regression. While not strictly violating the spec or any interface contracts, this issue does affect the end-user experience in a really bad way. I'm not sure whether to consider this release-blocking, however.
miu@ are you working on this at the moment?

Comment 3 by m...@chromium.org, May 4 2017

Cc: m...@chromium.org
Owner: ----
Status: Available (was: Assigned)
anatolid: No. Feel free to take this if you want.

I vaguely recall this issue getting fixed, though. We should re-check. Pretty simple, just turn on verbose logging (--vmodule=video_capture_oracle=2), and look for this log line: https://cs.chromium.org/chromium/src/media/capture/content/video_capture_oracle.cc?rcl=d01fb51d1a9ba850c92f525dc31187ef79a2586c&l=398

Comment 4 by m...@chromium.org, May 5 2017

Owner: m...@chromium.org
Status: Started (was: Available)
Back at my desk, just tried this on a recent trunk build: Still an issue. Actually, I'll whip-up a quick change to address this. I think we can just make sure the size is set before, instead of just after, the first frame is captured from a new RenderWidgetHostView target.
Project Member

Comment 5 by bugdroid1@chromium.org, May 6 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/bebdfb5fde6a56eb40c7f2efc7bc0cbbcecdc41e

commit bebdfb5fde6a56eb40c7f2efc7bc0cbbcecdc41e
Author: miu <miu@chromium.org>
Date: Sat May 06 18:53:15 2017

Tab Capture: Set size before changing target RWHV

Fixes a performance issue where tab capture always starts out at the
maximum configured resolution, regardless of the source size. This
change ensures the source size updates the capture size before the first
frame is ever captured.

BUG= 704277 

Review-Url: https://codereview.chromium.org/2859223005
Cr-Commit-Position: refs/heads/master@{#469851}

[modify] https://crrev.com/bebdfb5fde6a56eb40c7f2efc7bc0cbbcecdc41e/content/browser/media/capture/web_contents_tracker.cc

Labels: -M-58 M-60

Comment 7 by m...@chromium.org, May 9 2017

Status: Fixed (was: Started)

Sign in to add a comment