Enable Nemotron-3-Diarization on MLX, CUDA, XNNPACK, and Vulkan
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Ambito
- embedded-iot, machine-learning, mobile-dev
Direzione di ricerca
Start with the Nemotron-3-Diarization model card, checkpoint configuration, and Transformers integration linked in the issue, then compare them with the upstream NeMo reference and the NeMo-Speech.cpp option. Done requires export and native inference across MLX, CUDA, XNNPACK, and Vulkan, with documented commands, regression coverage, reference comparisons, and measured performance and delegation results.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
🚀 The feature, motivation and pitch
Enable NVIDIA Nemotron-3-Diarization in ExecuTorch, with export and native inference examples for MLX, CUDA, XNNPACK, and Vulkan. Support offline recordings and streaming audio so applications can produce speaker timestamps locally for meetings, calls, and speech pipelines.
The model card describes a ~100M-parameter model supporting up to eight speakers, ordered by first arrival. It consumes 16 kHz mono audio, uses 128-bin mel features and a 31-layer Transformer with RoPE, stacks features to an 80 ms encoder frame rate, and uses a Conv1D upsampling head to produce per-speaker activity probabilities at a default 10 ms resolution. Streaming preserves speaker identities through an Arrival-Order Speaker Cache (AOSC) and FIFO context.
Proposed scope
- Model loading and export: Add a reproducible example with pinned checkpoint and dependency revisions, a PyTorch reference, and backend selection. Export the neural computation to
.pteplus any required backend artifacts. Define input/output shapes, supported dtypes, and bounded sequence lengths or padded chunk sizes. Keep the shared model representation portable across the four backends. - Native inference: Provide a C++ runner and audio-file CLI covering mel preprocessing, chunk scheduling, AOSC/FIFO updates, and conversion of activity probabilities into speaker/start/end segments. Expose streaming feed, reset, and final-flush behavior; document which work runs on the host. Inference should run without Python or NeMo installed.
- Streaming and offline modes: Support the published 30.4 s offline-style configuration and 1.04 s, 0.64 s, and 0.32 s streaming presets. Preserve arrival-order speaker labels, look-ahead handling, padding masks, and timestamp alignment across chunks. These values are input-buffer latency, excluding compute time.
Backend workstreams
| Backend | Target | Work to validate and enable |
|---|---|---|
| MLX | Apple Silicon GPU | Lower the encoder and speaker head through the MLX delegate; validate RoPE, masked attention, Conv1D, and varying chunk/cache lengths. |
| CUDA | NVIDIA GPU | Integrate the CUDA export/runtime path; validate attention, shape handling, supported precision, and host/device transfer costs. Document the tested GPU and CUDA requirements. |
| XNNPACK | Arm and x86 CPU | Establish a floating-point CPU baseline; inspect attention/matmul, normalization, and Conv1D delegation, and tune threading. Validate dynamic shapes or provide padded/static variants where needed. |
| Vulkan | Supported Android and desktop GPUs | Validate attention, RoPE, Conv1D, tensor layouts, shape changes, and device limits. Add lowering/kernel support as needed and document any partitions assigned to XNNPACK or portable kernels during export. |
These are validation targets, not confirmed operator gaps. Record actual delegation coverage and remaining blockers for each backend. Establish floating-point correctness first; evaluate reduced precision and quantization separately against that baseline.
Acceptance criteria
- Each backend has documented export/build/run commands and a successful end-to-end run on named hardware, with delegation coverage and fallback operators reported.
- Compare preprocessing, per-frame probabilities, and final segments against the same pinned upstream reference. Report diarization error rate (DER) with the dataset, scoring settings, and agreed numerical/quality tolerances.
- Cover silence, overlapping speech, speaker arrivals, up to eight speakers, short/final chunks, reset between recordings, cache rollover, and long recordings with bounded streaming memory.
- Report model/artifact size, peak memory, real-time factor, and p50/p95 chunk processing latency at batch size 1, including preprocessing and state updates. Separate initialization/warm-up, input buffering, and steady-state compute; record hardware, precision, thread count, and streaming preset.
- Add regression coverage for export, runtime correctness, and streaming state handling, with documentation of supported configurations and remaining limitations.
Alternatives
The upstream NeMo and Transformers implementations provide reference inference. NeMo-Speech.cpp provides another native deployment option. This request brings the model into ExecuTorch's runtime and delegate ecosystem.
Additional context
- Model card and recommended streaming configurations
- Checkpoint configuration
- Transformers integration
cc @SS-JIA @manuelcandales @digantdesai @cbilgin @GregoryComer @JakeStevens @iseeyuan @lucylq @helunwencser @tarun292 @kimishpatel @jackzhxng @Gasoonjia @metascroy
- Lingua principale
- Python
- Stelle
- 5k
- Fork
- 1.2k
- Merge medio
- 2g 12h
- PR unite (30g)
- 588
Guida per i contributori
Apri 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 pytorch/executorch
-
enhancement triaged
Difficoltà 2/5 Mezza giornata Idoneità per principianti 68/100
pytorch/executorch#21640 ·
-
bug module: qnn module: quantization
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
pytorch/executorch#23108 ·
-
good first issue module: examples module: webgpu
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
pytorch/executorch#23099 ·
-
good first issue module: examples module: vulkan
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
pytorch/executorch#23098 ·
-
good first issue module: cuda module: examples
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
pytorch/executorch#23097 ·
Tutte le issue di pytorch/executorch
Issue simili
-
agent-ready documentation needs-triage
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
-
documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 92/100
-
instance instance add
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
searxng/searx-instances#939 · 1 commento ·
-
area-deployment area-integrations triage:bot-seen
Difficoltà 2/5 Mezza giornata Idoneità per principianti 86/100