Replies: 3 comments 1 reply
-
Ah - weird. Fixed the issue. I was running on Windows in Anaconda shell. Somehow when it launches a new window for a shell it doesn't handle the extended uni characters well. I got around the problem by just typing 'bash' in the Anaconda shell and then launching the little script with bash so that all the whisper run stayed in that same environment. This is the "fun" of running Whisper under WSL2 in Windows 11 I guess. |
Beta Was this translation helpful? Give feedback.
-
The problem is the following line (under Windows 11): c:\Python311\Lib\site-packages\whisper\transcribe.py line 339:
If I replace it to the following then it does not crash anymore but it also does not produce the correct output:
Maybe someone with enough python knowledge can correct this. A possible solution is described here: https://stackoverflow.com/questions/10569438/how-to-print-unicode-character-in-python In any case the output must be UTF-8 for TXT and JSON VTT and other files so that all languages will work correctly. |
Beta Was this translation helpful? Give feedback.
-
add_to_textfile() function no longer exists in utils.py |
Beta Was this translation helpful? Give feedback.
-
When I run Whisper in a batch model on the large model it produces a musical symbol and fails.
Seems to work fine though in a normal command line just not in a shell as below. Odd?
Any suggestions?
here's the script:
for f in *.mp4
do echo 'Start processing: ' "${f}" $(date)
whisper --language en --model large --device cuda --verbose True --condition_on_previous_text False --temperature_increment_on_fallback None --output_dir whisp_out_large "${f}"
whisper --model large --language en --device cuda --verbose True --output_dir whisp_out_large "${f}"
mv "${f}" "./_transcription_done_large/${f}"
echo 'Stop processing: ' "${f}" $(date)
done
Here's the full output:
Beta Was this translation helpful? Give feedback.
All reactions