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 output device names truncated to 32 characters #2067

Open
nvaccessAuto opened this issue Jan 29, 2012 · 6 comments
Open

Audio output device names truncated to 32 characters #2067

nvaccessAuto opened this issue Jan 29, 2012 · 6 comments
Labels
bug component/audio NVDA's audio output (nvWave, issues with usb audio etc). component/NVDA-GUI

Comments

@nvaccessAuto
Copy link

Reported by HKatic on 2012-01-29 13:10
In NVDA's synthesizer preferences dialog, the Output Device Combo Box displays incomplete device names. For example, I have 2 sound cards, the one which is Realteck High Definition Audio, and another which is SoundBlaster X-Fi Surround 5.1 Pro. However, they are displayed as follows:
Output device: Speakers (Realtek High Definiti
Output device: Speaker (Sound Blaster X-Fi Sur
This simply means that the entire device name doesn't fit into the Combo Box control, and that the control or dialog itself needs to be resized.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-01-29 21:54
It has nothing to do with the size of the combo box control. The issue is that the Windows API function we use to retrieve the device names only returns a maximum of 32 (or maybe 31) characters.
Changes:
Changed title from "The Output Device Combo Box in Synthesizer preferences needs resizing" to "Audio output device names truncated to 32 characters"

@bhavyashah
Copy link

@jcsteh As you indicated in #2067 (comment), the reported issue is a limitation of the Windows API function we use. Do we have alternatives to use with a more relaxed character limit? CC @feerrenrut for GUI expertise

@jcsteh
Copy link
Contributor

jcsteh commented Aug 15, 2017

I don't know. There are newer APIs, but the question is whether we can map these back to WinMM device identifiers. Further research is required.

@michaelDCurran michaelDCurran added the component/audio NVDA's audio output (nvWave, issues with usb audio etc). label Jan 26, 2019
@Adriani90
Copy link
Collaborator

@hkatic is this also in Windows 10 the case?

@Adriani90
Copy link
Collaborator

I can reproduce this in NVDA alpha-20097,6a573cd9.
cc: @JulienCochuyt

@JulienCochuyt
Copy link
Collaborator

Found a few hints here: https://stackoverflow.com/questions/1449162/get-the-full-name-of-a-wavein-device/43396412

Long story short:

  • First pass a WAVEOUTCAPS2 structure to gain the device GUID then lookup in registry
  • If this fails (no info in registry), use DirectSound to fetch device info

It's doable, but a bit complicated for what it attempts to solve...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component/audio NVDA's audio output (nvWave, issues with usb audio etc). component/NVDA-GUI
Projects
None yet
Development

No branches or pull requests

6 participants