On Firefox 53 we able to see the remote video

chrome://webrtc-internals receiving video statistics are attached

Deleted: ChromeStoppedDecodingH.264Video.jpg 201 KB

	ChromeStoppedDecodingH.264Video.jpg 201 KB View Download

michaelz, how do you reproduce this? What application? Is it reproducible with appr.tc?

Philip, can you take a look? 

Please use the following link for connection
To reproduce this problem you can use: 
http://test1000.orionmcu.com?url=3_bf0d279a6474c1b9e2b5947bbb0976be
enter any name for example "Alex", join to the conference - you can see there is no remote video opened.
Use the same link on chrome 57 it works.

I can reproduce this issue using Chromium M58 on Mac.

The SW H264 decoder reports error "[15154:46851:0505/102404.083737:ERROR:h264_decoder_impl.cc(330)] avcodec_decode_video2 error: -1094995529"

The HW H264 decoder reports error "[15371:24875:0505/103301.354734:VERBOSE1:h264_parser.cc(432)] Error in stream: unexpected EOS while trying to read &bit
[15371:24875:0505/103301.354943:VERBOSE1:h264_parser.cc(878)] Error in stream: invalid value while trying to read &data
[15371:24875:0505/103301.355136:ERROR:vt_video_decode_accelerator_mac.cc(511)] Could not parse SPS
[15371:775:0505/103301.355437:VERBOSE1:gpu_channel.cc(692)] sending message @0x7fc91d049130 on channel @0x7fc91b55ba40 with type 852109
[15371:24875:0505/103301.355456:VERBOSE1:h264_parser.cc(260)] Requested a nonexistent PPS id 0
[15371:24875:0505/103301.355692:VERBOSE1:h264_parser.cc(1310)] Error in stream: invalid value, expected pps
[15375:37379:0505/103301.355835:ERROR:rtc_video_decoder.cc(526)] VDA Error:3
[15371:24875:0505/103301.355883:ERROR:vt_video_decode_accelerator_mac.cc(555)] Could not parse slice header"

maojie0...@gmail.com,
Thank you for your analysis - so the problem is reproducible on Mac as well

 Issue 719095  has been merged into this issue.

I'm not sure if  Issue 719095  is related to this issue. But I did some revert test, if I revert this patch https://codereview.webrtc.org/2704183002, my Chromium 58 could decode the H264 bitstream normally.

 Issue 719095  is related to SEI packets handling and we feel it is different than 717884 as we don't observe above video decode errors for the H264 stream. In our case we see two kind of issues :

1) Blank video : We see blank video on Chrome when SEI packets are there with every IDR frame from the beginning. 

2) Video freeze : When H264 stream which doesn't have SEI NAL packet in first IDR frame, we do see video on Chrome and thereafter freeze issues whenever SEI packets arrive with IDR frame. So video does decode for our H264 stream, it is just the handling of SEI packets in the H264 stream which causes IDR frames to get discarded. 

We have been updating https://groups.google.com/forum/#!msg/discuss-webrtc/dt_A8pv_nBU/KEW1-kpCBQAJ forum post for this issue. Comment from Philip in this thread talk about handling of SEI packets as Delta Frame and review request https://codereview.chromium.org/2769863007/. We have tried a fix to treat SEI packets as separate frame and not as Delta frame, and it seems to be working. Diff with fix has been attached to 719095 issue.

krajshree@chromium.org,
Request you to mark 719095 as not a duplicate of 717884 and keeping it as separate issue. Thanks.

I've got very similar issue but with VP8 - Chrome 57 can successfully decode video but Chrome 58 cannot.

I get these errors:

[63196:54791:0509/222620.245962:WARNING:vp8_header_parser.cc(178)] Failed to get QP, invalid length: 1164
[63196:54791:0509/222620.246377:WARNING:generic_decoder.cc(174)] Failed to decode frame with timestamp 3332525173, error code: -1

maybe similar to: 
https://bugs.chromium.org/p/webrtc/issues/detail?id=7583

We are looking into the SEI NAL issues and we think there are some improvements we can make here shortly.

Hi,
We have been using Chrome 57.0.2987.133 so far and were able to get the H264 video from our client.
When we did upgrade to Chrome 58.0.3029.110, we do not get the video on the browser. However when we captured the wireshark, we see that video packets are coming all the wayto the browser. 

When we use a different client, we seem to get the H264 video on the 58.0.3029.110 chrome version. 

Can you please help us understand what could be wrong when using our client?
Attached the Wireshark log for your reference(Not working case log and working case log) 

Please use the filter "rtp.p_type == 103 && ip.dst==172.168.0.13" to see H264 packets to the browser machine.

Deleted: wireshark_Linphone_Client_to_WebRTC_Working_2.pcapng 4.5 MB

wireshark_Linphone_Client_to_WebRTC_Working_2.pcapng 4.5 MB Download

Deleted: wireshark_Client_to_WebRTC_Notworking_1.pcapng 5.0 MB

wireshark_Client_to_WebRTC_Notworking_1.pcapng 5.0 MB Download

hitz.infitech, is this working for you with current Chrome Canary?

We were not seeing issues reported in this issue ( Issue 717884 ). We have verified fix made for  Issue 719095  (Blank video due to SEI NAL packets) and as per our testing with latest Chrome Canary fix is found to be working.

Latest chrome Version 59.0.3071.86 (Official Build) (64-bit) fixed the issue