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

Issue 783784 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Email to this user bounced
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebAudio getOutputTimestamp().performanceTime origin is not performance.timing.navigationStart on Windows

Reported by geek.uil...@gmail.com, Nov 10 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36

Steps to reproduce the problem:
1. Create a webaudio context
2. Inspect the value of audioCtx.getOutputTimestamp().performanceTime after some time
3. The origin of getOutputTimestamp().performanceTime is not performance.timing.navigationStart

What is the expected behavior?
On Linux and Android at least, getOutputTimestamp().performanceTime origin is performance.timing.navigationStart as the specification requires.

What went wrong?
The origin of getOutputTimestamp().performanceTime on Windows is wrong.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 62.0.3202.89  Channel: stable
OS Version: 10
Flash Version: 

Test case available at: https://jsfiddle.net/mut12uwh/1/
 

Comment 1 by rtoy@chromium.org, Nov 10 2017

Status: Available (was: Unconfirmed)
Thanks for the repro case.  The time difference on Windows is huge, but linux has a diff of about 5-10 and macos has a diff of about 5.
Labels: Needs-Triage-M62

Comment 3 by rtoy@chromium.org, Nov 10 2017

Cc: mikhail....@intel.com
+mikhail.pozdnyakov Any ideas on what's happening here?
Owner: mikhail....@intel.com
Status: Assigned (was: Available)
rtoy@ thanks for cc'ing, I'm taking a look.
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 16 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/1f01492b35dc3ee926882ca534600d4cfb63b6b3

commit 1f01492b35dc3ee926882ca534600d4cfb63b6b3
Author: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com>
Date: Thu Nov 16 09:45:06 2017

[Windows] WASAPIAudioOutputStream: fix delay timestamp calculation

The 'qpc_position' result of IAudioClock::GetPosition must be
converted to raw QPC value before base::TimeTicks::FromQPCValue
can be called on it.

Bug:  783784 
Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: I4918c71e439d87b4e231cd9f8d73ac5ed6c69abb
Reviewed-on: https://chromium-review.googlesource.com/768682
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Henrik Andreasson <henrika@chromium.org>
Commit-Queue: Mikhail Pozdnyakov <mikhail.pozdnyakov@intel.com>
Cr-Commit-Position: refs/heads/master@{#517037}
[modify] https://crrev.com/1f01492b35dc3ee926882ca534600d4cfb63b6b3/media/audio/win/audio_low_latency_output_win.cc

Status: Fixed (was: Assigned)

Sign in to add a comment