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

Issue 722516 link

Starred by 8 users

Issue metadata

Status: Duplicate
Merged: issue 719095
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug


Previous locations:
webrtc:7639


Sign in to add a comment

Unable to playback H264 in Chrome on macOS

Reported by stijnvan...@gmail.com, May 12 2017

Issue description

What steps will reproduce the problem?
Playback a WebRTC video using the h264 video codec

What is the expected result?
Show video

What do you see instead?
Nothing

What version of the product are you using? On what operating system?
Chrome 58.0.3029.110 on MacOS (10.12.4) (Windows works fine)

Please provide any additional information below.
Also Chrome 57 worked fine


 
Project: chromium
Moved issue webrtc:7639 to now be  issue chromium:722516 .
Components: Blink>WebRTC>Video
Please provide more details about what you mean with a "WebRTC video". Do you have reproduction steps and/or a sample web page?
Labels: OS-Mac
We use webrtc video for 1 on 1 video chats with wowza to communicate between Chrome and Flash video.

Since the chrome 58 update on macOS the video chat won’t show when we use H264 as video codec in wowza. When using VP8 it works fine. Problem with VP8 is that Flash doesn't support it. Chrome 57 and earlier versions didn’t have this problem.

We tried setting up a p2p sample web page without wowza but aren’t able to configure the video chat using H264.

Please let me know if there is anything else I might be able to add.

Comment 5 by holmer@chromium.org, May 16 2017

Cc: philipel@chromium.org
This could be related to the SEI issue, see: https://bugs.chromium.org/p/chromium/issues/detail?id=717884

stijnvanderlaan, could you verify if there are SEI packets in your stream? In that case I think we should dupe it. it to 717884.
Can you tell me how to check for this?

Comment 7 by hdodda@chromium.org, May 17 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
@stijnvanderlaan-- Could you please provide us a sample video link/file to reproduce the issue from test team end .

@holmer-- Could you please respond to comment #6 , on how to check the SEI packets ??

Thanks!

Comment 8 by e...@demonsters.nl, May 17 2017

Hi hdodda thanks for getting back to us (Im a co-worker from stijnvanderlaan). 

At this moment its very difficult for us to send you a sample video link/file. We dont see any problems during a p2p connection nor do we see problems when we change codecs in wowza to VP8. Things go wrong once we use H264.

We would be glad to tell you if the stream contains SEI packets and hopefully holmer can tell us how.

Comment 9 by holmer@chromium.org, May 30 2017

If you can get access to an unencrypted rtp stream with wireshark, you should be able to inspect the packets there and determine the nal types.

We have made some fixes to Chrome recently, so you may want to test with Chrome Canary and see if your issues have been resolved.
Thanks, it looks like it's fixed in Chrome Canary!
Project Member

Comment 11 by sheriffbot@chromium.org, May 30 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 719095
Status: Duplicate (was: Unconfirmed)
Good to hear!

Sign in to add a comment