Add a new Cubeb API to get the hardware name, driver name and version of the sound card

NEW
Assigned to

Status

()

Core
Audio/Video: cubeb
P3
normal
Rank:
25
a year ago
8 months ago

People

(Reporter: chunmin, Assigned: chunmin)

Tracking

(Blocks: 2 bugs)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Assignee)

Description

a year ago
Per discussion in https://bugzilla.mozilla.org/show_bug.cgi?id=1197045#c22, we need a new Cubeb API to expose the debugging information.
(Assignee)

Updated

a year ago
Assignee: nobody → cchang
(Assignee)

Updated

a year ago
See Also: → bug 1197045
(Assignee)

Updated

a year ago
Blocks: 1378634

Updated

a year ago
Rank: 25
Priority: -- → P2
For Windows, it'd also be really nice if we could find out if enhancements (audio processing objects or APOs) are enabled for a device.  This is available in the Sound control panel under the Properties for a given device on the Enhancement tabs.  Unfortunately, there doesn't appear to be a public Windows API to enumerate these things (or even detect if enhancements are disabled).  It looks like it's possible to dig through the registry to find this info, but it might be quite painful to work this out and may be more effort than it's worth investing at the moment.

Comment 2

11 months ago
I had a quick look. Is [0] not appropriate here ?

[0]: https://docs.microsoft.com/en-us/uwp/api/Windows.Media.Effects.AudioRenderEffectsManager

Comment 3

11 months ago
From MSDN [0]:

> Application Audio Effect Awareness

> Applications have the ability to call APIs to determine which audio 
> effects are currently active on the system. For more information on
> the audio effects awareness APIs, see AudioRenderEffectsManager class.

[0]: https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/audio-processing-object-architecture
(In reply to Paul Adenot (:padenot) from comment #2)
> I had a quick look. Is [0] not appropriate here ?

Those are Windows 10 Universal Windows Platform (UWP) APIs, so it's not immediately obvious if they're usable (https://blogs.windows.com/buildingapps/2017/01/25/calling-windows-10-apis-desktop-application/), but that is the sort of query API we want.

(In reply to Paul Adenot (:padenot) from comment #3)
> https://docs.microsoft.com/en-us/windows-hardware/drivers/audio/audio-
> processing-object-architecture

That stuff in your second comment is WDM/system level AFAICT.
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
(Assignee)

Updated

8 months ago
Duplicate of this bug: 1408309
(Assignee)

Updated

8 months ago
Blocks: 1408307
(Assignee)

Comment 7

8 months ago
Created attachment 8918732 [details]
1. Audio hardware on OSX - USB.png
(Assignee)

Comment 8

8 months ago
Created attachment 8918733 [details]
2. Get audio device info from USB.png

To get the audio device information in detail, we might need to query the audio device fisrt(attachment 8918732 [details]), then get the information from its `transport` port. 

------------
Note:

How to get the audio devices:
$ system_profiler SPAudioDataType

How to get the USB devices:
$ system_profiler SPUSBDataType
or 
$ ioreg -p IOUSB
You need to log in before you can comment on or make changes to this bug.