The events speechRecognizer.ContinuousRecognitionSession.ResultGenerated and speechRecognizer.HypothesisGenerated do no longer work
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- desktop, operating-systems
Research direction
Start in the mentioned Scenario_ContinuousDictation.cs file, especially the ContinuousRecognitionSession_ResultGenerated handler and the speechRecognizer event setup. Reproduce the issue with the listed Speech4TTS option 8 steps on the stated UWP configuration, then verify that recognition events fire and dictated text appears in the Message Dication field.
Written by the indexing model from the issue text.
Description
Which sample are you reporting a bug in?
Example: SpeechAndTTS
Describe the bug
In the case continouus dictation sample no events with the recognized are raised.
The code is in Scenario_ContinuousDictation,cs
I canot link to a code line because the event that shoild be raised, speechRecognizer.ContinuousRecognitionSession.ResultGenerated for example is just not called.
To Reproduce
- Download the sample
- Run the Speech4TTS sample
- Select option 8
- Select a language
- Click "Dictate"
Expected behavior
Speech is translated into text and shown in the field Message Dication or a break point in the first line of ContinuousRecognitionSession_ResultGenerated is hit.
Screenshots
If applicable, add screenshots to help explain your problem.
Configuration
- UWP
- Windows Desktop Version 25H2 Build 26200.9168
- Visual Studio version: 18.9.2
Additional context
Add any other context about the problem here.
Online Speech recognition is set in the Windows privacy settings
- Dominant language
- JavaScript
- Stars
- 9.7k
- Forks
- 7.8k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/Windows-universal-samples
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
microsoft/Windows-universal-samples#1442 · 6 comments ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
microsoft/Windows-universal-samples#1440 · 3 comments · 1 reaction ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/Windows-universal-samples#1437 · 3 comments ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/Windows-universal-samples#1435 · 7 comments ·
All issues in microsoft/Windows-universal-samples
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100