New issue
Advanced search Search tips

Issue 645986 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 24
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

chrome webrtc send RTP use a random timestamp

Reported by wangh...@gmail.com, Sep 12 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.101 Safari/537.36

Example URL:

Steps to reproduce the problem:
1.sever send only H.264 sdp to chrome,and send H.264 RTP package to chrome.

2. 
3. 

What is the expected behavior?

decode a increasing random timestamp normally

What went wrong?
when I use a increasing timestamp ( like 20,40,60,80),
in webrtc-internal chrome can not decode RTP package.
when I use (capture time in ms * 90 + random offset),frome this https://bugs.chromium.org/p/webrtc/issues/detail?id=3111. However, render video have many problems (eg. green ,stuck)

Did this work before? N/A 

Is it a problem with Flash or HTML5? HTML5

Does this work in other browsers? Yes 

Chrome version: 53.0.2785.101  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0
 
Components: Blink>WebRTC
Labels: TE-NeedsTriageHelp
Added TE-NeedsTriageHelp as it seems it is out of scope from TE side.
Cc: hbos@chromium.org holmer@chromium.org
[triage]: holmer, hbos, what is the correct behavior here?

Comment 3 by holmer@chromium.org, Sep 14 2016

I don't understand the question. Are you saying that Chrome fails to decode if your rtp timestamps start at 0?
Labels: Needs-Feedback
[triage]: wanghb89, please respond to #3.

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

holmer@:
Yes,when timestamp start at 0, the chrome failds to decode H.264!
when I change to (capture time in ms * 90 + random offset), Chrome can decode and render the image

Project Member

Comment 6 by sheriffbot@chromium.org, Sep 25 2016

Labels: -Needs-Feedback Needs-Review
Owner: phoglund@chromium.org
Thank you for providing more feedback. Adding requester "phoglund@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: ----
holmer: is this a valid bug then?
Components: -Internals>Media

Comment 9 by guidou@chromium.org, Oct 26 2016

Components: -Blink>WebRTC Blink>WebRTC>Video
 Issue 644984  has been merged into this issue.
Owner: holmer@chromium.org
hbos, holmer - please close if not relevant anymore.
Status: Assigned (was: Unconfirmed)
Labels: -Needs-Review
Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]
Status: Archived (was: Assigned)

Sign in to add a comment