Issue metadata
Sign in to add a comment
|
Chrome Ver 57 on Windows 7 with OpenH264 1.6 sends out very low bitrate blocky bad video when packetization-mode is 0 in SDP offer
Reported by
joanne.x...@gmail.com,
Mar 28 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: 1. Send a SDP offer to the chrome, content like this: s=ba2768de-abd7-3e24-825c-b7583a91a461 e=unknown@invalid.net c=IN IP4 135.60.86.242 t=0 0 a=msid-semantic: WMS ba2768de-abd7-3e24-825c-b7583a91a461 m=audio 6220 UDP/TLS/RTP/SAVPF 96 0 13 101 c=IN IP4 135.60.86.242 a=ice-ufrag:qMXTjCV/ a=ice-pwd:o3PBVAC28HZ3feTBAGielgFj a=candidate:32 1 udp 2130706431 135.60.86.242 6220 typ host a=end-of-candidates a=fingerprint:sha-256 3D:68:8C:E1:33:14:59:14:5E:CA:D3:AE:7A:3B:CE:7A:35:F1:AD:8D:07:03:64:F1:A5:AD:FB:97:5D:BC:79:51 a=setup:actpass a=rtpmap:96 opus/48000/2 a=fmtp:96 maxplaybackrate=16000; sprop-maxcapturerate=16000; maxaveragebitrate=20000; stereo=0; useinbandfec=0; usedtx=0; cbr=0; sprop-stereo=0 a=rtpmap:0 PCMU/8000 a=rtpmap:13 CN/8000 a=rtpmap:101 telephone-event/8000 a=maxptime:20 a=ptime:20 a=minptime:20 a=rtcp-mux a=ssrc:1601188190 cname:4dbfd71e-9092-11e6-bb4c-9c8e992c5cb0 a=ssrc:1601188190 msid:ba2768de-abd7-3e24-825c-b7583a91a461 audio-0 a=sendrecv m=video 6222 UDP/TLS/RTP/SAVPF 97 c=IN IP4 135.60.86.242 b=AS:1280 a=ice-ufrag:qMXTjCV/ a=ice-pwd:o3PBVAC28HZ3feTBAGielgFj a=candidate:32 1 udp 2130706431 135.60.86.242 6222 typ host a=end-of-candidates a=fingerprint:sha-256 3D:68:8C:E1:33:14:59:14:5E:CA:D3:AE:7A:3B:CE:7A:35:F1:AD:8D:07:03:64:F1:A5:AD:FB:97:5D:BC:79:51 a=setup:actpass a=content:default,1,100,1 a=rtpmap:97 H264/90000 a=fmtp:97 profile-level-id=42e01f;in-band-parameter-sets=1;max-rcmd-nalu-size=1292 a=rtcp-fb:97 nack pli a=rtcp-fb:97 ccm fir a=rtcp-fb:97 ccm tmmbr a=rtcp-mux a=recvonly 2. Chrome answers like this: v=0 o=- 4915911165941465533 2 IN IP4 127.0.0.1 s=- t=0 0 a=msid-semantic: WMS QYZ8KpylrX8h5Ns6FO5LSaCaUtzHpvW6wuZb m=audio 59867 UDP/TLS/RTP/SAVPF 96 0 13 101 c=IN IP4 192.168.0.3 a=rtcp:9 IN IP4 0.0.0.0 a=candidate:3793934955 1 udp 2122262783 2600:8800:1700:4380:ed5a:11e0:f106:4b12 59865 typ host generation 0 network-id 4 a=candidate:2224440194 1 udp 2122197247 2600:8800:1700:4380:e5ba:d6f6:23ad:3651 59866 typ host generation 0 network-id 3 a=candidate:3802297132 1 udp 2122129151 192.168.0.3 59867 typ host generation 0 network-id 2 a=candidate:2418917555 1 udp 2122063615 135.105.97.8 59868 typ host generation 0 network-id 1 a=candidate:2896242331 1 tcp 1518283007 2600:8800:1700:4380:ed5a:11e0:f106:4b12 9 typ host tcptype active generation 0 network-id 4 a=candidate:3390422898 1 tcp 1518217471 2600:8800:1700:4380:e5ba:d6f6:23ad:3651 9 typ host tcptype active generation 0 network-id 3 a=candidate:2887880668 1 tcp 1518149375 192.168.0.3 9 typ host tcptype active generation 0 network-id 2 a=candidate:3735960643 1 tcp 1518083839 135.105.97.8 9 typ host tcptype active generation 0 network-id 1 a=ice-ufrag:zPD9 a=ice-pwd:vmK1hcvm/j1t+YRyO7vgJTKn a=fingerprint:sha-256 A5:64:2E:83:0B:BB:64:8F:2D:15:02:F0:55:D0:07:49:15:F5:67:4F:A7:22:6A:C1:C7:C2:B5:D5:4A:CB:81:51 a=setup:active a=mid:audio a=sendrecv a=rtcp-mux a=rtpmap:96 opus/48000/2 a=fmtp:96 minptime=10;useinbandfec=1 a=rtpmap:0 PCMU/8000 a=rtpmap:13 CN/8000 a=rtpmap:101 telephone-event/8000 a=ssrc:3407184116 cname:ldnMNc6zgrY3zGI8 a=ssrc:3407184116 msid:QYZ8KpylrX8h5Ns6FO5LSaCaUtzHpvW6wuZb 601aa6c5-e0e5-47c1-91d3-c3d7eae1ca95 a=ssrc:3407184116 mslabel:QYZ8KpylrX8h5Ns6FO5LSaCaUtzHpvW6wuZb a=ssrc:3407184116 label:601aa6c5-e0e5-47c1-91d3-c3d7eae1ca95 m=video 59871 UDP/TLS/RTP/SAVPF 97 c=IN IP4 192.168.0.3 a=rtcp:9 IN IP4 0.0.0.0 a=candidate:3793934955 1 udp 2122262783 2600:8800:1700:4380:ed5a:11e0:f106:4b12 59869 typ host generation 0 network-id 4 a=candidate:2224440194 1 udp 2122197247 2600:8800:1700:4380:e5ba:d6f6:23ad:3651 59870 typ host generation 0 network-id 3 a=candidate:3802297132 1 udp 2122129151 192.168.0.3 59871 typ host generation 0 network-id 2 a=candidate:2418917555 1 udp 2122063615 135.105.97.8 59872 typ host generation 0 network-id 1 a=candidate:2896242331 1 tcp 1518283007 2600:8800:1700:4380:ed5a:11e0:f106:4b12 9 typ host tcptype active generation 0 network-id 4 a=candidate:3390422898 1 tcp 1518217471 2600:8800:1700:4380:e5ba:d6f6:23ad:3651 9 typ host tcptype active generation 0 network-id 3 a=candidate:2887880668 1 tcp 1518149375 192.168.0.3 9 typ host tcptype active generation 0 network-id 2 a=candidate:3735960643 1 tcp 1518083839 135.105.97.8 9 typ host tcptype active generation 0 network-id 1 a=ice-ufrag:oHRV a=ice-pwd:1vkJdTAWHsIcqli4QHpdaavz a=fingerprint:sha-256 A5:64:2E:83:0B:BB:64:8F:2D:15:02:F0:55:D0:07:49:15:F5:67:4F:A7:22:6A:C1:C7:C2:B5:D5:4A:CB:81:51 a=setup:active a=mid:video a=sendonly a=rtcp-mux a=rtpmap:97 H264/90000 a=rtcp-fb:97 ccm fir a=rtcp-fb:97 nack pli a=fmtp:97 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f a=ssrc:2600202029 cname:ldnMNc6zgrY3zGI8 a=ssrc:2600202029 msid:QYZ8KpylrX8h5Ns6FO5LSaCaUtzHpvW6wuZb 647f61aa-dcbe-4245-ab86-4a1f150e4558 a=ssrc:2600202029 mslabel:QYZ8KpylrX8h5Ns6FO5LSaCaUtzHpvW6wuZb a=ssrc:2600202029 label:647f61aa-dcbe-4245-ab86-4a1f150e4558 3. Check in chrome://webrtc-internal and see if chrome sends very low bitrate video What is the expected behavior? Chrome should send out video with good quality@1Mbps. What went wrong? 1. When is offered with packetization-mode 0, chrome should response with packetization-mode 0 instead of 1 according to RFC6184. 2. With Chrome Ver 57.0.2987.110 on Windows 7 with OpenH264 1.6 sends out very low bitrate (<50Kbps) blocky bad video when packetization-mode is 0 in SDP offer, please see screen shoots of send chart, BWE chart and chrome debug log in attached chrome_ver57_win7.zip. The same sdp to Chrome Version 56.0.2924.87 on Windows 7 or Chrome version 57.0.2987.110 on Windows 10 work fine, related charts and logs can be found in attached attached chrome_ver56_win7.zip and attached chrome_ver57_win10.zip respectively. Did this work before? Yes 56.0.2924.87 Chrome version: 57.0.2987.110 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: This issue may be related to Issue 600254 . I tested the same with Chrome Canary ver 59, the problem still exists in the Chrome Canary ver 59.
,
Mar 30 2017
This looks like out of scope for TE, hence adding the respective label for it to triage further.
,
Jul 31 2017
There is no valid updates happened in the last few months, closing the issue. Feel free to reopen if needed. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Mar 29 2017