Replies: 3 comments 2 replies
-
Another case I get often, is that sometimes it starts well, and at some point it just starts completely messing up the natural order of the sentence and creates very long blocks without stopping at the end of sentences:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
I posted sample code for segmenting whisper output into sentences here: |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hope this can be done someday. It will be very useful in occasions where a full sentence is prefered. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've been using whisper for more than a year, and using a lot of various options to generate SRT file.
But I have never managed to get a stable output where Whisper respects the natural sentence flow.
I don't get it and come here for some help... if anyone can help.
The command I mostly use is as such:
whisper interview_lukas_english.mp4 --language English --model large-v2 --output_format srt --word_timestamps True --highlight_words True --initial_prompt "Hello. My name is Tom. Welcome to my YouTube channel."
I'm using --word_timestamps True and --highlight_words True to have some extra post-processing after Whisper (mainly to fix the issue I'm describing here).
The output I'm getting is the following:
I feel like Whisper is trying hard that every sentence is exactly the same length, but I don't need that. What I would prefer is that every stence stops at the final dot, or if not possible, at a comma, and if there's none of them and the sentence is too long, cut where it makes sense to cut.
What I would expect:
Note that I've also tried the more recent option
--max_words_per_line
which doesn't work well for me, because it chops sentences at non-natural places.Any advice, anyone?
Beta Was this translation helpful? Give feedback.
All reactions