Why Project Health Audits Matter
Few things disrupt a studio session more than opening a project in front of a client and encountering errors like "24 Audio Files Missing" or "Plugin VST3 Not Found".
Sabes Pro includes a Project Health Inspector to scan your session dependencies before opening your DAW or delivering files to mastering.
What the Health Inspector Audits
When executing a Project Health Audit, Sabes Pro inspects:
- Audio Sample Paths: Verifies that every WAV, AIFF, and FLAC file referenced on your session timeline exists at the expected path on disk.
- Unlinked External Assets: Identifies audio files referenced from temporary desktop or downloads folders outside your primary project directory.
- Plugin Verification: Cross-checks active VST2, VST3, and CLAP plugin identifiers against installed system DLLs.
- Repository Integrity: Verifies local AES-256-GCM encrypted snapshot block consistency.
Step-by-Step Health Audit Guide
1. Select Your Project
In the Sabes Pro dashboard, select your project card.
2. Click Run Health Audit
Click Health Check in the project header. Sabes Pro scans session dependencies on disk in seconds.
3. Review Diagnostic Results
The Inspector displays clear health status indicators:
- Green (Healthy): All referenced samples exist in your project folder and plugins are verified.
- Yellow (Warning): Audio files exist, but are referenced from external folders outside your project directory.
- Red (Critical Error): Missing WAV files or uninstalled plugin dependencies detected.
4. Consolidate Unlinked Assets
If external audio files are flagged, click Consolidate Assets to copy unlinked samples directly into your project folder before archiving or shipping your session bundle.