Temporarily bump audio input and output latency on OSX as a stop-gap measure, on macbook pros

RESOLVED FIXED in Firefox 63

Status

()

enhancement
P2
normal
Rank:
15
RESOLVED FIXED
11 months ago
11 months ago

People

(Reporter: padenot, Assigned: padenot)

Tracking

Trunk
mozilla63
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox63 fixed)

Details

Attachments

(1 attachment)

Assignee

Description

11 months ago
No description provided.
Assignee

Updated

11 months ago
Assignee: nobody → padenot

Comment 2

11 months ago
mozreview-review
Comment on attachment 8993614 [details]
Bug 1477200 - Temporarily bump audio input and output latency on OSX as a stop-gap measure, on macbook pros.

https://reviewboard.mozilla.org/r/258314/#review265366

::: dom/media/GraphDriver.cpp:600
(Diff revision 1)
>        if (!strncmp(model.get() + offset, "Air", 3) ||
>            isdigit(model[offset + 1])) {
>          return true;
>        }
>      }
> -    return false;
> +    return true;

can you add a comment here about the why?

Comment 3

11 months ago
mozreview-review
Comment on attachment 8993614 [details]
Bug 1477200 - Temporarily bump audio input and output latency on OSX as a stop-gap measure, on macbook pros.

https://reviewboard.mozilla.org/r/258314/#review265368

I did some tracing without and with this patch on appear.in, and saw a rough 10-fold improvement in number of budget overruns. This is the reason for the r+. Please also file a followup (mentioned in comment) to tune it back down and link it to somewhere in the tree of perf improvement bugs.
Attachment #8993614 - Flags: review?(apehrson) → review+
On a similar note I don't see the benefit of having the smallest possible latency for webrtc since we have to buffer 10ms of data until we pass it to the processing. Lower latency means lower budget, means more cheap iteration that will only buffer data but, in the end, the iteration that will execute the processing will have less time available for the same amount of data.
Assignee

Comment 5

11 months ago
(In reply to Alex Chronopoulos [:achronop] from comment #4)
> On a similar note I don't see the benefit of having the smallest possible
> latency for webrtc since we have to buffer 10ms of data until we pass it to
> the processing. Lower latency means lower budget, means more cheap iteration
> that will only buffer data but, in the end, the iteration that will execute
> the processing will have less time available for the same amount of data.

This is only in the case where we're using the APM and PeerConnection, but yes. Having the fastest latency possible is very important for Web Audio use-cases.
Comment hidden (mozreview-request)

Comment 7

11 months ago
Pushed by paul@paul.cx:
https://hg.mozilla.org/integration/autoland/rev/3f95add38e74
Temporarily bump audio input and output latency on OSX as a stop-gap measure, on macbook pros. r=pehrsons

Updated

11 months ago
Rank: 15
Priority: -- → P2

Comment 8

11 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/3f95add38e74
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla63

Updated

11 months ago
Depends on: 1478381
You need to log in before you can comment on or make changes to this bug.