New issue
Advanced search Search tips

Issue 668712 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC screen share Resolution Quality is very low. (Only H.264)

Reported by dodor...@gmail.com, Nov 25 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. Webrtc screen share Resolution Quality is very low. 
2. Only H.264, it is intermittent and frequent symptoms.
3. But, VP8 codec is OK.

What is the expected behavior?

What went wrong?
Webrtc screen share Resolution Quality is very low. 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 54.0.2840.99  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: Shockwave Flash 23.0 r0
 
Labels: -Hotlist-Interop

Comment 2 by dodor...@gmail.com, Nov 28 2016

in 54 stable version 
uploaded webrtc-internal image
 
Is this a bug?
When will it be fixed?

screen share.PNG
91.1 KB View Download

Comment 3 by dodor...@gmail.com, Nov 28 2016

I'm tested screen share on h.264 

52.0.2743.116 - Good Resolution 
53.0.2785.116 - Low Resolution
54.0.2840.99 stable - Low Resolution
55.0.2883.59 beta - Low Resolution
56.0.2924.3 dev - Low Resolution
57.0.2931.0 canary - Good Resolution 

Will the 57 stable version be modified and released?

Comment 4 by dodor...@gmail.com, Nov 28 2016

Mac, Windows is same.

Comment 5 by guidou@chromium.org, Nov 28 2016

Components: -Blink>WebRTC Blink>WebRTC>Video
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.

Thank you!
Labels: M-57

Comment 8 by tommi@chromium.org, Mar 9 2017

Owner: sprang@chromium.org
Status: Assigned (was: Unconfirmed)
Erik - I'm tentatively assigning this to you.
M57 is going out to stable now, so quite possibly this is already fixed as per comments above.

Comment 9 by sprang@chromium.org, Mar 10 2017

Looks like cpu adaptation or quality scaling kicked in. How was the stream configured?
I don't remember any bug around that, could just be that m57 has better h264 performance?

Sign in to add a comment