New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 644771 link

Starred by 3 users
Status: Fixed
Owner:
█ magjed@chromium.org
Last visit 16 days ago
Closed: Apr 2017
Cc:
mflodman@chromium.org
sprang@chromium.org
brandtr@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome webrtc can not render remote video

Reported by wangh...@gmail.com, Sep 7 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. I send a webrtc offer to the chrome ,content like this:

v=0
o=- 145385010286214769 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS SIzsxQNV502lgDz1tS2xf8Goysqwl5wscAcd
m=audio 9 UDP/TLS/RTP/SAVPF 0
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:2rBhNLXtPfZ5ajCl
a=ice-pwd:Dr/29rvxK6ZV586nvfcG7Pm1
a=fingerprint:sha-256 E2:9A:56:87:07:D7:8D:2E:B8:98:20:95:43:D7:90:E3:55:D6:C1:96:08:02:51:3D:11:ED:BA:D1:3E:1B:18:F8
a=setup:actpass
a=mid:audio
a=sendrecv
a=rtcp-mux
a=rtpmap:9 G722/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=maxptime:60
a=ssrc:123456789 cname:HpozKTlhjeeUBxTM
a=ssrc:123456789 msid:SIzsxQNV502lgDz1tS2xf8Goysqwl5wscAcd c3277607-a619-4ee6-8fe6-a8cacc55779a
a=ssrc:123456789 mslabel:SIzsxQNV502lgDz1tS2xf8Goysqwl5wscAcd
a=ssrc:123456789 label:c3277607-a619-4ee6-8fe6-a8cacc55779a
m=video 9 UDP/TLS/RTP/SAVPF 107
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:2rBhNLXtPfZ5ajCl
a=ice-pwd:Dr/29rvxK6ZV586nvfcG7Pm1
a=fingerprint:sha-256 E2:9A:56:87:07:D7:8D:2E:B8:98:20:95:43:D7:90:E3:55:D6:C1:96:08:02:51:3D:11:ED:BA:D1:3E:1B:18:F8
a=setup:actpass
a=mid:video
a=sendrecv
a=rtcp-mux
a=rtpmap:107 H264/90000
a=rtcp-fb:107 ccm fir
a=rtcp-fb:107 nack
a=rtcp-fb:107 nack pli
a=fmtp:107 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=rtcp-fb:107 goog-remb
a=ssrc:987654321 cname:HpozKTlhjeeUBxTM
a=ssrc:987654321 msid:SIzsxQNV502lgDz1tS2xf8Goysqwl5wscAcd b78cce51-d110-474e-b5db-e30da41a3933
a=ssrc:987654321 mslabel:SIzsxQNV502lgDz1tS2xf8Goysqwl5wscAcd
a=ssrc:987654321 label:b78cce51-d110-474e-b5db-e30da41a3933

the chrome give me the webrtc sdp answer is 
v=0
o=- 7790464261402929753 2 IN IP4 127.0.0.1
s=-
t=0 0
a=group:BUNDLE audio video
a=msid-semantic: WMS aCEspxiKh9EGJUGcotpk008SjgAk6vR1HQzu
m=audio 9 UDP/TLS/RTP/SAVPF 0
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:6p+ZLw5coNAC3dF0
a=ice-pwd:NJkQcDQqlwSE/1n0mTPJ/r8p
a=fingerprint:sha-256 C9:E1:CC:67:61:1C:1F:47:45:F5:62:F6:24:CE:9C:93:D2:FA:A5:F2:25:DD:7C:B9:89:E7:B9:BA:C3:FD:84:A4
a=setup:active
a=mid:audio
a=sendrecv
a=rtcp-mux
a=rtpmap:0 PCMU/8000
a=ssrc:1674803677 cname:OJCwParWEytqLioU
a=ssrc:1674803677 msid:aCEspxiKh9EGJUGcotpk008SjgAk6vR1HQzu 70f74106-8df8-4ebf-80cb-651533466aa5
a=ssrc:1674803677 mslabel:aCEspxiKh9EGJUGcotpk008SjgAk6vR1HQzu
a=ssrc:1674803677 label:70f74106-8df8-4ebf-80cb-651533466aa5
m=video 9 UDP/TLS/RTP/SAVPF 107
c=IN IP4 0.0.0.0
a=rtcp:9 IN IP4 0.0.0.0
a=ice-ufrag:6p+ZLw5coNAC3dF0
a=ice-pwd:NJkQcDQqlwSE/1n0mTPJ/r8p
a=fingerprint:sha-256 C9:E1:CC:67:61:1C:1F:47:45:F5:62:F6:24:CE:9C:93:D2:FA:A5:F2:25:DD:7C:B9:89:E7:B9:BA:C3:FD:84:A4
a=setup:active
a=mid:video
a=sendrecv
a=rtcp-mux
a=rtpmap:107 H264/90000
a=rtcp-fb:107 ccm fir
a=rtcp-fb:107 nack
a=rtcp-fb:107 nack pli
a=rtcp-fb:107 goog-remb
a=fmtp:107 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=ssrc:1860291632 cname:OJCwParWEytqLioU
a=ssrc:1860291632 msid:aCEspxiKh9EGJUGcotpk008SjgAk6vR1HQzu 55f40b14-824b-48d0-aac9-aaf1c1f927fd
a=ssrc:1860291632 mslabel:aCEspxiKh9EGJUGcotpk008SjgAk6vR1HQzu
a=ssrc:1860291632 label:55f40b14-824b-48d0-aac9-aaf1c1f927fd

I send 264 video to the chrome use nalu & fu-a pakcage to build 264 RTP pakcage

What is the expected behavior?
chrome can render remote video

What went wrong?
And I send 264 video to the chrome , the chrome cannot render the image. I find out that chrome can receive the rtp ,but cannot decode the rtp package

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

Comment 1 by ajha@chromium.org, Sep 9 2016

Components: -Internals>Media Blink>WebRTC>Video
Owner: hta@chromium.org
Status: Assigned (was: Unconfirmed)
hta@: Could you please confirm if this is related to  Issue 600254 .

Comment 2 by hta@chromium.org, Sep 9 2016 

No, this is not related to  issue 600254  (packetization-mode 0 support).
As you can see, both sides have "packetization-mode=1" in their SDP.

Error reporter: Please identify what the hardware and software of each system is. We have had problems with H.264 output coming from specific hardware decoders (at least one is fixed, but not AFAIK backported to M52).

Comment 3 by wangh...@gmail.com, Sep 9 2016 

hta@:

the same edition of chrome with different pc have different appearance.
Can I close hardware decoders?

Comment 4 by hta@chromium.org, Sep 12 2016 

wanghb89: is the Chrome running on Windows, Mac, Linux or ChromeOS? Which OS version?

Your Chrome tag says "Windows NT 10.0; WOW64" - is this correct?
What is the system that is sending H.264? ("use nalu & fu-a pakcage to build 264 RTP pakcage" doesn't tell me very much).
What systems can successfully receive H.264 produced by the same H.264 encoder?

Comment 5 by wangh...@gmail.com, Sep 13 2016 

My system is win10.
my server is also in win10.
my server read 264 file, than pakcage it into 264 RTP mode(pcakketization-mode=1,only send 264 nalu and fu-a )

Btw, I send RTP with timestamp (capture time in ms * 90 + random offset https://bugs.chromium.org/p/webrtc/issues/detail?id=3111) the chrome can decode the 264, But have lots of problem.
1  picture render stuck
2 blurred the images

my test on new M54 edition have also this problem！

if u like, U can read my  packetizerH264 code written by golang
pakcage.go
1.4 KB View Download

Comment 6 by hta@chromium.org, Sep 14 2016 

Are there any other H.264 decoders that can read, decode and display your H.264 RTP stream?

The packetizer you provided seems incomplete compared to the length of the packetization spec; I would like to be assured that the packet stream is valid before using more time on this.

Comment 7 by wangh...@gmail.com, Sep 14 2016 

firefox and some edition of chrome(M53) on win7  can decode the  H.264 RTP stream(the same H.264 file)

Comment 8 by hta@chromium.org, Sep 14 2016 

If this is working in m53 and not working in m52, I think we can close this as "fixed".

Comment 9 by wangh...@gmail.com, Sep 15 2016 

 hta@:
M54 is also have this problem?

May I ask why firefox can work well? what"s difference between firefox and chrome?What do I need to pay attention？

Comment 10 by wangh...@gmail.com, Sep 21 2016 

Can Anyone help me out?

Comment 11 by hta@webrtc.org, Sep 21 2016 

You might want to try to run Chrome with logging turned on, to see if there's an error message in the logs. There should be instructions for turning on logging on www.webrtc.org.

https://webrtc.org/web-apis/chrome/

Comment 12 by wangh...@gmail.com, Sep 21 2016 

hta@

I got 11992:9724:0921/223145:ERROR:h264_decoder_impl.cc(333)]
avcodec_decode_video2 error: -1094995529
Can you give me more information?  I have not find 333 line in my
downloaded webrtc!

2016-09-21 21:44 GMT+08:00 h… via monorail <
monorail+v2.3115252668@chromium.org>:

Comment 13 by wangh...@gmail.com, Oct 14 2016 

Hi ALL
I find the solution :
1  sps, pps and IDR must have the same timestamp
2 set the last RTP pakcage of IDR mark true

2016-09-21 22:34 GMT+08:00 Wanghb Wang <wanghb89@gmail.com>:

Comment 14 by hta@chromium.org, Apr 5 2017

Owner: magjed@chromium.org
Assigning to magjed to evaluate whether this can be closed now.

Comment 15 by magjed@chromium.org, Apr 5 2017

Status: Fixed (was: Assigned)
Sounds like this is fixed in comment #13. wanghb89@ - please verify.
►

Sign in to add a comment