New issue
Advanced search Search tips

Issue 734985 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

AppRTC h264 call, video is in unclear (blotchy) on Mac (stable) from Win 10 machine

Project Member Reported by jkallar@chromium.org, Jun 20 2017

Issue description

Chrome:  61.0.3128.0/dev  (Win 10); 58.0.3029.110/stable (MacOS 10.11.5)

What steps will reproduce the problem?
1. Browse to https://appr.tc/?vsc=h264 on Win 10 machine, choose and room name and ‘Join'
2. Browse to https://appr.tc/?vsc=h264 on MacOS machine, enter same room name from step 1 and ‘Join’
3. Open the javascript console (alt+cmd+j or ctr+shift+j) on both platforms and watch for any errors
4. Disconnect the call from Win 10 machine

What is the expected result?
- Good audio at both ends
- Good clear video at both ends
- Call is successfully disconnected-
- No JS errors

What happens instead?
step 2:  On Mac machine, the video sent from the Win 10 machine is unclear / blotchy (see attached screenshot)

Please provide any additional information below. Attach a screenshot if
possible.


I see the SAME bug on win 10 (61.0.3128.0/dev) when doing a h264 loopback call ie. https://appr.tc/?debug=loopback&vsc=h264

I do NOT see the bug if I do Win 10 (stable, 58.0.3029.110 ) to Mac (stable, 58.0.3029.110)  AppRTC call

I do NOT see the bug if you replace h264 with vp8/9 in the above steps

Devices used to produce the bug:
Win 10:  Logitech c930e or Microsoft LifeCam HD-3000
MacOS: inbuilt FaceTime camera
 
screenshot-h264.png
924 KB View Download
Labels: Needs-Feedback
Owner: emir...@chromium.org
Status: Assigned (was: Unconfirmed)
Can you share chrome://webrtc-internals/ dump when this happens?
jkallar@ assignment has come to an end. I might be able to repro this week unless you have the possibility.
That would be really helpful as I dont have a Win 10 at the moment. Also, the problem seems to be related to interop between 58 and 61. I haven't touched HW encoder specific code between those, so I expect webrtc-internals to show where else problem might be. 
Cc: jansson@chromium.org
I cannot reproduce the issues mentioned using Chrome 60(stable) and 62(canary). jansson@, can you check if it still reproduces for you?
Status: Archived (was: Assigned)
Archiving as there is no activity for a while. Feel free to open if it can still reproduce.

Sign in to add a comment