Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Audio subsystem detection needs different handling on display-audio-only platforms on Windows #644

Open
filipleple opened this issue Dec 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@filipleple
Copy link
Member

Device

VP3210 for example

RTE version

any

OSFV version

any

Affected component(s) or functionality

No response

Brief summary

Audio subsystem detection needs different handling on display-audio-only platforms on Windows. Get-WmiObject -class Win32_SoundDevice returns nothing on VP3210, even though an HDMI monitor is being properly detected and listed as an output in the sound settings.

How reproducible

100%

How to reproduce

Connect an HDMI monitor to VP3210, note that it's properly detected in the sound settings and run Get-WmiObject -class Win32_SoundDevice

Expected behavior

According to AUD001.002 in OSFV as of now, some entry related to the display audio subsystem should be listed

Actual behavior

The command returns no output, even though the display audio option does reliably get detected

Link to screenshots or logs

PS C:\Users\user> Get-WmiObject -class Win32_SoundDevice
PS C:\Users\user>

Additional context

No response

Solutions you've tried

No response

@SebastianCzapla
Copy link
Contributor

Will address it in: #634

Btw during tests of the feature, I got audio detected on Display Port, but not on HDMI, not sure why is it that way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants