Open Bug 1612093 Opened 6 years ago Updated 2 years ago

AudioContext.outputLatency on Fenix is wrong

Categories

(Core :: Web Audio, defect, P3)

Product:
Core
Component:
Web Audio
Type:
defect

Tracking

()

People

(Reporter: padenot, Assigned: padenot)

Details

It's returning weird values in 74, and nothing in 71.

I had a look at the code and 1 is off. There is a integer division instead of a floating point division in the second part of the calculation.

Assignee: nobody → padenot
Priority: -- → P3
Severity: normal → S3

just checkin' in since I reported this via email, and outputLatency stability came up in some discussions .. this is still a thing in release 116 and nightly 118

Simon, what Android version are you running on the system that exhibit the issue? We've landed a new audio backend for Android that doesn't have this issue, but it's enabled only on select Android versions because of issues in some OEM version of the system code.

Flags: needinfo?(simon.mainey)

Galaxy A30, Android 11

Flags: needinfo?(simon.mainey)
You need to log in before you can comment on or make changes to this bug.