Skip to content

adding whisper-large-v3 as an available model option#2

Open
NKeleher wants to merge 1 commit intomainfrom
feature/add-whisper-large-models
Open

adding whisper-large-v3 as an available model option#2
NKeleher wants to merge 1 commit intomainfrom
feature/add-whisper-large-models

Conversation

@NKeleher
Copy link
Copy Markdown
Contributor

Pull Request Summary 🚀

What does this PR do? 📝

Add the Large Whisper model as an option for transcription models.

Adding instructions about how to include new available models.

Why is this change needed? 🤔

In addition to the smaller Whisper models, we want access to Whisper Large V3, (the turbo version was already included in the script).

How was this implemented? 🛠️

updated the AVAILABLE_MODELS section of src/transcribe_audio.py with the HUgging Face models for whisper-large-v3

How to test or reproduce? 🧪

there are two audio files in tests/assets/audio you can use them to tests transcription input and output.

Use the following with whisper-tiny output is terrible but it's fast for testing:

uv run src/transcribe_audio.py uv run python src/transcribe_audio.py --input-path tests/assets/audio/ --output-path output/ --model whisper-tiny --format csv

Then use whisper-large-v3 (warning this may be slow to download the model and to run) *Do not run unless you have ample bandwidth and memory. note the --all-audio ensures that the transcriptions are re-run which is important if you previously ran transcription with other models.

uv run src/transcribe_audio.py uv run python src/transcribe_audio.py --input-path tests/assets/audio/ --output-path output/ --model whisper-large-v3 --format csv --all-audio

Screenshots (if applicable) 📷

Checklist ✅

  • I have run and tested my changes locally
  • I have limited this PR to less than 1000 lines of code change (if not, explain why)
  • I have updated/added tests to cover my changes (if applicable)
  • I have updated/added requirements to cover my changes (if applicable)
  • I have run linting and formatting on any code changes (if applicable)
  • I have updated the documentation (README, etc.) accordingly

Reviewer Emoji Legend

:code: Meaning
😃👍💯 :smiley: :+1: :100: I like this...

...and I want the author to know it! This is a way to highlight positive parts of a code review.
⭐⭐⭐ :star: :star: :star: Important to fix before PR can be approved...

And I am providing reasons why it needs to be addressed as well as suggested improvements.
⭐⭐ :star: :star: Important to fix but non-blocking for PR approval...

And I am providing suggestions where it could be improved either in this PR or later.
:star: Give this some thought but non-blocking for PR approval...

...and consider this a suggestion, not a requirement.
:question: I have a question.

This should be a fully formed question with sufficient information and context that requires a response.
📝 :memo: This is an explanatory note, fun fact, or relevant commentary that does not require any action.
:pick: This is a nitpick.

This does not require any changes and is often better left unsaid. This may include stylistic, formatting, or organization suggestions and should likely be prevented/enforced by linting if they really matter
♻️ :recycle: Suggestion for refactoring.

Should include enough context to be actionable and not be considered a nitpick.

@NKeleher NKeleher requested review from iabaako and noureini July 25, 2025 21:07
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

Successfully merging this pull request may close these issues.

1 participant