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.

Sign up for GitHub

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

Jump to bottom

Missing boundary events for Google voices on Chrome desktop #4

Open
HadrienGardeur opened this issue Apr 28, 2024 · 0 comments
Open

Missing boundary events for Google voices on Chrome desktop #4

HadrienGardeur opened this issue Apr 28, 2024 · 0 comments
Assignees
@HadrienGardeur
Labels
external-issue Issues that are also tracked in an external issue tracker

Comments

@HadrienGardeur
Copy link
Owner

HadrienGardeur commented Apr 28, 2024 •
edited
Loading

Boundary events are quite important for playback and highlighting, as knowing which word is being read is required for features such as:

  • turning the page when an utterance is spread across multiple pages
  • or highlighting the current word being read differently from the full utterance

In addition to its issue with playback of longer utterances (reported in #3), Google voices also have an additional issue: they do not return boundary events.

Links:

  • TBD
@HadrienGardeur HadrienGardeur added external-issue Issues that are also tracked in an external issue tracker playback Related to the playback step for read aloud labels Apr 28, 2024
@HadrienGardeur HadrienGardeur self-assigned this Apr 28, 2024
@HadrienGardeur HadrienGardeur changed the title Missing boundary events for Google voices on Chrome OS desktop Missing boundary events for Google voices on Chrome desktop May 3, 2024
@HadrienGardeur HadrienGardeur removed the playback Related to the playback step for read aloud label May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@HadrienGardeur HadrienGardeur

Labels
external-issue Issues that are also tracked in an external issue tracker
Projects
Known-issues for read aloud
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@HadrienGardeur