SpeechSynthesizer: include ResultId in SpeechSynthesisBookmarkEventArgs
See original GitHub issueThe SpeechSynthesisEventArgs
for SynthesisStarted
, Synthesizing
, SynthesisCompleted
and SynthesisCanceled
all contain a SpeechSynthesisResult
with a unique ID of speech synthesis result.
However, SpeechSynthesisBookmarkEventArgs
does not include this result Id.
When reusing the same SpeechSynthesizer
, there’s no possibility to map bookmarks to the synthesize results by using this unique id.
Is it possible to also include this unique ID in the bookmark event arguments as well, or are these two features so different that it’s up to the SDK users to implement such a mapping?
Thanks in advance!
Issue Analytics
- State:
- Created a year ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
SpeechSynthesizer class
Executes speech synthesis on plain text. The task returns the synthesis result. Constructor Details. SpeechSynthesizer(SpeechConfig, AudioConfig).
Read more >speech
Package speech provides functionality for speech recognizers along with their related configuration and event objects.
Read more >SpeechSynthesizer Class (System.Speech.Synthesis)
Provides access to the functionality of an installed speech synthesis engine. ... To add or remove lexicons, use the AddLexicon and RemoveLexicon methods....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This will be supported in the Speech SDK 1.25.0 release (early 2023).
Thank you for your input. It is possible to add the ID to the bookmark events as well. This is a feature request/bug. I’ve added it to our backlog. We will address this in a future release. Once the work is done, we will update this issue to let you know what release the feature/fix will be in.