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

When using the voice playback API provided by Microsoft, I cannot get all the installed voice packets in the system #108991

Open
vsfeedback opened this issue Oct 17, 2024 · 1 comment
Labels
area-System.Speech needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration question Answer questions and provide assistance, not an issue with source code or documentation.
Milestone

Comments

@vsfeedback
Copy link

vsfeedback commented Oct 17, 2024

This issue has been moved from a ticket on Developer Community.


[severity:It's more difficult to complete my work]
在使用SpeechSynthesizer.GetInstalledVoices()获取系统中的可用语音时只能获取到系统默认英文语音包和当前语言语音包,无法获取到我在windows设置在讲述人功能中下载的其他语音包 这使我很困惑


AI Summary (1 comments)
Issue Summary:

A user reported difficulty in retrieving all installed voice packs using the SpeechSynthesizer.GetInstalledVoices() API in Visual Studio. Specifically, they can only access the default English voice pack and the current language voice pack, but cannot retrieve other voice packs downloaded via the Windows Narrator settings. This issue complicates their work, prompting confusion. The feedback has been forwarded to the engineering team for further evaluation.

Reproduction Steps:

Use SpeechSynthesizer.GetInstalledVoices() in a Visual Studio project.
Note that only the default English voice and the current language voice are retrieved.
Voice packs downloaded from Windows Narrator are missing.

Original Comments

Feedback Bot on 8/22/2024, 08:26 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Oct 17, 2024
@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Oct 17, 2024
@steveharter steveharter added area-System.Speech and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Oct 17, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-speech
See info in area-owners.md if you want to be subscribed.

@steveharter steveharter added the question Answer questions and provide assistance, not an issue with source code or documentation. label Oct 17, 2024
@jeffhandley jeffhandley added needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration and removed untriaged New issue has not been triaged by the area owner labels Oct 20, 2024
@jeffhandley jeffhandley added this to the Future milestone Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Speech needs-further-triage Issue has been initially triaged, but needs deeper consideration or reconsideration question Answer questions and provide assistance, not an issue with source code or documentation.
Projects
None yet
Development

No branches or pull requests

3 participants