Expose the currently used cubeb backend for support purposes

RESOLVED FIXED

Status

()

Core
Audio/Video: cubeb
P4
normal
Rank:
45
RESOLVED FIXED
5 years ago
a year ago

People

(Reporter: kinetik, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Since bug 837564 makes it possible for different backends to be used depending on a given machine's capabilities, we may need to know which backend is in use for support purposes.

It might makes sense to expose the result of calling cubeb_get_backend_id(ctx) in about:support, but at a minimum we should log it via NSPR logging.
(Reporter)

Updated

5 years ago
Depends on: 837564
OS: Linux → All
Hardware: x86_64 → All
backlog: --- → webrtc/webaudio+
Rank: 45
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
Priority: -- → P4
backlog: webrtc/webaudio+ → ---
Component: Audio/Video: MediaStreamGraph → Audio/Video: cubeb
(Reporter)

Comment 1

a year ago
This was done in bug 1288980, and bug 1197045 covers extending it.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.