Open Bug 970693 Opened 11 years ago Updated 2 years ago

Automate audio latency test metrics

Categories

(Core :: WebRTC: Audio/Video, defect, P3)

Product:
Core
Component:
WebRTC: Audio/Video
Type:
defect
Points:
2

Tracking

()

Milestone:
mozilla34
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: abr, Assigned: padenot)

References

(Blocks 2 open bugs)

Details

We need checkins to automatically trigger measurements of audio latency on all built platforms as part of continuous integration
Blocks: 970426
Depends on: 970698
Blocks: 970698
No longer depends on: 970698
This is a measurement of capture to render, with the network hop over loopback. Note that we plan to put this data into Talos, so plan accordingly.
I'm going to include in this graphing it in Talos instead of having two bugs
Assignee: nobody → rjesup
Assignee: rjesup → jib
Blocks: 906942
Priority: -- → P2
Whiteboard: [p=2, 1.5:p2, ft:webrtc]
Target Milestone: --- → mozilla32
Priority: P2 → P3
Whiteboard: [p=2, 1.5:p2, ft:webrtc] → [p=2, 1.5:p2, ft:webrtc][s=fx32]
No longer blocks: 970698
Audio latency should be a secondary-output of the SNR measurements (it looks at the SNR at different offsets, and reports the best SNR, which should also tell you the delay). Alternatively, we could send a single impulse at different periods, and then hunt for it, but I think the SNR measurement should be good enough. We'll want to feed this into the graph servers, and do it for all platforms we can.
Blocks: 1023648
No longer blocks: 970426
Assignee: jib → paul
Priority: P3 → P2
Target Milestone: mozilla32 → mozilla33
Target Milestone: mozilla33 → mozilla34
backlog: --- → webRTC+
Points: --- → 2
Rank: 25
Whiteboard: [p=2, 1.5:p2, ft:webrtc][s=fx32]
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.