Feature: Support fishaudio/drama-3 (multi-speaker TTS, 35B-A3B MoE)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 6/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Ambito
- machine-learning
Direzione di ricerca
This is scoping work, not a code change. Start by checking whether the existing TTS task strategy covers reference-audio conditioning, speaker tags and streaming, and look at how the transform-model flow onboards a family. Identify the codec for the 10 codebooks and confirm whether TensorRT can consume the FP8 experts. Done means an agreed design and validation plan, not a patch.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Request type
New model or checkpoint support
Problem and use case
Request support for fishaudio/drama-3 (https://huggingface.co/fishaudio/drama-3), a multi-speaker, long-form text-to-speech model. TensorRT-Model-Connect has no family for it today, and no existing issue or PR covers it (searched for drama, fishaudio, fish audio).
Per the model card, the model:
- has about 36B total parameters (safetensors, BF16 and F8_E4M3 tensors);
- uses a 35B mixture-of-experts text backbone with 3B active parameters per token and hybrid full/linear attention;
- uses a codebook-MTP audio decoder that decodes 10 codebooks causally over the whole sequence, with FP8 MoE experts and the remaining weights in BF16;
- supports up to 16 speakers through
<|speaker:0|>...<|speaker:15|>tags, voice cloning from a reference clip plus transcript, point tags for emotion control, audio editing as continuation, and automatic chunking and streaming for long text; - is released under the Fish Audio Community License, and its reference deployment path is SGLang-Omni.
Proposed outcome
A drama_3 model family (or whatever name the maintainers prefer) that onboards the checkpoint through the normal transform-model flow and produces a bundle that passes family validation against the reference implementation.
Model and target details
- Model:
fishaudio/drama-3(revision to be pinned at onboarding) - Task: text-to-speech with multi-speaker and reference-audio conditioning
- Precision: BF16 with FP8 (E4M3) MoE experts as shipped; other precisions need separate evaluation
- Target GPU: not decided
Open questions (unverified, need scoping before implementation)
- Task fit: The current audio contract is mono-only. It is unclear whether the existing TTS task strategy covers reference-audio conditioning, speaker tags, and streaming output, or whether a new task or an extension is needed first.
- Codec: The model card does not say which codec turns the 10 codebooks back into a waveform. It has to be identified and covered too.
- Architecture overlap: The text backbone looks like a hybrid-attention MoE. Family ownership rules mean any code is duplicated into the new family rather than shared with
qwen_moeor similar families. - FP8 experts: Need to confirm that TensorRT can consume the shipped FP8 expert weights, or whether a dequantized BF16 path is the baseline.
- Size: 36B parameters is far above the current families. Single-GPU feasibility and the validation plan have to be settled.
- License: The Fish Audio Community License terms need review before redistributing any bundle or fixture.
Alternatives considered
The model card's only documented runtime is SGLang-Omni.
- Lingua principale
- Python
- Stelle
- 276
- Fork
- 73
- Merge medio
- 1g 9h
- PR unite (30g)
- 156
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di NVIDIA/TensorRT-Model-Connect
-
Docs: ITrtModule::forward() output-buffer lifetime and dtype contract are undocumentedForse di nuovo libera Una pull request per questa issue è stata chiusa senza essere unita. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
NVIDIA/TensorRT-Model-Connect#1126 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
[Accuracy] MoGe selected convolutions replace Native replicate padding with zerosForse già presa @chaofengw-nv l’ha presa 7 giorni fa. Apertabug
NVIDIA/TensorRT-Model-Connect#1727 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Feature: Nomic Embed Text v1.5 native embeddingsForse già presa @JiaxinD l’ha presa 19 giorni fa. Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
NVIDIA/TensorRT-Model-Connect#1582 ·
I maintainer di solito rispondono entro 1 giorno
-
retry_backoff retries the entire multi-family GPU test run even when a single family's genuine (non-transient) failure is the causeForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
NVIDIA/TensorRT-Model-Connect#1576 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
NVIDIA/TensorRT-Model-Connect#1567 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di NVIDIA/TensorRT-Model-Connect
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
gramaziokohler/compas_timber#870 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
autowarefoundation/autoware_carla_scenario#500 ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue priority: low size: XS testing
Difficoltà 1/5 1-3 ore Idoneità per principianti 86/100
cubrid-lab/cubrid-mcp-server#385 ·
I maintainer di solito rispondono entro 1 giorno
-
good first issue priority: low size: S testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
cubrid-lab/cubrid-cookbook-python#447 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100