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

#29367 Feature Request: Add FunASR as audio/transcriptions provider

  • State: open
  • Author: @LauraGPT
  • Labels: llm translation

<!-- funasr-ops:accuracy-note-20260714 --> > [!NOTE] > **License and capability clarification (2026-07-14):** FunASR is a toolkit, not a single checkpoint. The [FunASR](https://github.com/modelscope/FunASR#license) and [SenseVoice](https://github.com/FunAudioLLM/SenseVoice#license) repository source code is MIT; model weights follow each model card. [SenseVoiceSmall](https://huggingface.co/FunAudioLLM/SenseVoiceSmall) supports Chinese, Cantonese, English, Japanese, and Korean, and its weights use the linked FunASR Model Open Source License Agreement. [Fun-ASR-Nano-2512](https://huggingface.co/FunAudioLLM/Fun-ASR-Nano-2512) is Apache-2.0. Language coverage, punctuation, and performance depend on the selected model and runtime configuration.

## Feature Request

LiteLLM already supports `/audio/transcriptions` with multiple providers. FunASR would be an excellent self-hosted provider addition.

**Why FunASR?**

- **OpenAI-compatible API**: `funasr-server` provides `/v1/audio/transcriptions` — should be straightforward to add as a provider - **SenseVoice**: 50+ languages, 5-10x faster than Whisper, 234M params - **Self-hosted**: No API key, fully local — many LiteLLM users need on-pre…

GitHub resolver

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

Refresh page
vote history (3 events)
#0 of 0 · 31d19h9m1s ago — entered · #import:https:::github.com:berriai:litellm post #1727
Configurable timezone support is harder because it spans backend aggregation, date-boundary semantics, exports, UI formatting, configuration validation, and timezone/DST compatibility. The provider addition is more contained around an audio adapter, request handling, and provider-specific tests.
Adding a new audio provider spans provider architecture, request translation, configuration, dependency/runtime compatibility, tests, and documentation. The fallback defect is narrower, mainly involving conditional request construction and regression coverage, though it carries subtle cross-provider behavior risk.
#0 of 0 · 31d17h39m49s ago — current · #import:https:::github.com:berriai:litellm post #3213
Terraform support is harder because it requires coordinated provider schema, lifecycle behavior, state handling, validation, and compatibility testing, whereas the other task is comparatively contained to a single provider integration and its adapter tests.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search