File generation versus terminal output #1321
-
I notice that whisper tries to generate files and that the types of files to be generated can be adjusted with --output_format {txt,vtt,srt,tsv,json,all}, -f {txt,vtt,srt,tsv,json,all}. What is the difference between these files and a file that is generated using the > character in the command line, e.g., using
I ask because I wonder if under certain conditions whisper will not have the permissions to write its own output files (e.g., when running as user www-data, as in the above example) but would nevertheless be able to write terminal output to a file using the > character. And if that is the case, I wonder whether one of the options for the --output_format command line switch should be "none". |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
It doesn't support Alternatively, you can write a separate Python script doing something similar to the Lines 374 to 453 in 248b6cb but skip the part saving the outputs. |
Beta Was this translation helpful? Give feedback.
It doesn't support
--output-format none
, and likely we won't plan to -- ifwww-user
can write to/tmp
, you can specify something like--output_dir /tmp/whisper
.Alternatively, you can write a separate Python script doing something similar to the
cli()
function:whisper/whisper/transcribe.py
Lines 374 to 453 in 248b6cb