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

[Bug] Skip feature not working with Microsoft online voices #33

Open
Mitia99 opened this issue Dec 5, 2024 · 3 comments
Open

[Bug] Skip feature not working with Microsoft online voices #33

Mitia99 opened this issue Dec 5, 2024 · 3 comments

Comments

@Mitia99
Copy link

Mitia99 commented Dec 5, 2024

As the title says, skip feature doesn't work with Microsoft online voices

Tested with version 0.2.3
image

Thanks for investigating,

@gexgd0419
Copy link
Owner

As for now, the SAPI5 skipping feature isn't supported by this engine (for any voice, not just online ones), and is listed here as an unsupported feature.

Unlike some features that are impossible to implement, this one is doable. If there are proper sentence boundary events, I can skip sentences based on their timestamps.

Do you think it's necessary to implement this? How many TTS clients (other than the test app) utilize this feature?

@gexgd0419
Copy link
Owner

Note that the TtsApplication is mainly for testing basic SAPI5 TTS functionality, so the Skip button uses the SAPI5 built-in skipping feature provided by the TTS engine. Other TTS apps, such as Balabolka, may choose to stop speaking and then start speaking at the new position, in which case the SAPI5 skipping feature is not used.

@Mitia99
Copy link
Author

Mitia99 commented Dec 5, 2024

Do you think it's necessary to implement this? How many TTS clients (other than the test app) utilize this feature?

It will be great to support this. I found this issue while using PDF-XChange Editor(you can use it for free) btw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants