vibevoice-asr

Transcribes audio with VibeVoice ASR on Google Colab using BitNet CPU or 7B GPU models.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/franklinbaldo/skills --skill vibevoice-asr-franklinbaldo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibevoice-asr
Source: https://github.com/franklinbaldo/skills/tree/main/vibevoice-asr
Command: npx skills add https://github.com/franklinbaldo/skills --skill vibevoice-asr-franklinbaldo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires huggingface-hub, torch, transformers, accelerate, librosa, soundfile, google-colab-cli, and includes scripts (resource) components.

What problem does it solve? Transcribing long audio recordings with speaker labels and timestamps requires either expensive local GPU hardware or manual cloud setup. This Skill runs Microsoft's VibeVoice ASR models on Google Colab through the official Colab CLI, letting you choose between a low-cost CPU path and a high-accuracy GPU path without owning the hardware. ## Core Features & Use Cases - Dual model paths: Run the economical BitNet build (VibeASR.cpp, CPU-only) or the full 7B VibeVoice-ASR-HF model on A100/H100 GPUs, with an explicit, never-hidden fallback from full to BitNet. - Structured transcription output: Produces a plain transcript, a metadata JSON with model revision, hardware, duration, and parsed speaker/timestamp segments, plus a stderr log for auditing. - Hotwords and batch sessions: Pass domain vocabulary via --context (e.g., legal entity names) and reuse named Colab sessions to transcribe batches without recompiling or re-downloading models. - Use Case: A legal team needs to transcribe hours of Portuguese hearing recordings. Use the full model on an A100 with context hotwords like "IPERON, Sisprev, Procuradoria-Geral do Estado" to get accurate speaker-labeled transcripts with timestamps. ## Quick Start Use the vibevoice-asr skill to transcribe my recording.wav file on Colab with the full 7B model on an A100 GPU, including the hotwords IPERON and Sisprev.

Frequently Asked Questions about vibevoice-asr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I transcribe audio with VibeVoice ASR on Google Colab?▼

Run the run_colab.sh wrapper with your audio file and an output prefix. It creates a Colab session, uploads the audio (converted to MP3 by default), executes the transcription job remotely, and downloads the transcript, metadata JSON, and log.

What is the difference between VibeVoice-ASR-BitNet and VibeVoice-ASR-HF?▼

BitNet is a 1.58 GB quantized build running on CPU via VibeASR.cpp, suited for low-cost triage and batches. VibeVoice-ASR-HF is the full 7B checkpoint requiring a high-memory GPU like A100, offering higher accuracy; published Portuguese WER was 22.41 for the 7B versus 24.87 for BitNet.

Does VibeVoice ASR work on Windows?▼

The Google Colab CLI officially supports Linux and macOS. On Windows you must use WSL; without WSL or admin permission, choose another Linux environment. The audio itself is processed remotely on Colab infrastructure.

What happens if the A100 GPU is not available for the full model?▼

By default the job fails rather than silently downgrading. If you pass --fallback-bitnet, the wrapper explicitly falls back to the BitNet CPU path and records the requested model, effective model, and fallback reason in the metadata.

How do I improve transcription of names and acronyms in audio?▼

Pass hotwords with the --context option, for example organization names, acronyms, and vocabulary likely to appear in the recording. The context is sent to the remote runtime with the job but is not repeated in the metadata output.

Can I transcribe multiple audio files without re-downloading the model each time?▼

Yes. Use --session with --keep for the first file, then --session with --reuse for subsequent files in the same named session. A reused session keeps its original accelerator, and you stop it manually with the Colab CLI when done.