Matlab Evaluate Acoustic Metrics
MathWorksOfficialCreated by MathWorks
- Skill
- Tool integration
- Science and research
- BSD-2-Clause
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured approach to using MATLAB Audio Toolbox for acoustic measurement and analysis. It guides users through selecting the correct functions for psychoacoustic metrics, speech intelligibility, noise compliance, and broadcast loudness. The skill emphasizes proper calibration techniques, standard-compliant workflows, and the correct handling of signal data to ensure accurate results, while explicitly warning against the use of nonexistent or licensed-restricted functions.
What it does
- Calculates psychoacoustic metrics like loudness, sharpness, roughness, and fluctuation strength.
- Evaluates speech quality and intelligibility using metrics such as ViSQOL, STOI, STI, and SII.
- Assesses noise compliance using NC, RC, and RNC ratings for various environments.
- Performs offline SPL measurements and broadcast loudness checks (EBU R 128).
- Provides guidance on microphone calibration and system-level calibration factors.
- Offers standard-compliant filtering and unit conversion utilities.
When to use it
- When you need to measure perceived loudness or sound quality in a research or engineering context.
- When evaluating room acoustics or HVAC noise compliance against industry standards.
- When analyzing speech intelligibility for communication systems or public address setups.
- When you need to calibrate audio recordings for accurate SPL or metric computation.
- When you need to perform broadcast loudness compliance checks.
Advantages
- Ensures adherence to international standards like ISO 532-1/2, ANSI/ASA S12.2, and IEC 60268-16.
- Prevents common errors such as incorrect function usage, argument ordering, or manual implementation of complex algorithms.
- Provides clear guidance on calibration to ensure measurement accuracy.
- Streamlines the selection of appropriate metrics based on specific application goals.
Usage examples
- “How do I calculate the loudness of a recording in sones?”
- The agent will guide you to use the acousticLoudness function, specifying the ISO 532-1 method, applying your calibration factor, and selecting the appropriate sound field.
- “Is my office HVAC noise compliant?”
- The agent will recommend using the roomCriteria function to obtain an RC rating, explaining how to interpret the output and verify the measurement conditions.
- “How can I measure the speech quality of a processed audio file?”
- The agent will instruct you to use the visqol function with the 'speech' mode, ensuring the processed signal is passed as the first argument.
- “How do I calibrate my microphone for SPL measurements?”
- The agent will explain how to use calibrateMicrophone with a 1 kHz tone recording and a known SPL reference to compute the correct calibration factor.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/matlab/matlab-evaluate-acoustic-metrics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip matlab-evaluate-acoustic-metrics.zip -d .agents/skills
Documentation by MathWorks
Evaluate Acoustic Metrics
Select the correct Audio Toolbox function for acoustic measurement, apply proper calibration, and choose appropriate standards — instead of reimplementing algorithms or calling nonexistent functions.
When to Use
Computing psychoacoustic metrics (loudness, sharpness, roughness, fluctuation)
Evaluating speech quality or intelligibility (ViSQOL, STOI, STI, SII)
Assessing noise compliance (NC rating, RC rating, RNC, SIL)
Measuring SPL from recordings (offline, calibrated)
Computing broadcast loudness (EBU R 128 / LUFS)
Measuring reverberation time (RT60) from impulse responses
Detecting tonal content (tone-to-noise ratio, prominence ratio)
Converting microphone sensitivity to CalibrationFactor
User mentions PESQ or POLQA (redirect to correct alternatives)
When NOT to Use
Real-time streaming audio processing loops — use
matlab-process-streaming-audioAudio device I/O, recording, or live
calibrateMicrophone— usematlab-play-record-audioAudio plugin authoring (VST/AU) — use
matlab-write-audio-pluginGeneral filter design unrelated to measurement — use
matlab-design-digital-filterSpatial audio / HRTF / SOFA processing
Workflow
Follow this decision tree to route the user's goal to the right function:
1. Identify the measurement goal
| Goal | Category | Go to |
|---|---|---|
| "How loud is it?" (perceived) | Psychoacoustic | → Psychoacoustic Metrics |
| "Does it comply with broadcast loudness?" | Broadcast | → Broadcast Loudness |
| "Is the noise level acceptable for this space?" | Noise compliance | → Noise Compliance |
| "Can people understand speech in this room?" | Speech intelligibility | → STI/SII Measurement |
| "How good does processed speech sound?" | Speech quality | → Speech Quality |
| "What's the SPL?" | Level measurement | → SPL Measurement |
| "What's the reverberation time?" | Room acoustics | → RT60 |
| "Is there a tonal component?" | Tonality | → Tonality |
2. Ask before computing
Before writing code, confirm these with the user:
Calibration: Do they have a CalibrationFactor? Did they calibrate with
calibrateMicrophone? (See Calibration section)Standard: Which standard or method applies? (ISO 532-1 vs 532-2, NC vs RC vs RNC)
Sound field: Free field or diffuse field recording?
Application context: What space type? What's the concern? (Drives NC vs RC vs RNC selection)
3. Select function and apply
Use the Key Functions table and the category-specific patterns below.
Functions That Do NOT Exist
| Function | Status | Use Instead |
|---|---|---|
pesq | Does NOT exist (proprietary ITU-T P.862 license) | visqol(degraded, reference, fs, Mode="speech") |
polqa | Does NOT exist (proprietary ITU-T P.863 license) | visqol(degraded, reference, fs) |
Never suggest pesq or polqa. They are not in Audio Toolbox and cannot be added due to licensing.
Key Functions
| Function | Purpose | Standard | Available From |
|---|---|---|---|
acousticLoudness | Perceived loudness (sones) | ISO 532-1/2 | R2020a |
acousticSharpness | Perceived sharpness (acum) | DIN 45692 | R2020a |
acousticRoughness | Perceived roughness (asper) | — | R2021a |
acousticFluctuation | Fluctuation strength (vacil) | — | R2020b |
integratedLoudness | Broadcast loudness (LUFS) | EBU R 128 / ITU-R BS.1770 | R2016b |
loudnessMeter | Streaming broadcast loudness meter | EBU R 128 / ITU-R BS.1770 | R2018a |
visqol | Full-reference audio quality (MOS) | — | R2024a |
stoi | Short-time objective intelligibility | — | R2024a |
mnru | Modulated noise reference unit | ITU-T P.810 | R2024a |
dBov | Power level relative to overload (dB) | ITU-T G.100.1 | R2024a |
speechTransmissionIndex | STI from IR or test signals | IEC 60268-16 | R2026a |
speechIntelligibilityIndex | SII from IR, test signals, or levels | ANSI/ASA S3.5-1997 | R2026b |
stipaExcitation | Generate STI/STIPA test signals | IEC 60268-16 | R2026a |
siiExcitation | Generate SII test signals | ANSI/ASA S3.5-1997 | R2026b |
noiseCriteria | NC rating + SIL + spectrum imbalance + rattle risk | ANSI/ASA S12.2 | R2026b |
roomNoiseCriteria | RNC rating (detects surging/fluctuations) | ANSI/ASA S12.2 | R2026b |
roomCriteria | RC Mark II rating (HVAC systems) | ANSI/ASA S12.2 | R2026b |
noiseCriteriaCurves | Look up NC curve values | ANSI/ASA S12.2 | R2026b |
noiseCriteriaRecommendations | Recommended NC levels by room type | ANSI/ASA S12.2 | R2026b |
speechInterferenceLevel | SIL from recording | ANSI/ASA S12.2 | R2026b |
rt60 | Reverberation time from impulse response | ISO 3382-1/2 | R2025a |
acousticToneToNoiseRatio | Detect/quantify tones | ECMA-418-1 | R2023b |
acousticProminenceRatio | Tonality via critical band comparison | ECMA-418-1 | R2023b |
splMeter | SPL measurement (time-weighted, per-band) | IEC 61672 | R2018a |
calibrateMicrophone | Compute calibration factor from known tone | — | R2018b |
weightingFilter | A/C/Z/K frequency weighting | IEC 61672-1 | R2016b |
octaveFilter | Single octave-band filter | ANSI S1.11-2004 | R2017b |
octaveFilterBank | Multi-band octave filtering | ANSI S1.11-2004 | R2019a |
See references/function-arguments.md for complete argument lists, defaults, and valid values for each function — consult when constructing calls with non-default parameters.
Calibration
CalibrationFactor from microphone sensitivity
Convert dB sensitivity (dBV/Pa) to the linear CalibrationFactor:
sensitivity_dBV = -26; % Example: -26 dBV/Pa microphone
calibrationFactor = 1 / 10^(sensitivity_dBV/20);The CalibrationFactor is the 3rd positional argument for acousticLoudness, acousticSharpness, acousticRoughness, and acousticFluctuation (default: sqrt(8)). For noise compliance functions, pass it as a name-value: CalibrationFactor=value.
System-level calibration advice
Always ask the user about their signal chain. If the recording path includes a preamp, audio interface, or ADC with unknown gain, the mic sensitivity spec alone is insufficient. Recommend:
Play a 1 kHz tone through the system and record it through the full signal chain (mic → preamp → ADC → WAV). Use a pistonphone for a known 94 dB reference, or place a physical SPL meter next to the microphone to get an SPL reading.
Compute the system calibration factor:
calibrationFactor = calibrateMicrophone(calRecording, fs, SPLreading, FrequencyWeighting="Z-weighting")Pass that factor to the measurement function
calibrateMicrophone expects a 1 kHz tone recording as input. The SPLreading argument is the known SPL in dB (e.g., 94 from a pistonphone, or the value shown on a physical SPL meter).
Cross-reference: for the physical recording workflow with calibrateMicrophone, see the matlab-play-record-audio skill.
Patterns
Psychoacoustic Metrics
[audioIn, fs] = audioread("recording.wav");
calFactor = 1 / 10^(-26/20);
loudness = acousticLoudness(audioIn, fs, calFactor, ...
Method="ISO 532-1", SoundField="diffuse", TimeVarying=true);
sharpness = acousticSharpness(audioIn, fs, calFactor, ...
SoundField="diffuse", TimeVarying=true);
roughness = acousticRoughness(audioIn, fs, calFactor, SoundField="diffuse");
fluctuation = acousticFluctuation(audioIn, fs, calFactor, SoundField="diffuse");Return types: acousticLoudness returns a scalar (sones) for stationary analysis. With TimeVarying=true, it returns a column vector (time-varying loudness in sones). The second output (specificLoudness) is a matrix (time x critical bands). It does NOT return a struct or timetable.
Ask the user:
ISO 532-1 (Zwicker, stationary/time-varying) or ISO 532-2 (Moore-Glasberg)?
Free-field or diffuse-field recording?
Time-varying analysis needed?
See references/psychoacoustic-metrics.md for method selection guidance (ISO 532-1 vs 532-2), interpretation tables (sone values, sharpness/roughness/fluctuation scales), tonality metric selection, and combined sound quality assessment workflows.
Unit Conversions
Use built-in functions — do NOT reimplement conversion formulas manually:
| Conversion | Function | Method selection |
|---|---|---|
| phon → sone | phon2sone(phon, standard) | "ISO 532-1" (default), "ISO 532-2" |
| sone → phon | sone2phon(sone, standard) | "ISO 532-1" (default), "ISO 532-2" |
| Hz → ERB | hz2erb(freq) | Single formula (no variants) |
| ERB → Hz | erb2hz(erb) | Single formula (no variants) |
| Hz → bark | hz2bark(freq) | Single formula (no variants) |
| bark → Hz | bark2hz(bark) | Single formula (no variants) |
| Hz → mel | hz2mel(freq, MelStyle=s) | "oshaughnessy" (default), "slaney" |
| mel → Hz | mel2hz(mel, MelStyle=s) | "oshaughnessy" (default), "slaney" |
When the user specifies a standard (e.g., "ISO 532-2"), pass it as the second positional argument for phon2sone/sone2phon. For hz2mel/mel2hz, use the MelStyle name-value pair.
Noise Compliance
Choose the function based on the application:
| Situation | Function | Why |
|---|---|---|
| General background noise rating | noiseCriteria | Standard NC curves (ANSI/ASA S12.2) |
| HVAC system noise specifically | roomCriteria | RC Mark II designed for HVAC evaluation |
| Noise with audible surging/fluctuation | roomNoiseCriteria | RNC penalizes time-varying noise (requires ≥15 s recording) |
| Quick speech interference check | speechInterferenceLevel | Direct SIL value |
| Need recommended levels for room type | noiseCriteriaRecommendations | Lookup table by room use |
[audioIn, fs] = audioread("office_noise.wav");
[NC, SIL, specImbalance, rattleRisk] = noiseCriteria(audioIn, fs, ...
CalibrationFactor=2.3);
[RC, LMF, QAI, rattleRisk] = roomCriteria(audioIn, fs, ...
CalibrationFactor=2.3);
SIL = speechInterferenceLevel(audioIn, fs, CalibrationFactor=2.3);
rec = noiseCriteriaRecommendations("NC", Occupancy="all");Return types:
NCis a string (e.g.,"NC-35"or"NC-56 (1000 Hz)"if a band exceeds)RCis a string (e.g.,"RC-32(N)"— the letter indicates spectrum quality: N/R/H/RV)SILandLMFare double scalars (dB)QAIis a double scalar (dB; 0 = ideal neutral)specImbalanceandrattleRiskare structs with.Summary(string) and.Details(table) — access.Summaryfor display. Exception:specImbalancedegrades to acharscalar (not a struct) when NC exceeds the curve range (e.g., "Above NC-70") or falls below NC-15. Guard withisstruct(specImbalance)before dot-indexing.noiseCriteriaRecommendationsrequires a criteria name argument:"NC","RNC", or"RC"
Ask the user:
What type of space? (office, classroom, hospital, concert hall)
Is the noise source HVAC? → prefer
roomCriteriaIs the noise steady or fluctuating? → if fluctuating, use
roomNoiseCriteria
See references/noise-compliance.md for detailed output interpretation and selection guidance.
Speech Quality
[degraded, fs] = audioread("processed_speech.wav");
[reference, ~] = audioread("reference_speech.wav");
mosScore = visqol(degraded, reference, fs, Mode="speech");
intelligibility = stoi(degraded, reference, fs);Critical: stoi and visqol argument order is (processed, reference, fs) — processed/degraded signal FIRST.
visqol modes: "speech" for narrowband/wideband speech (outputs 1-5 MOS), "audio" (default) for general audio.
STI/SII Measurement
Two methods are available for both speechTransmissionIndex and speechIntelligibilityIndex:
IR-based method (simpler — no alignment needed):
[ir, fs] = audioread("room_impulse_response.wav");
sti = speechTransmissionIndex(ir, fs);
sii = speechIntelligibilityIndex(ir, fs);Direct method (from test signals transmitted through the system):
fs = 48000;
reference = stipaExcitation(fs, Duration=15);
% Transmit reference through system, record as 'processed'
[processed, ~] = audioread("received_stipa.wav");
% IMPORTANT: Align signals before computing (see Signal Alignment)
processed = alignsignals(processed, reference);
sti = speechTransmissionIndex(processed, reference, fs);Ask the user:
Do they have an impulse response? → use IR method (simpler, no alignment needed)
Measuring live? → generate test signal, transmit, record, align, compute
STI or SII? STI for room/PA systems (IEC 60268-16); SII for hearing/communication (ANSI S3.5)
See references/sti-measurement.md for STI NV arguments, post-processing adjustment workflow (Annex M), test signal generation, and result interpretation. See references/sii-measurement.md for SII standard clause selection (5.1-5.3), BandImportanceFunction guidance, measurement positioning, and result interpretation.
SPL Measurement (Offline)
[audioIn, fs] = audioread("recording.wav");
spl = splMeter(SampleRate=fs, ...
Bandwidth="Full band", ...
FrequencyWeighting="A-weighting", ...
TimeWeighting="fast", ...
CalibrationFactor=2.3);
[Lt, Leq, Lpeak, Lmax] = spl(audioIn);
% For a single overall value, read the final row
fprintf("Leq: %.1f dB(A)\n", Leq(end));Valid Bandwidth values: "Full band" (overall level), "1 octave", "2/3 octave", "1/3 octave". There is no "broadband" option — use "Full band" for a single overall SPL value.
Output arity: All outputs (Lt, Leq, Lpeak, Lmax) have one row per input sample. For a 12-second file at 44.1 kHz, that is 539,648 rows. Never fprintf or disp the full output — it will hang. Instead:
Single overall value: read
Leq(end)(the final accumulated value)Time-interval readings: downsample to interval boundaries:
Leq(round(fs*T):round(fs*T):end, :)whereTis the desired interval in seconds
TimeInterval controls the integration window for Leq computation but does NOT reduce the number of output rows.
Do not manually compute 20*log10(rms(audioIn)/20e-6) — splMeter handles calibration, weighting, and time integration correctly per IEC 61672.
Multi-band (octave-band) SPL: Use splMeter with Bandwidth="1 octave" — do NOT use octaveFilterBank + manual dB conversion. Key properties for octave-band SPL:
[audioIn, fs] = audioread("recording.wav");
spl = splMeter(SampleRate=fs, ...
Bandwidth="1 octave", ...
FrequencyWeighting="Z-weighting", ...
TimeWeighting="fast", ...
FrequencyRange=[15 8000], ...
OctaveFilterOrder=8, ...
CalibrationFactor=2.3);
[Lt, Leq, Lpeak, Lmax] = spl(audioIn);
cf = getCenterFrequencies(spl);Critical gotchas for octave-band splMeter:
Property name is
OctaveFilterOrder(notFilterOrder).FilterOrderdoes not exist onsplMeter.FrequencyRangecompares against true center frequencies (fc = 1000 × 10^(3b/10)per IEC 61260), not nominal values. A band is included only if its true center falls within[lower, upper]. Bands below 1 kHz have true centers slightly above nominal (e.g., "63 Hz" = 63.10); bands above 1 kHz have true centers below nominal (e.g., "2 kHz" = 1995.26, "8 kHz" = 7943.28). Usefloor(true_center)for lower bounds andceil(true_center)for upper bounds. Common case "16 Hz to 8 kHz": use[15 8000]— the 16 Hz true center is 15.85 (so 15 ≤ 15.85 includes it) and 8 kHz true center is 7943 (so 8000 ≥ 7943 includes it). Do NOT use[16 8000]— this drops the 16 Hz band.Output is per-sample (see Output arity note above). Never print the full output. For time-interval readings, downsample:
Lt100ms = Lt(round(fs*0.1):round(fs*0.1):end, :);
See references/spl-measurement.md for weighting selection guidance (A/C/Z and fast/slow), SPL interpretation tables, occupational exposure limits, splMeter vs poctave equivalency, and common measurement scenarios.
Broadcast Loudness (EBU R 128)
[audioIn, fs] = audioread("broadcast_content.wav");
[loudness, loudnessRange] = integratedLoudness(audioIn, fs);
% Check compliance: target is -23 LUFS +/- 1 LU
isCompliant = abs(loudness - (-23)) <= 1;Use integratedLoudness for offline compliance checks. Use loudnessMeter for streaming/real-time monitoring (see matlab-process-streaming-audio).
RT60
[ir, fs] = audioread("room_ir.wav");
rtsummary = rt60(ir, fs, Bandwidth="1 octave");Ask the user:
What is the room type? (drives the target RT60)
Do they have an IR, or do they need to measure one?
T30 (standard) vs T20 (when noise floor limits dynamic range)?
See references/rt60-measurement.md for target RT60 values by space type, T20/T30/EDT interpretation, frequency-dependent analysis, and relationship to STI.
Tonality
[audioIn, fs] = audioread("machine_noise.wav");
[tnr, tnrFreq, isProminent] = acousticToneToNoiseRatio(audioIn, fs);
[pr, prFreq, isProminent] = acousticProminenceRatio(audioIn, fs);All outputs are empty (0×1) when no tonal components are detected. Check isempty(tnr) before indexing.
Standards-Compliant Filters (Custom Preprocessing)
The metric functions above perform standards-compliant filtering internally. Use standalone filter objects only for custom measurement workflows where no single metric function applies AND you do not need SPL output:
% A-weighting filter
wf = weightingFilter("A-weighting", fs);
weightedSignal = wf(audioIn);
% Octave-band filter bank (for waveform-level band decomposition only)
ofb = octaveFilterBank("1 octave", fs, ...
FrequencyRange=[31.5 16000], FilterOrder=8);
bandSignals = ofb(audioIn);If you need octave-band SPL levels, use splMeter with Bandwidth="1 octave" instead of octaveFilterBank + manual dB conversion. See the Multi-band SPL section above.
Signal Alignment
| Function | Internal alignment? | Action |
|---|---|---|
visqol | Yes | No action needed |
stoi | No | Align before calling |
speechTransmissionIndex | No | Align for direct method; IR method avoids issue |
speechIntelligibilityIndex | No | Align for direct method; IR method avoids issue |
For the direct (processed, reference, fs) method, always align signals:
processed = alignsignals(processed, reference);SII is more sensitive to misalignment than STI. At 50 ms delay: SII error ~0.016, STI negligible. At 200 ms: SII ~0.036, STI ~0.017. The IR-based (ir, fs) method avoids alignment issues entirely.
Common Mistakes
| Mistake | Why it fails | Correct approach |
|---|---|---|
Call pesq(reference, degraded, fs) | Function does not exist | visqol(degraded, reference, fs, Mode="speech") |
stoi(reference, processed, fs) | Wrong argument order | stoi(processed, reference, fs) — processed FIRST |
acousticFluctuationStrength(...) | Wrong function name | acousticFluctuation(audioIn, fs, calFactor) |
| Implement NC from scratch with hardcoded curves | Misses SIL, spectrum imbalance, rattle risk | noiseCriteria(audioIn, fs, CalibrationFactor=cf) |
20*log10(rms(x)/20e-6) for SPL | No weighting, no time integration, no calibration | splMeter with appropriate settings |
| Implement STI algorithm manually | ~100 lines, error-prone, misses NV options | speechTransmissionIndex(ir, fs) |
| Divide signal by calibration factor manually | Incorrect; factor is a multiplier, not a divisor | Pass as positional arg or CalibrationFactor=value |
| Skip alignment for direct STI/SII | Silent accuracy degradation | alignsignals(processed, reference) before calling |
Use acousticLoudness for broadcast loudness | Wrong standard (ISO 532 = sones, not LUFS) | integratedLoudness for EBU R 128 compliance |
string(rattleRisk) or fprintf("%s", specImbalance) | These are structs, not strings | Access .Summary field: rattleRisk.Summary |
specImbalance.Summary when NC is out of curve range | specImbalance degrades to char (not struct) when "Above NC-70" or below NC-15 | Guard: if isstruct(specImbalance), disp(specImbalance.Summary); end |
roomNoiseCriteria on recordings shorter than 15 s | ANSI/ASA S12.2-2019 requires ≥150 Lt samples at 100 ms intervals | Ensure recording is at least 15 seconds; use noiseCriteria for shorter clips |
round(NC) or arithmetic on NC/RC output | NC and RC are strings, not numbers | Use directly: fprintf("%s\n", NC) |
noiseCriteriaRecommendations() with no args | First argument (criteria name) is required | noiseCriteriaRecommendations("NC") |
loudness.OverallLoudness after acousticLoudness | Returns a scalar or vector, not a struct | Use directly: fprintf("%.1f sones\n", loudness) |
splMeter(..., FilterOrder=8) | Property does not exist on splMeter | Use OctaveFilterOrder=8 |
splMeter(..., FrequencyRange=[16 8000]) for 16 Hz–8 kHz | Drops 16 Hz band (true center is 15.85 Hz, which is below 16) | Use FrequencyRange=[15 8000] — use floor(true_center) for lower bound |
octaveFilterBank + 20*log10(rms(band)/pRef) for SPL | Manual, no time weighting, no calibration integration | Use splMeter with Bandwidth="1 octave" |
Treating splMeter output as a single value | All outputs have one row per input sample (e.g., 539k rows for 12s at 44.1 kHz) | Use Leq(end) for a single value, or downsample to interval boundaries |
Conventions
Always ask about the user's measurement goal before selecting a function
Always ask about calibration — recommend
calibrateMicrophonefor system-level accuracyDefault to
SoundField="free"for anechoic/outdoor,"diffuse"for reverberant roomsDefault to
Method="ISO 532-1"for loudness (Zwicker method, most common)Use IR-based methods for STI/SII when an impulse response is available (avoids alignment)
Pass
CalibrationFactorexplicitly rather than pre-scaling the signalFor noise compliance, prefer
roomCriteriafor HVAC andnoiseCriteriafor general background noise
Copyright 2026 The MathWorks, Inc.
Files
- ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
- LICENSELicence file added by AutoGineer1.4 KiB
- SKILL.md22.7 KiB
- manifest.yaml444 B
- references/function-arguments.md7.3 KiB
- references/noise-compliance.md16.4 KiB
- references/psychoacoustic-metrics.md16.0 KiB
- references/rt60-measurement.md14.4 KiB
- references/sii-measurement.md16.9 KiB
- references/spl-measurement.md12.5 KiB
- references/sti-measurement.md14.0 KiB
references/psychoacoustic-metrics.md
Psychoacoustic Metrics
Guidance for selecting and interpreting acousticLoudness, acousticSharpness, acousticRoughness, acousticFluctuation, acousticToneToNoiseRatio, and acousticProminenceRatio.
When to Use Psychoacoustic Metrics
Psychoacoustic metrics quantify perceived sound characteristics that dB SPL alone cannot capture. Two sounds at the same dB level can differ dramatically in perceived loudness, annoyance, and character depending on their spectral and temporal content.
| Metric | Measures | Unit | Typical Application |
|---|---|---|---|
acousticLoudness | Perceived loudness | sone | Product sound quality, noise annoyance, automotive NVH, appliance noise |
acousticSharpness | High-frequency dominance / "harshness" | acum | Alert/alarm design, product sound quality, hearing aid tuning |
acousticRoughness | Rapid amplitude modulation (15–300 Hz) | asper | Engine/motor sound quality, bearing fault detection, "harshness" |
acousticFluctuation | Slow amplitude modulation (up to ~20 Hz) | vacil | HVAC surging detection, engine idle quality, periodic variation |
acousticToneToNoiseRatio | Tonal prominence above broadband noise | dB | Product noise regulation (ECMA-418-1), transformer hum, fan tonal noise |
acousticProminenceRatio | Tonal prominence via critical band comparison | dB | IT equipment noise (ECMA-418-1), regulatory compliance |
Intake Questions
1. What is the user's concern or goal?
| User Says | Metric(s) to Use |
|---|---|
| "How loud does this sound?" / "Is it too loud?" | acousticLoudness |
| "It sounds harsh / shrill / piercing" | acousticSharpness |
| "It sounds rough / buzzy / grating" | acousticRoughness |
| "It throbs / surges / pulsates" | acousticFluctuation |
| "There's a whine / hum / tone" | acousticToneToNoiseRatio or acousticProminenceRatio |
| "Overall sound quality assessment" | All four (loudness + sharpness + roughness + fluctuation) |
| "Compare two products" | Run same metrics on both; compare values |
| "Does this meet noise regulations?" | Check which standard applies — may need tonality metrics for penalty assessment |
2. Calibration
All psychoacoustic metrics require calibrated input for absolute values. Ask:
Do they have a CalibrationFactor? (3rd positional argument, default
sqrt(8))If they only need relative comparison between sounds (not absolute sones/acum), calibration is less critical — but the same factor must be used for both
3. Sound field
Free field (
"free"): Outdoor, anechoic chamber, or close-mic recordings without room reflectionsDiffuse field (
"diffuse"): Reverberant rooms, typical indoor recordingsEarphones (
"earphones"): Headphone playback — requiresEarphoneResponseforacousticLoudnessEardrum (
"eardrum"): Signal already represents the pressure at the eardrum (e.g., from a probe mic)
Default is "free". Using the wrong sound field introduces ~2–5 phon error in loudness.
4. Time-varying analysis?
Stationary sounds (fans, HVAC steady-state, continuous tones): Single-value output is appropriate
Transient or varying sounds (engine run-up, door slam, tool operation): Time-varying analysis reveals how perception changes over time
Only acousticLoudness with Method="ISO 532-1" supports TimeVarying=true. ISO 532-2 is stationary only. acousticSharpness also supports TimeVarying=true.
acousticLoudness — Method Selection
ISO 532-1 (Zwicker) vs ISO 532-2 (Moore-Glasberg)
| Aspect | ISO 532-1 | ISO 532-2 |
|---|---|---|
| Basis | Critical-band rate (Bark scale) | Auditory filter shapes (ERB scale) |
| Time-varying | Yes (TimeVarying=true) | No (stationary only) |
| Low-frequency precision | Less precise below ~200 Hz | Improved low-frequency model |
| Low-level accuracy (< 40 phon) | Good | Better |
| Tonal / line-spectral sounds | Adequate | More accurate (sharper auditory filters) |
| Binaural (different signal at each ear) | Not supported | Supported |
| Industry adoption | Most widely used; default for most standards | Growing adoption; required by some automotive OEMs |
| Established since | 1975 (revised 2017) | 2017 |
When to Use Each
| Scenario | Recommended Method |
|---|---|
| Time-varying analysis (engine run-up, transients) | ISO 532-1 (only option) |
| General product sound quality | ISO 532-1 (industry standard, most comparable to existing data) |
| Automotive NVH (unless OEM specifies otherwise) | ISO 532-1 |
| Accurate loudness at low levels (< 40 phon) | ISO 532-2 |
| Tonal sounds where spectral detail matters | ISO 532-2 |
| Regulatory compliance that specifies ISO 532-2 | ISO 532-2 |
| Comparing to legacy measurements | ISO 532-1 (historical data uses Zwicker) |
| Unsure / no specific requirement | ISO 532-1 (default, more widely understood) |
Key Differences in Practice
At moderate-to-high levels (> 40 phon), both methods give similar results (within ~5%)
Below 40 phon, ISO 532-2 gives more accurate results because its auditory filter model better represents low-level hearing
For narrowband/tonal sounds, ISO 532-2 can give different (typically more accurate) specific loudness patterns because ERB filters have better frequency resolution than Bark bands
Time-varying loudness (ISO 532-1 only) uses a 2 ms temporal resolution with attack/decay modeling — essential for impulsive or transient sounds
Interpreting Loudness Values
| Loudness (sone) | Subjective Impression | Example |
|---|---|---|
| 1 | Reference (40 phon = 1 sone) | Quiet library |
| 2 | Twice as loud as 1 sone | Quiet office |
| 4 | Twice as loud as 2 sone | Normal conversation at 1 m |
| 8 | Twice as loud as 4 sone | Busy restaurant |
| 16 | Twice as loud as 8 sone | Vacuum cleaner at 1 m |
| 32+ | Very loud | Power tools, loud music |
Key property: Doubling of sone value = doubling of perceived loudness. This is the primary advantage over dB: a +10 dB increase roughly doubles loudness, but this depends on frequency and level. Sones capture the actual perceptual doubling.
Specific Loudness
The second output of acousticLoudness is specific loudness — loudness distributed across critical bands. Use it to identify which frequencies contribute most to the overall loudness:
Peaks in specific loudness → dominant frequency regions of the sound
Comparing specific loudness patterns between products shows where one sounds louder
Feed specific loudness into
acousticSharpness,acousticFluctuation, oracousticRoughnessfor consistent analysis (avoids recomputation). This is only valid when loudness uses ISO 532-1 (the default) — sharpness, fluctuation, and roughness are defined on the Bark-band specific loudness of ISO 532-1, not the ERB-band output of ISO 532-2.
acousticSharpness — Guidance
What Sharpness Measures
Sharpness quantifies the proportion of high-frequency energy in the specific loudness pattern. A sound with more energy above ~3 kHz relative to lower frequencies will have higher sharpness.
| Sharpness (acum) | Subjective Impression | Example |
|---|---|---|
| 0.5–1.0 | Dull, warm | Low-frequency fan hum |
| 1.0–1.5 | Neutral | Broadband noise |
| 1.5–2.5 | Sharp, bright | High-speed drill, alarm |
| > 2.5 | Very sharp, piercing | Metal-on-metal, high-pitch alert |
Weighting Methods
DIN 45692 (default): Standard method, most common
Aures: Accounts for loudness level — sharpness decreases at low levels (more perceptually accurate)
von Bismarck: Original empirical method, legacy use
Use DIN 45692 unless the user has a specific reason for another method.
When Sharpness Matters
Alert/alarm design: Sharpness > 1.5 acum helps signals cut through background noise, but > 3.0 can be painful
Product sound quality: Lower sharpness is generally preferred (sounds "warmer" and less fatiguing)
Hearing aid fitting: Excessive sharpness indicates too much HF gain
Vehicle interior: Sharpness contributes to perceived quality — premium vehicles target low sharpness
acousticRoughness — Guidance
What Roughness Measures
Roughness quantifies perception of rapid amplitude modulation in the 15–300 Hz range (with peak sensitivity around 70 Hz). It corresponds to a "buzzing" or "grating" quality.
| Roughness (asper) | Subjective Impression | Example |
|---|---|---|
| < 0.2 | Smooth | Pure tone, steady broadband noise |
| 0.2–0.5 | Slightly rough | Some electric motors |
| 0.5–1.0 | Moderately rough | Diesel engine idle, small power tools |
| > 1.0 | Very rough | Unbalanced machinery, bearing defects |
When Roughness Matters
Engine/motor sound quality: Roughness is a primary contributor to "harshness" perception in automotive NVH
Bearing fault detection: Developing faults create amplitude modulation at characteristic frequencies → increased roughness
Electric vehicle noise: Without engine masking, EV motor roughness becomes audible and annoying
Product quality comparison: Lower roughness generally correlates with higher perceived quality
Modulation Frequency Output
The third output fMod reports the detected modulation frequency. This is diagnostically valuable:
fMod near rotational frequencies → imbalance or eccentricity
fMod at gear mesh frequencies → gear noise
fMod at blade-pass frequency → fan/compressor
acousticFluctuation — Guidance
What Fluctuation Strength Measures
Fluctuation strength quantifies perception of slow amplitude modulation below ~20 Hz (peak sensitivity at 4 Hz). It corresponds to a "throbbing" or "wah-wah" quality.
| Fluctuation (vacil) | Subjective Impression | Example |
|---|---|---|
| < 0.1 | Steady | Constant fan noise |
| 0.1–0.3 | Slight pulsation | Some HVAC systems |
| 0.3–0.5 | Noticeable throbbing | Engine idle, rotating equipment |
| > 0.5 | Strong pulsation | Helicopter rotor, severe HVAC surging |
Relationship to RNC
Fluctuation strength and Room Noise Criteria (RNC) address similar phenomena from different perspectives:
acousticFluctuationgives a psychoacoustic metric (vacil) for any soundroomNoiseCriteriagives a noise compliance rating that penalizes fluctuation in the context of background noise
If acousticFluctuation is elevated AND the noise is background HVAC, suggest also running roomNoiseCriteria for a compliance-oriented assessment.
When Fluctuation Matters
HVAC complaints: "The noise seems to come and go" → measure fluctuation strength. If > 0.1 vacil, fluctuation is likely the annoyance driver (even if overall level is low).
Engine idle quality: Low fluctuation is a target for premium vehicles
Periodic noise sources: Anything with a repetition rate of 0.5–20 Hz will register as fluctuation
Tonality Metrics — Guidance
acousticToneToNoiseRatio vs acousticProminenceRatio
| Aspect | Tone-to-Noise Ratio (TNR) | Prominence Ratio (PR) |
|---|---|---|
| Standard | ECMA-418-1 | ECMA-418-1 |
| Method | Compares tone power to noise in critical bandwidth | Compares critical band power to adjacent bands |
| Best for | Detecting discrete tones in broadband noise | Detecting tonal prominence in shaped spectra |
| Regulation | Common in EU product noise directives | Common for IT equipment |
| Penalty threshold | TNR > 6 dB → tone is prominent | PR > 9 dB → tone is prominent |
When to Use Tonality Metrics
Product noise certification: Many regulations (EU Machinery Directive, outdoor equipment) apply a tonal penalty (+5 dB or K-factor) when prominent tones are detected
Transformer/power supply hum: Detect and quantify 50/60 Hz or harmonic tones
Fan noise: Blade-pass frequency tones often trigger tonality penalties
Quality control: Detect emerging tonal defects in manufacturing (new bearings shouldn't have tones)
Interpreting Results
Both functions return empty arrays when no tonal components are detected — always check isempty(tnr) before indexing.
The isProminent output directly answers the regulatory question: does this tone exceed the prominence threshold?
TNR > 6 dB: Prominent per ECMA-418-1 — tonal penalty applies
PR > 9 dB: Prominent per ECMA-418-1 — tonal penalty applies
Multiple tones detected: Each is reported separately; the most prominent drives the penalty
Frequency Information
The tnrFreq / prFreq outputs identify where each detected tone sits. Use this to:
Trace the tone back to a physical source (e.g., 120 Hz = 2× mains frequency → power supply)
Target mitigation (notch filter, vibration isolation at that frequency)
Monitor whether a tone shifts frequency under load (indicates speed-dependent source)
Sound Quality Assessment — Combined Metrics
For comprehensive product sound quality evaluation, compute all four metrics and interpret together:
| Metric | Target Direction | Rationale |
|---|---|---|
| Loudness | Lower | Quieter products preferred (unless loudness signals power/performance) |
| Sharpness | Lower | Less fatiguing, perceived as higher quality |
| Roughness | Lower | Smoother operation, fewer vibration issues |
| Fluctuation | Lower | Steadier, more predictable |
Exception: Some products intentionally target specific psychoacoustic signatures (e.g., sports car exhaust aims for moderate roughness to convey "power"). In these cases, the target is a specific profile, not simply "minimize all."
Psychoacoustic Annoyance (PA)
Zwicker's psychoacoustic annoyance combines loudness, sharpness, fluctuation, and roughness into a single scalar [1]:
PA = N5 * (1 + sqrt(wS^2 + wFR^2))where:
N5— percentile loudness in sones (level exceeded 5% of the time)wS = (S - 1.75) * 0.25 * log10(N5 + 10)for S > 1.75 acum; otherwisewS = 0wFR = (2.18 / N5^0.4) * (0.4*F + 0.6*R)where F is fluctuation (vacil), R is roughness (asper)
Extracting N5: Call acousticLoudness with TimeVarying=true. The third output (perc) contains percentile loudness; with default Percentiles=[0,5], perc(2) is N5.
% Stationary loudness for sharpness
[~, specStationary] = acousticLoudness(x, fs, calib);
S = acousticSharpness(specStationary);
% Time-varying loudness for N5, fluctuation, roughness
[~, specHD, perc] = acousticLoudness(x, fs, calib, TimeVarying=true, TimeResolution="high");
spec = specHD(1:4:end,:,:); % standard resolution for fluctuation
N5 = perc(2);
vacil = acousticFluctuation(spec);
asper = acousticRoughness(specHD); % roughness needs high resolution
F = mean(vacil(:,1));
R = mean(asper(:,1));
wS = 0;
if S > 1.75
wS = (S - 1.75) * 0.25 * log10(N5 + 10);
end
wFR = (2.18 / N5^0.4) * (0.4*F + 0.6*R);
PA = N5 * (1 + sqrt(wS^2 + wFR^2));PAT (annoyance with tonality): For tonal noise (engines, transformers), More [2] extended the formula to include tonality:
PAT = N5 * (1 + sqrt(γ0 + γ1*wS^2 + γ2*wFR^2 + γ3*wT^2))where wT^2 = (1 - exp(γ4*N5))^2 * (1 - exp(γ5*K5))^2, K5 is the 5th percentile prominence ratio, and constants are γ0 = −0.16, γ1 = 11.48, γ2 = 0.84, γ3 = 1.25, γ4 = 0.29, γ5 = 5.49. If no prominent tone is detected, use PA (without tonality).
References:
Zwicker, E. and Fastl, H. Psychoacoustics: Facts and Models. Springer, 2013.
More, S. R. Aircraft noise characteristics and metrics (thesis), 2010, pp. 201–204.
Typical Workflow
Record the product under standardized operating conditions
Compute all four metrics (same CalibrationFactor and SoundField for consistency)
Compute psychoacoustic annoyance (PA or PAT) as a single-number summary
Compare to competitor products or previous product generations
Identify which metric is the primary differentiator
Use specific loudness / modulation frequency to trace the physical source
Copyright 2026 The MathWorks, Inc.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- MathWorks
- Publisher
- MathWorks (Official)
- Source
- matlab/matlab-agentic-toolkit · skills-catalog/signal-processing/matlab-evaluate-acoustic-metrics · commit 2a7f215
- Licence
- BSD 2-Clause License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE.md)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by MathWorks.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download matlab-evaluate-acoustic-metrics.zip