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

Issue 809369 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

H264 encoder is not preserving capture timestamps.

Reported by j...@bebo.com, Feb 6 2018

Issue description

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

Steps to reproduce the problem:
1. run chrome with --enable-logging
2. https://appr.tc/?debug=loopback&vsc=h264

What is the expected behavior?

What went wrong?
Seeing a lot of warning log lines: 
"Encoder is not preserving capture timestamps"
when using H264 in WebRTC. 

Did this work before? N/A 

Chrome version: 64.0.3282.140  Channel: beta
OS Version: 10.0
Flash Version: Shockwave Flash 28.0 r0
 
chrome_debug.log
37.9 KB View Download
Components: Internals>Media
Labels: Needs-Triage-M64
Cc: krajshree@chromium.org
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #64.0.3282.140 and latest canary #66.0.3342.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. ran chrome with --enable-logging
2. https://appr.tc/?debug=loopback&vsc=h264
3. Did not observe any errors in console.

jake@ - Could you please check the attached screen cast and please let us know if anything missed from our side. Also please check the issue on canary #66.0.3342.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
809369.mp4
498 KB View Download

Comment 4 by j...@bebo.com, Feb 10 2018

I apologize, I forgot to mention that you'd have to join the video room. Since it's the encoder that's giving the WARNING log about preserving timestamps. 
I've just tested it on the new Chrome Beta (65.0.3325.51), I still see it. 

2018-02-09 17-15-06.flv
8.8 MB Download
Project Member

Comment 5 by sheriffbot@chromium.org, Feb 10 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@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

Comment 6 by j...@bebo.com, Feb 10 2018

Just tested Chrome Canary (66.0.3343.4), I did not see the WARNING log lines anymore.
Labels: Needs-Feedback
Tested the issue on chrome reported version 64.0.3282.140 using windows-10 with steps mentioned below:
1) Launched chrome reported version and navigated to URL: https://appr.tc/?debug=loopback&vsc=h264 and joined the video room
2) Exited from the room and opened Devtools > Console, seen many warning lines in console tab
3) Didn't observed warning message "Encoder is not preserving capture timestamps" as mentioned in Comment#0

@Reporter:
Please find the atatched screencast for your reference anf let us know your input on it which helps us in further triaging it.

Thanks!
809369.mp4
10.0 MB View Download
Components: -Internals>Media Blink>WebRTC>Video
Cc: brandtr@chromium.org
Owner: ilnik@chromium.org
Status: Assigned (was: Unconfirmed)
ilnik: Is this is a problem, or is this just an overly cautious log statement? 

Comment 10 by ilnik@webrtc.org, Feb 27 2018

It's only a warning. I am not sure exactly about since what version is that fixed, but on older versions of WebRTC it would cause us not to produce any timing frames. So only issue caused by that is less logging.

Comment 11 by ilnik@chromium.org, Feb 27 2018

Cc: -brandtr@chromium.org ilnik@chromium.org
Owner: brandtr@chromium.org
Status: WontFix (was: Assigned)
jake: Please see #10 why this is a benign logging output.

Sign in to add a comment