Compares your mix or master against built-in genre profiles that define typical loudness, spectral balance, dynamics, and width targets. Shows how your track deviates from the norm for a given genre.
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
| file_path | string | required | Path to audio file to analyze |
| profile_name | string | required | Genre profile name. Use list_profiles to see all available names. |
Example Output
Illustrative summary; MCP responses use structured JSON.
$ compare_to_profile master.wav --profile "pop"
Profile Comparison: master.wav vs Pop profile
Loudness: Integrated LUFS: -8.5 LUFS Target: -10.0 to -7.0 LUFS on_target True Peak: -0.8 dBTP Target: -1.0 dBTP max on_target
Frequency (dB from flat, normalized): 31 Hz: +1.4 Target: +1.0 on_target 62 Hz: +2.3 Target: +1.0 slightly_above 125 Hz: +1.2 Target: +1.0 on_target 250 Hz: +0.3 Target: 0.0 on_target 500 Hz: -0.4 Target: 0.0 on_target 1 kHz: +0.7 Target: +1.0 on_target 2 kHz: +1.1 Target: +1.0 on_target 4 kHz: +3.6 Target: +2.0 slightly_above 8 kHz: +0.1 Target: +2.0 slightly_below 16 kHz: -0.9 Target: +1.0 slightly_below
Dynamics: Crest Factor: 8.4 dB Target: 6.0-10.0 dB on_target
Stereo: Width: 0.72 Target: 0.7-1.2 (wide) on_target Mono below 100 Hz: bass correlation 0.97, stereo bass: no on_target
What the Numbers Mean
-
Ratings – Level and spectral deviations use inclusive boundaries of 1, 3, and 6 in the metric’s units. Width and correlation use 0.05, 0.15, and 0.25 because they are unitless ratios. These map to
on_target, slight, moderate, and significant above/below labels. Profile ranges are measured from their nearest boundary; unavailable measurements areunmeasurable. -
Frequency – Each of the 10 octave bands (31 Hz to 16 kHz) is compared as a normalized dB offset from flat. The response distinguishes the measured offset, the profile target, and the deviation between them; a measured +1.2 dB is not necessarily a +1.2 dB deviation.
-
Mono below – Reports the bass correlation below the profile’s mono-compatibility cutoff and whether the low end carries stereo content the genre convention says should be mono.
Example Prompts
Genre check
Compare my master to a pop profile – is it competitive?
EDM target
How does my track compare to EDM standards? Check loudness and spectrum against the EDM profile
Multiple profiles
Compare my mix against both the rock and pop profiles – it’s somewhere between the two genres
Related Tools
- list_profiles – See all available genre profile names
- compare_to_reference – Compare against a specific reference track instead of a genre average
- match_to_reference – Process a copy against a reference
- analyze_loudness – Detailed loudness breakdown
Pro tip
Profiles are guidelines, not rules. If your track is “too quiet” for EDM but it’s a moody downtempo track, that’s fine. Use profiles to confirm intentional choices and catch unintentional deviations.