Issue metadata
Sign in to add a comment
|
Regression: Remote video blockiness(intermittent) during apprtc calls with H264 |
||||||||||||||||||||||
Issue descriptionChrome Version: 54.0.2840.26/ 8743.30.0 beta Device : Squawks Steps to reproduce: 1. Start a loopback apprtc call using https://appr.tc/?debug=loopback&vsc=h264 2. Observe local and remote audio/video quality Expected result: Local and remote video should be clear throughout the apprtc loopback call Actual result: Remote video is blocky intermittently for the first 1-2 minutes of the apprtc loopback call Feedback submitted for this issue: https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:srcv&lReport=13553056669 Notes: 1. This issue is also observed during apprtc peer2peer calls with H264 2. This issue is not seen in M53 stable (53.0.2785.103 / 8530.81.0) 3. This issue is so far observed on devicesGnawty, Swanky, Winky Reks, Guado 4. This issue was observed with both wifi and wired network
,
Sep 21 2016
Is this device using HW encode?
,
Sep 21 2016
Yes. Squawks (Bay Trail Rambi family) uses hardware encoding.
,
Sep 22 2016
HW encoding, in that case, emircan are you the right person to own this?
,
Sep 22 2016
Adding wuchengli@ and posciak@ to take a look. Do you know if anything changed for M54 for this device family? I found a similar issue below from earlier: https://groups.google.com/a/google.com/forum/#!msg/chromeos-video-bugs/Df3coQDMVIw/7JAiISxpBgAJ
,
Sep 23 2016
I think this is https://code.google.com/p/chrome-os-partner/issues/detail?id=45996. The issue exists for a long time. It's a limitation of Intel driver for H264. Is this really a regression? Can you check again if M53 has this issue?
,
Sep 27 2016
Re-tested apprtc calls with H264 on chrome device Squawks with M53 53.0.2785.144 / 8530.93.0 stable Out of 4 test apprtc calls, remote video blockiness was observed only in the first apprtc call for one second and video was clear for the rest of the call.
,
Sep 28 2016
,
Sep 30 2016
OK. It's not a regression. This should be 45996. Also, WebRTC didn't use H264 HW encode in the past. Please look at the videos in 45996. If you think the blcokiness of this is different from 45996, please reopen this one. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kjellander@chromium.org
, Sep 21 2016Owner: hbos@chromium.org
Status: Assigned (was: Untriaged)