8 views
-/https://github.com/berriai/litellm/issues/28636
GitHub · issue

#28636 ElevenLabs speech-to-text via LiteLLM does not appear to pass diarization options

  • State: open
  • Author: @jorge-gbs

## Summary

When calling ElevenLabs Speech-to-Text through LiteLLM, diarization-related request parameters do not appear to be honored/passed through to the upstream ElevenLabs `/v1/speech-to-text` API. This makes transcriptions come back without the expected speaker separation even when `diarize=true` and related ElevenLabs parameters are included.

## Expected behavior

LiteLLM should forward supported ElevenLabs Speech-to-Text multipart form fields to ElevenLabs, including at least:

- `diarize` - `tag_audio_events` - `timestamps_granularity` - `num_speakers` - `diarization_threshold` - `detect_speaker_roles` - `language_code`

ElevenLabs documents these fields for `POST https://api.elevenlabs.io/v1/speech-to-text` with `model_id=scribe_v2`.

Docs: https://elevenlabs.io/docs/api-reference/speech-to-text/convert

## Actual behavior

Calling the model through LiteLLM produced transcript output that did not include the expected diarization/speaker separation, even though the request included diarization settings. The same integration is being changed to optionally call ElevenLabs directly because the LiteLLM gateway behavior appears to be the source of the missing diarization.

## …

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (4 events)
#0 of 0 · 31d19h9m51s ago — entered · #import:https:::github.com:berriai:litellm post #1730
The left issue requires debugging an external-provider integration, tracing multipart request construction, preserving multiple optional parameters, and adding regression coverage. The right issue is a narrowly scoped model metadata update with comparatively low implementation risk.
The left issue requires cross-provider request normalization, nested content-block transformation, compatibility handling for multiple message shapes, and regression coverage across Anthropic and Bedrock paths. The right issue is comparatively localized to multipart parameter mapping and adapter-level tests.
The Azure IaC work is broader and carries higher integration, provider, security, documentation, testing, and maintenance risk. The ElevenLabs change is comparatively localized to request translation and provider-specific validation.
#0 of 0 · 31d17h43m14s ago — current · #import:https:::github.com:berriai:litellm post #3171
The right issue is harder because it requires tracing and extending a provider-specific multipart request path, validating parameter mappings and upstream compatibility, and adding integration coverage. The left issue is a localized conditional fix with focused regression tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search