audio-verify

Verify game audio against MogG references using identity, rate, and distortion metrics.

4|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/freeqaz/rb3 --skill audio-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audio-verify
Source: https://github.com/freeqaz/rb3/tree/main/.claude/skills/audio-verify
Command: npx skills add https://github.com/freeqaz/rb3 --skill audio-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ffmpeg, fpcalc, pycryptodome, ffprobe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Prove the audio the game plays is the SAME audio as the source song AND is played CORRECTLY (right pitch/speed, not clipped/noise/silent). Decrypts+decodes the source mogg into a ground-truth reference, captures the game output headless, then measures identity (mix-robust chroma cross-correlation + Chromaprint fingerprint), playback rate, and distortion. Use after any audio change (mixer, limiter, resampler, decode, gain) to confirm the right song still plays correctly, or to investigate an audio-fidelity report.

Core Features & Use Cases

  • Ground-truth creation by decrypting/decoding the source MogG to a reference that matches the game's mono/stereo downmix.
  • Headless capture and automated comparison across gameplay and preview sections using identity, rate, and distortion metrics.
  • Clear verdicts (MATCH / DEGRADED / WRONG-SIGNAL) to guide debugging.

Quick Start

Capture a headless gameplay clip and run the verifier to compare it against the ground-truth reference.

Frequently Asked Questions about audio-verify

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

FAQPage Schema
How do I verify captured game audio matches the source MogG file?

Verify captured game audio against a MogG reference by decrypting and decoding the source into a ground-truth track, then comparing identity, playback rate, and distortion metrics. The process outputs clear MATCH, DEGRADED, or WRONG-SIGNAL verdicts to confirm audio fidelity.

How can I check if game audio playback has correct pitch and no clipping?

Check game audio playback pitch and clipping by capturing a headless output clip and running automated comparison against a decoded reference. The analysis measures mix-robust chroma cross-correlation and Chromaprint fingerprints to detect pitch shifts, speed errors, and distortion.

Do I need ffmpeg and Chromaprint to run audio verification headlessly?

Yes, you need ffmpeg, Chromaprint, and Python 3 to run audio verification headlessly. These dependencies are required to decode the source MogG, generate the ground-truth reference, and compute the identity, rate, and distortion metrics for comparison.

What is the best way to investigate an audio fidelity report after changing a mixer or resampler?

The best way to investigate an audio fidelity report after a mixer or resampler change is to capture a headless gameplay clip and run an automated verifier. This compares the output against a ground-truth reference to identify if the signal is degraded, wrong, or matching.

Does audio verification support both gameplay and preview section captures?

Yes, audio verification supports both gameplay and preview section captures. The tool operates on native headless captures as well as web captures, computing identity and distortion metrics across both sections to ensure the correct song plays without clipping or speed alterations.