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

Suggestion: a time-based instead of word-based caption buffer #18

Open
casperdewith opened this issue Nov 4, 2024 · 1 comment
Open
Assignees

Comments

@casperdewith
Copy link

Currently, when setting up live captioning (Audiovisual > Captioning), the dialog box asks you to enter a buffer size, which is counted in words.

The ‘Captioning Settings’ dialog box, where the ‘Word buffer’ field has value 5.

I would like to be able to choose a different unit: a (real) number of seconds. This means that when this unit is selected, and I chose x seconds, any prefix of my buffer that has not changed for more than x seconds is output.

I request this functionality because some strokes in my steno theory have a lot of words. I obviously want to be able to undo any single stroke without anyone noticing, so I have to use a large buffer. As a consequence, though, the delay between me stroking a stroke and it being displayed is often long. And manually flushing the buffer after every sentence to shorten this delay is not fun.

@greenwyrt greenwyrt self-assigned this Nov 9, 2024
@greenwyrt
Copy link
Owner

I can definitely see the usefulness of this feature. The places that have to be changed are the display_captions in the window editor and send_cap in captionWorker. It probably will take me a bit of time to work on this, because the buffer mechanism right now is based solely on the text, and using the time is something different.

I have an idea of an approach and this is more a comment to myself: to start, in display_captions, subset paragraph element collection by last pos to word before cursor, do time diff, use length of elements that pass to move cursor to new position.

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