togethercomputer / togethercomputer/together-py
Whisper realtime translates non-English speech despite 99-language claim
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 31
Description
Impact
This is currently blocking the multilingual launch of our production macOS dictation application. The realtime openai/whisper-large-v3 endpoint translates non-English speech into English instead of transcribing it in the original language.
Primary reproduction: raw WebSocket protocol
Using Together's documented realtime WebSocket protocol:
- Connect to:
wss://api.together.ai/v1/realtime?intent=transcription&model=openai/whisper-large-v3&input_audio_format=pcm_s16le_16000&turn_detection=none - After
session.created, send:{"type":"transcription_session.updated","session":{"language":"auto"}} - Append 16 kHz mono PCM16 audio and commit the buffer.
- Repeat with
language: "es".
For audio saying:
Hola, buenos días.
Both Auto and explicit Spanish return:
Hello, good morning.
Independent confirmation
I reproduced the same behavior with Together's official Python SDK v2.28.0 using client.beta.realtime.transcription(...), with both language="auto" and language="es". A second Spanish recording returned an empty result when Spanish was explicitly selected.
Controls
The same recordings are transcribed correctly by:
- Together Parakeet realtime streaming
- Together Whisper REST with explicit
language="es"
This isolates the problem to the Together Whisper realtime path rather than the audio or client encoding.
Expected behavior
Realtime Whisper should preserve the source language, consistent with the model page's claim that streaming Whisper supports 99 languages:
https://www.together.ai/models/whisper-large-v3-streaming
Requested action
Please confirm whether realtime Whisper is currently English-only, fix the endpoint or correct the documentation, and provide an ETA or production-safe workaround. I can provide the original recordings and complete WebSocket event logs immediately.
@yadavsahil197 @sbeurnier @zainhas @blainekasten — tagging the public author and reviewers of the realtime SDK implementation because this is critical for our launch.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the raw WebSocket flow and the Python SDK call with the supplied Spanish recordings or event logs. Compare both realtime paths with Together Whisper REST and Parakeet, then trace the realtime transcription implementation; done means the endpoint preserves Spanish, or the documentation clearly states the limitation and gives a production-safe workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100