Similar to Whisper PR#228, this adds -ocsv, aka --output-csv, writing CSV file containing millisecond timestamps #340
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For efficiency in storage, parsing and accuracy from representing timestamps in milliseconds (rather than floating-point numbers), this PR, like openai/whisper#228 adds feature to output CSV file containing lines formatted like:
<startTime-in-integer-milliseconds>, <endTime-in-integer-milliseconds>, "<transcript-line-including-commas>"
The CSV file is created when option
-ocsv
, or--output-csv
is provided to the 'main' command-line.Similar to the output file naming conventions for
--output_vtt
or--output_srt
, the resulting CSV file for an input file named<mediaBaseName>.wav
is named<mediaBaseName>.wav.csv