FFmpeg Errors
Issues with FFmpeg audio capture and device enumeration.
Symptoms
- "FFmpeg not found" error
- "Failed to start audio capture" message
- Audio devices not listed
- Silent audio levels despite speaking
- FFmpeg error in logs
Common Errors
Error: FFmpeg Not Found
Message:
Failed to start audio capture: FFmpeg not foundWindows Solutions:
- Reinstall Intervu — Bundled FFmpeg downloads during installation
- Use system FFmpeg — Set custom path in Settings → Advanced → FFmpeg Path
macOS Solutions:
- Install FFmpeg via Homebrew — FFmpeg is not bundled on macOS
brew install ffmpeg- Verify installation:
ffmpeg -version- Set custom path if needed — In Settings → Advanced → FFmpeg Path:
- Intel Macs:
/usr/local/bin/ffmpeg - Apple Silicon Macs:
/opt/homebrew/bin/ffmpeg
- Intel Macs:
Error: Device Not Found
Windows Message:
[dshow] Could not find device "CABLE Output"Causes:
- VB-Cable not installed
- Device name changed
- Windows audio system needs refresh
Solutions:
- Install VB-Cable (see No Audio Devices)
- Reboot
- Check exact device name in Windows Sound Settings
macOS Message:
[avfoundation] Could not find device ":0"Causes:
- FFmpeg not installed or lacks AVFoundation
- Microphone permission not granted
- Device disconnected
Solutions:
- Install FFmpeg:
brew install ffmpeg - Grant microphone permission in System Settings → Privacy & Security
- Reconnect audio device
- Click Refresh Devices in Intervu Settings
Error: Permission Denied
Windows Message:
Permission denied when accessing microphoneSolutions:
- Open Settings → Privacy → Microphone
- Enable microphone access for apps
- Enable microphone access for desktop apps
- Restart Intervu
macOS Message:
Microphone permission not grantedSolutions:
- Open System Settings → Privacy & Security → Microphone
- Enable Intervu
- If not listed, open Intervu and click the microphone button to trigger the permission prompt
- Restart Intervu
Bundled FFmpeg (Windows Only)
How It Works
Intervu bundles a custom FFmpeg build from gyan.dev on Windows:
- During
npm install,scripts/download-ffmpeg.jsruns - Downloads FFmpeg to
%LOCALAPPDATA%/intervu/ffmpeg.exe - ~214MB download
Checking Bundled FFmpeg
# Check if FFmpeg exists
dir %LOCALAPPDATA%\intervu\ffmpeg.exe
# Check file size (should be ~200MB)
# If much smaller, download failedRe-downloading FFmpeg
If the bundled FFmpeg is corrupted:
# Navigate to Intervu directory
cd %LOCALAPPDATA%\intervu
# Delete corrupted file
del ffmpeg.exe
# Reinstall Intervu or manually downloadmacOS Users
FFmpeg is not bundled on macOS. You must install it manually via Homebrew: brew install ffmpeg
Using System FFmpeg
If bundled FFmpeg doesn't work, use system FFmpeg.
Windows: Installing FFmpeg System-Wide
- Download from ffmpeg.org
- Extract to
C:\ffmpeg - Add
C:\ffmpeg\binto PATH
macOS: Installing FFmpeg
brew install ffmpegConfiguring in Intervu
- Open Settings (gear icon)
- Go to Advanced Settings
- Set FFmpeg Path to your FFmpeg executable:
- Windows:
C:\ffmpeg\bin\ffmpeg.exe - macOS (Intel):
/usr/local/bin/ffmpeg - macOS (Apple Silicon):
/opt/homebrew/bin/ffmpeg
- Windows:
- Restart Intervu
Required FFmpeg Build
Intervu requires FFmpeg with platform-specific audio support:
- Windows: Use "full" build from gyan.dev with DirectShow support (not "essentials" or "shared")
- macOS: Homebrew FFmpeg includes AVFoundation support by default
- Linux: Install
ffmpegpackage withlibavdevice
Platform Audio Support
- Windows: Standard FFmpeg builds may not include DirectShow. Use the full gyan.dev build.
- macOS: Homebrew's FFmpeg includes AVFoundation. Other builds may lack it.
FFmpeg Logs
Viewing FFmpeg Output
- Open Settings (gear icon)
- Click Open Logs Folder
- Open
app.log - Look for lines starting with
[ffmpeg]
Common Log Messages
Windows — Successful start:
[ffmpeg] Starting audio capture: dshow://Audio=CABLE Output
[ffmpeg] Audio capture startedmacOS — Successful start:
[ffmpeg] Starting audio capture: :0
[ffmpeg] Audio capture startedWindows — Device enumeration:
[ffmpeg] Listing devices...
[ffmpeg] Found device: CABLE Output
[ffmpeg] Found device: Microphone (USB)macOS — Device enumeration:
[ffmpeg] listing AVFoundation devices...
[ffmpeg] Found device: MacBook Pro Microphone
[ffmpeg] Found device: BlackHole 2chError messages:
[ffmpeg] Error: Could not open inputfile
[ffmpeg] Error: Device not found
[ffmpeg] Error: Permission deniedPerformance Issues
High CPU Usage
FFmpeg audio capture is CPU-light (~1-2%). If you see higher:
- Check audio chunk duration (increase to reduce API calls)
- Lower sample rate if possible
- Close unnecessary applications
Audio Delay
Audio should be near real-time. If delayed:
- Reduce audio chunk duration in Advanced Settings
- Check system resources
- Ensure GPU is being used for STT/LLM
Buffer Overflow
[ffmpeg] Buffer overflow, dropping packetsCauses:
- System can't process audio fast enough
- Network latency to STT endpoint
Solutions:
- Increase audio chunk duration
- Use local STT endpoint
- Close unnecessary applications
Alternative Audio Capture
If FFmpeg continues to have issues, consider:
VB-Cable Recording (Windows)
Some users record directly from VB-Cable using OBS or Audacity, then use the file with Intervu's manual mode (if available in future versions).
Hardware Loopback
Some audio interfaces support loopback recording, bypassing the need for VB-Cable.
BlackHole + Multi-Output (macOS)
On macOS, use BlackHole with a multi-output device. See macOS Setup Guide for detailed instructions.
Still Not Working?
Windows: Complete Reset
# Close Intervu
# Delete all Intervu data
rmdir /s /q %APPDATA%\intervu
rmdir /s /q %LOCALAPPDATA%\intervu
# Reinstall Intervu
# Reconfigure from scratchmacOS: Complete Reset
# Close Intervu
# Delete settings
rm -rf ~/Library/Application\ Support/intervu
# Reinstall FFmpeg if needed
brew reinstall ffmpeg
# Restart Intervu
# Reconfigure from scratchCheck Platform Version
Windows:
Intervu requires Windows 10 or later. Check your version:
winvermacOS:
Intervu requires macOS 12 (Monterey) or later. Check your version:
sw_versCheck Audio Drivers
Windows:
- Open Device Manager
- Expand Sound, video and game controllers
- Check for warning icons
- Update drivers if needed
macOS:
Audio drivers are managed by the system. If you have issues:
- Reset Core Audio:
sudo killall coreaudiod - Check for macOS updates
- Verify BlackHole is installed correctly
Next Steps
- No Audio Devices — Device enumeration issues
- macOS Troubleshooting — macOS-specific issues
- Audio Devices — Audio configuration