Black screen instead of video if certain H264 profiles are set as top priority
Reported by
djpe...@gmail.com,
Mar 3 2018
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36 Steps to reproduce the problem: 1. Go to "Mungle SDP WebRTC example": https://webrtc.github.io/samples/src/content/peerconnection/munge-sdp/ 2. Click "Get Media" 3. Click "Create Peer Connection" 4. Click "Create Offer" 5. Mungle the offer this way: Change codecs priority in m=video line: Before: 96 97 98 99 100 101 102 123 127 122 125 107 108 109 124 Change to: 125 100 127 102 96 98 124 108 97 101 122 99 107 109 123 (Same numbers but what is important 125 is the first) 125 stands for H264, profile=640032: a=rtpmap:125 H264/90000 a=fmtp:125 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=640032 6. Click "Create Answer" 7. Click "Set Answer" What is the expected behavior? Peer Connection connected Video Displayed in "Local" and "Remote" windows. What went wrong? Peer Connection connected, but Remote video is black. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.186 Channel: stable OS Version: OS X 10.11.6 Flash Version: 2 codecs behave this way: H264, profile=640032 H264, profile=4d0032 So, combinations like: 100 102 127 125 96 98 124 108 97 101 122 99 107 109 123 (H264 42001f) 102 100 127 125 96 98 124 108 97 101 122 99 107 109 123 (H264 42e01f) works fine. While, combinations like: 127 100 102 125 96 98 124 108 97 101 122 99 107 109 123 (H264 4d0032) 125 100 127 102 96 98 124 108 97 101 122 99 107 109 123 (H264 640032) produce the bug.
,
Mar 6 2018
Unable to reproduce the issue on chrome reported version 64.0.3282.186 using 10.12.6 with steps mentioned below: 1) Launched chrome reported version and navigated to URL: https://webrtc.github.io/samples/src/content/peerconnection/munge-sdp/ 2) Clicked on "Get Media", "Create Peer Connection" and "Create Offer" 3) Pasted which is mentioned below in "Answer SDP" Change codecs priority in m=video line: Before: 96 97 98 99 100 101 102 123 127 122 125 107 108 109 124 Change to: 125 100 127 102 96 98 124 108 97 101 122 99 107 109 123 (Same numbers but what is important 125 is the first) 125 stands for H264, profile=640032: a=rtpmap:125 H264/90000 a=fmtp:125 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=640032 4) Click "Create Answer" and "Set Answer" 5) Able to see video on both "Local" and "Remote" windows. @Reporter: Please find the attached screen cast for your reference and let us know if we missed anything in reproducing the issue. Try to test this issue by creating new person with no apps and extensions in it and let us know if the issue still persists. Thanks!
,
Mar 7 2018
Yes you missed something: 4. Click "Create Offer" 5. Mungle THE OFFER this way: You instead pasted text into Answer which later was replaced with the default answer. So, you basically changed nothing comparing to default behavior. Please see screen cast attached for the reference and read p.5 carefully.
,
Mar 7 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 7 2018
Also between p.5 and p.6 in the original description should be 5.5 Click "Set offer" My bad.
,
Mar 8 2018
,
Mar 15 2018
magjed@ can you triage?
,
Mar 19 2018
Looks like something is wrong with HW H264 High profile on Mac. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sindhu.chelamcherla@chromium.org
, Mar 4 2018