Generated banner for Matlab Evaluate Acoustic Metrics
Generated logo for Matlab Evaluate Acoustic Metrics

Matlab Evaluate Acoustic Metrics

MathWorksOfficialCreated by MathWorks

  • Skill
  • Tool integration
  • Science and research
  • BSD-2-Clause
  • No issues found

From the author

Select and use Audio Toolbox acoustic, psychoacoustic, and speech quality metrics. Use when computing loudness, sharpness, roughness, fluctuation strength, noise criteria (NC/RNC/RC), speech transmission index (STI), speech intelligibility index (SII), speech quality (ViSQOL, STOI), SPL, reverberation time (RT60), tone-to-noise ratio, or prominence ratio. Also use when asked about PESQ, POLQA, calibration factor, EBU R 128, LUFS, HVAC noise, background noise evaluation, or how to measure audio quality or noise compliance. Covers calibration, standard selection, signal alignment, and the complete function inventory including what does NOT exist.
— the description by MathWorks

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/matlab/matlab-evaluate-acoustic-metrics/download
  2. Unzip 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-audio

  • Audio device I/O, recording, or live calibrateMicrophone — use matlab-play-record-audio

  • Audio plugin authoring (VST/AU) — use matlab-write-audio-plugin

  • General filter design unrelated to measurement — use matlab-design-digital-filter

  • Spatial audio / HRTF / SOFA processing

Workflow

Follow this decision tree to route the user's goal to the right function:

1. Identify the measurement goal
GoalCategoryGo 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

FunctionStatusUse Instead
pesqDoes NOT exist (proprietary ITU-T P.862 license)visqol(degraded, reference, fs, Mode="speech")
polqaDoes 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

FunctionPurposeStandardAvailable From
acousticLoudnessPerceived loudness (sones)ISO 532-1/2R2020a
acousticSharpnessPerceived sharpness (acum)DIN 45692R2020a
acousticRoughnessPerceived roughness (asper)—R2021a
acousticFluctuationFluctuation strength (vacil)—R2020b
integratedLoudnessBroadcast loudness (LUFS)EBU R 128 / ITU-R BS.1770R2016b
loudnessMeterStreaming broadcast loudness meterEBU R 128 / ITU-R BS.1770R2018a
visqolFull-reference audio quality (MOS)—R2024a
stoiShort-time objective intelligibility—R2024a
mnruModulated noise reference unitITU-T P.810R2024a
dBovPower level relative to overload (dB)ITU-T G.100.1R2024a
speechTransmissionIndexSTI from IR or test signalsIEC 60268-16R2026a
speechIntelligibilityIndexSII from IR, test signals, or levelsANSI/ASA S3.5-1997R2026b
stipaExcitationGenerate STI/STIPA test signalsIEC 60268-16R2026a
siiExcitationGenerate SII test signalsANSI/ASA S3.5-1997R2026b
noiseCriteriaNC rating + SIL + spectrum imbalance + rattle riskANSI/ASA S12.2R2026b
roomNoiseCriteriaRNC rating (detects surging/fluctuations)ANSI/ASA S12.2R2026b
roomCriteriaRC Mark II rating (HVAC systems)ANSI/ASA S12.2R2026b
noiseCriteriaCurvesLook up NC curve valuesANSI/ASA S12.2R2026b
noiseCriteriaRecommendationsRecommended NC levels by room typeANSI/ASA S12.2R2026b
speechInterferenceLevelSIL from recordingANSI/ASA S12.2R2026b
rt60Reverberation time from impulse responseISO 3382-1/2R2025a
acousticToneToNoiseRatioDetect/quantify tonesECMA-418-1R2023b
acousticProminenceRatioTonality via critical band comparisonECMA-418-1R2023b
splMeterSPL measurement (time-weighted, per-band)IEC 61672R2018a
calibrateMicrophoneCompute calibration factor from known tone—R2018b
weightingFilterA/C/Z/K frequency weightingIEC 61672-1R2016b
octaveFilterSingle octave-band filterANSI S1.11-2004R2017b
octaveFilterBankMulti-band octave filteringANSI S1.11-2004R2019a

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:

  1. 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.

  2. Compute the system calibration factor: calibrationFactor = calibrateMicrophone(calRecording, fs, SPLreading, FrequencyWeighting="Z-weighting")

  3. 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:

ConversionFunctionMethod selection
phon → sonephon2sone(phon, standard)"ISO 532-1" (default), "ISO 532-2"
sone → phonsone2phon(sone, standard)"ISO 532-1" (default), "ISO 532-2"
Hz → ERBhz2erb(freq)Single formula (no variants)
ERB → Hzerb2hz(erb)Single formula (no variants)
Hz → barkhz2bark(freq)Single formula (no variants)
bark → Hzbark2hz(bark)Single formula (no variants)
Hz → melhz2mel(freq, MelStyle=s)"oshaughnessy" (default), "slaney"
mel → Hzmel2hz(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:

SituationFunctionWhy
General background noise ratingnoiseCriteriaStandard NC curves (ANSI/ASA S12.2)
HVAC system noise specificallyroomCriteriaRC Mark II designed for HVAC evaluation
Noise with audible surging/fluctuationroomNoiseCriteriaRNC penalizes time-varying noise (requires ≥15 s recording)
Quick speech interference checkspeechInterferenceLevelDirect SIL value
Need recommended levels for room typenoiseCriteriaRecommendationsLookup 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:

  • NC is a string (e.g., "NC-35" or "NC-56 (1000 Hz)" if a band exceeds)

  • RC is a string (e.g., "RC-32(N)" — the letter indicates spectrum quality: N/R/H/RV)

  • SIL and LMF are double scalars (dB)

  • QAI is a double scalar (dB; 0 = ideal neutral)

  • specImbalance and rattleRisk are structs with .Summary (string) and .Details (table) — access .Summary for display. Exception: specImbalance degrades to a char scalar (not a struct) when NC exceeds the curve range (e.g., "Above NC-70") or falls below NC-15. Guard with isstruct(specImbalance) before dot-indexing.

  • noiseCriteriaRecommendations requires 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 roomCriteria

  • Is 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, :) where T is 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 (not FilterOrder). FilterOrder does not exist on splMeter.

  • FrequencyRange compares 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). Use floor(true_center) for lower bounds and ceil(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

FunctionInternal alignment?Action
visqolYesNo action needed
stoiNoAlign before calling
speechTransmissionIndexNoAlign for direct method; IR method avoids issue
speechIntelligibilityIndexNoAlign 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

MistakeWhy it failsCorrect approach
Call pesq(reference, degraded, fs)Function does not existvisqol(degraded, reference, fs, Mode="speech")
stoi(reference, processed, fs)Wrong argument orderstoi(processed, reference, fs) — processed FIRST
acousticFluctuationStrength(...)Wrong function nameacousticFluctuation(audioIn, fs, calFactor)
Implement NC from scratch with hardcoded curvesMisses SIL, spectrum imbalance, rattle risknoiseCriteria(audioIn, fs, CalibrationFactor=cf)
20*log10(rms(x)/20e-6) for SPLNo weighting, no time integration, no calibrationsplMeter with appropriate settings
Implement STI algorithm manually~100 lines, error-prone, misses NV optionsspeechTransmissionIndex(ir, fs)
Divide signal by calibration factor manuallyIncorrect; factor is a multiplier, not a divisorPass as positional arg or CalibrationFactor=value
Skip alignment for direct STI/SIISilent accuracy degradationalignsignals(processed, reference) before calling
Use acousticLoudness for broadcast loudnessWrong standard (ISO 532 = sones, not LUFS)integratedLoudness for EBU R 128 compliance
string(rattleRisk) or fprintf("%s", specImbalance)These are structs, not stringsAccess .Summary field: rattleRisk.Summary
specImbalance.Summary when NC is out of curve rangespecImbalance degrades to char (not struct) when "Above NC-70" or below NC-15Guard: if isstruct(specImbalance), disp(specImbalance.Summary); end
roomNoiseCriteria on recordings shorter than 15 sANSI/ASA S12.2-2019 requires ≥150 Lt samples at 100 ms intervalsEnsure recording is at least 15 seconds; use noiseCriteria for shorter clips
round(NC) or arithmetic on NC/RC outputNC and RC are strings, not numbersUse directly: fprintf("%s\n", NC)
noiseCriteriaRecommendations() with no argsFirst argument (criteria name) is requirednoiseCriteriaRecommendations("NC")
loudness.OverallLoudness after acousticLoudnessReturns a scalar or vector, not a structUse directly: fprintf("%.1f sones\n", loudness)
splMeter(..., FilterOrder=8)Property does not exist on splMeterUse OctaveFilterOrder=8
splMeter(..., FrequencyRange=[16 8000]) for 16 Hz–8 kHzDrops 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 SPLManual, no time weighting, no calibration integrationUse splMeter with Bandwidth="1 octave"
Treating splMeter output as a single valueAll 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 calibrateMicrophone for system-level accuracy

  • Default to SoundField="free" for anechoic/outdoor, "diffuse" for reverberant rooms

  • Default 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 CalibrationFactor explicitly rather than pre-scaling the signal

  • For noise compliance, prefer roomCriteria for HVAC and noiseCriteria for general background noise


Copyright 2026 The MathWorks, Inc.


Files

references/rt60-measurement.md

RT60 Measurement

Guidance for selecting parameters, interpreting results, and guiding user workflows for rt60.

Intake Questions

1. What is the purpose?
PurposeWhat RT60 tells them
Room design verificationDoes the finished room meet the acoustic design target?
Speech intelligibility assessmentIs the room too reverberant for speech? (RT60 > 1.5s generally problematic)
Music venue evaluationIs the reverberance appropriate for the genre?
Noise control / absorption planningHow much absorption is needed to reduce RT60 to target?
Compliance with building standardsDoes the room meet standards like BB93, ANSI S12.60?
STI contextExplaining why STI is low — reverberance is the usual culprit
2. Do they have an impulse response?
  • Yes: Pass directly to rt60(ir, fs)

  • No, need to measure: See the matlab-play-record-audio skill for the IR capture workflow (sweeptone generation, playback/recording through the room, and impzest deconvolution). This skill covers what to do with the IR once obtained.

IR requirements: The IR must include the noise floor — continue recording after the reverberation tail has fully decayed. The function assumes at least the last 10% of the IR duration corresponds to noise (used for noise floor estimation). For large reverberant spaces (churches, concert halls), use longer captures (3–5 s minimum).

3. What analysis bandwidth?
BandwidthOutputWhen to use
"1 octave" (default)RT60 per octave bandStandard building acoustics, compliance checks, general room characterization
"1/3 octave"RT60 per 1/3-octave bandDetailed analysis, research, when absorption varies significantly within octave bands
4. Noise compensation method
MethodBehaviorWhen to use
"truncate-correct" (default)Lundby algorithm: estimates noise floor, truncates IR at noise intersection, compensates per ISO 3382-1Standard-compliant measurements; most situations
"subtract-truncate-correct"Additionally subtracts noise floor before truncationWhen the noise floor is relatively high; shown to introduce less systematic error in noisy conditions (non-ISO)

Default is appropriate for most users. Only suggest "subtract-truncate-correct" when IRs have marginal SNR and the user does not require strict ISO 3382-1 compliance.

5. Measurement conditions (ISO 3382-2)

ISO 3382-2 defines three measurement levels (Table 1, section 4.3):

LevelSource-mic combinationsSource positionsMic positionsAccuracy (octave)
Survey≥2≥1≥2~10%
Engineering≥6≥2≥2~5%
Precision≥12≥2≥3~2.5%

Position requirements (section 4.3.1):

  • Mic positions shall be at least half a wavelength apart (~2 m for typical frequency range)

  • Distance from mic to nearest reflecting surface (including floor) should preferably be at least a quarter wavelength (~1 m)

  • Minimum source-to-mic distance depends on room volume and expected RT60: d_min = 2×sqrt(V / (c×T))

  • Symmetric positions shall be avoided

Additional conditions:

  • Room state: Furnishings in place as intended for use (unfurnished rooms measure much longer RT60)

  • Background noise (section 5.2.1): Source level shall be at least 35 dB above background noise for T20, or 45 dB for T30

  • Reliability (ISO 3382-1 section 7.3): Results shall satisfy B×T > 16, where B is the filter bandwidth (Hz) and T is the measured reverberation time (s). Low-frequency bands with short RT60 may fail this criterion.

Interpreting RT60 Results

T20 vs T30 vs EDT
MetricEvaluation RangeWhat it represents
EDT (Early Decay Time)0 to −10 dBPerceived reverberance — what listeners experience (first part of decay dominates perception)
T20−5 to −25 dBReverberation time extrapolated from 20 dB range — more robust to noise than T30
T30−5 to −35 dBReverberation time from 30 dB range — more accurate but requires higher IR SNR

Guidance:

  • EDT correlates best with subjective impression of reverberance — use when reporting "how reverberant the room feels"

  • T30 is the standard metric for compliance and design verification (ISO 3382 prefers T30 when SNR allows)

  • T20 is a fallback when background noise limits the usable decay range

  • Topt uses the decay range yielding the best linear fit while remaining 10 dB above the detected noise floor — useful when neither T20 nor T30 gives a clean fit

  • In a well-diffused room, EDT ≈ T20 ≈ T30. If they diverge significantly:

    • EDT << T20/T30: Strong early reflections followed by a long tail (common with localized absorption near source/receiver)

    • EDT >> T20/T30: Weak early field (unusual — check measurement)

  • Metrics return NaN when the detected noise floor does not allow 10 dB of headroom over the evaluation range — this indicates insufficient IR SNR for that metric in that band

Additional Output Metrics

The rt60 output table includes metrics beyond reverberation time that are useful for room quality assessment:

MetricStandardDefinitionApplication
C50ISO 3382-1Clarity (50 ms cutoff) — early-to-late energy ratio (dB)Speech clarity: C50 > 0 dB is generally acceptable; higher is clearer
C80ISO 3382-1Clarity (80 ms cutoff) — early-to-late energy ratio (dB)Music clarity: C80 between −2 and +2 dB is optimal for most genres
D50ISO 3382-1Definition (50 ms cutoff) — early-to-total energy ratio (0 to 1)Speech: D50 > 0.5 generally indicates adequate articulation
TSISO 3382-1Center time — center of gravity of the squared IR (seconds)Lower TS = more early energy; correlates with clarity perception
DegreeOfNonLinearityISO 3382-2 B.21000×(1−r²) for the linear fit of each decay range (N-by-4 matrix: EDT, T20, T30, Topt)Values 0–5 typical; high values suggest non-exponential decay
CurvatureISO 3382-2 B.3100 × (T30/T20 − 1) (signed)Values −5 to 5 typical; magnitude indicates divergence between T20 and T30; sign indicates direction

When to report which metrics:

  • Room design compliance: T30 (or T20), Curvature

  • Speech room assessment: T30, EDT, C50, D50

  • Music venue assessment: T30, EDT, C80, TS

  • Measurement quality check: DegreeOfNonLinearity, Curvature

Target RT60 Values by Space Type
SpaceTarget RT60 (s)Standard/Reference
Recording studio / control room0.2–0.4—
Classroom (≤283 m³)≤ 0.6ANSI S12.60, BB93 (UK)
Classroom (>283 m³)≤ 0.7ANSI S12.60
Conference room0.4–0.7—
Lecture hall0.7–1.0—
Open plan office0.5–0.8—
Concert hall (symphony)1.8–2.2—
Concert hall (chamber music)1.4–1.8—
Opera house1.2–1.6—
Church (liturgical music)2.0–4.0—
Worship (speech-primary)0.8–1.2—
Hospital patient room0.4–0.6—
RT60 vs Frequency

RT60 typically varies with frequency:

  • Low frequencies (125–250 Hz): Often longer (less absorption from typical materials at LF)

  • Mid frequencies (500–1000 Hz): Reference range — most targets are specified here

  • High frequencies (2000–8000 Hz): Often shorter due to air absorption and porous absorber effectiveness

Common patterns and implications:

PatternCauseAction
Flat across frequencyWell-treated room with broadband absorptionIdeal for speech and music
Rising at low frequencyInsufficient bass trappingAdd bass traps, panel absorbers, or membrane absorbers
Falling at high frequencyExcessive HF absorption or air absorption in large roomsNormal for large volumes; add diffusion if HF liveness desired
Spike at one frequencyRoom mode or resonanceTreat the specific mode with targeted absorption
Relationship to STI

RT60 and STI are directly related — reverberation is the primary degrader of speech intelligibility in quiet rooms. Approximate STI for purely diffuse exponential-decay rooms with no ambient noise (computed using speechTransmissionIndex on synthetic IRs with AddOperationalAmbientNoise=false):

RT60 (s)Approximate STIIEC 60268-16 Category
0.50.74A
1.00.60D
1.50.50G
2.00.44H–I
3.00.36U
5.00.27U

Adding ambient noise can only reduce STI below these values.

If the user has STI concerns:

  • Short RT60 but low STI → noise is the dominant factor, not reverberation

  • Long RT60 and low STI → reduce RT60 with absorption (most effective intervention)

  • Use rt60 to diagnose, then speechTransmissionIndex to quantify the intelligibility impact

Assessing Measurement Quality

Use DegreeOfNonLinearity and Curvature from the output table to assess whether results are trustworthy:

  • DegreeOfNonLinearity (ξ): Defined as 1000×(1−r²), where r² is the correlation coefficient of the linear fit to the energy decay curve. ξ = 0 means a perfect linear fit (r² = 1). ISO 3382-2 B.2 states typical values are 0–5. To interpret as r²: r² = 1 − ξ/1000 (e.g., ξ = 5 → r² = 0.995).

  • Curvature: Quantifies the divergence between T30 and T20. Values near 0 indicate consistent decay; |Curvature| > 5 suggests coupled volumes or non-diffuse conditions (ISO 3382-2 B.3).

  • NaN values: If a metric returns NaN, the detected noise floor does not provide enough headroom for that evaluation range in that band — use a metric with a shorter evaluation range (T20 instead of T30) or re-record with a stronger source.

Common Scenarios

Scenario: Classroom Compliance Check
  1. Obtain room IR (see matlab-play-record-audio for capture workflow; sine sweep method preferred for SNR)

  2. Compute: rtsummary = rt60(ir, fs, Bandwidth="1 octave")

  3. Read T30 (or T20 if insufficient SNR) at 500 Hz, 1000 Hz, 2000 Hz

  4. Average these three mid-frequency bands → this is the compliance metric

  5. Compare to target: ANSI S12.60 requires ≤ 0.6 s for rooms ≤ 283 m³

Scenario: Diagnose Low STI
  1. Measure STI: speechTransmissionIndex(ir, fs, OperationalNoiseLevel="NC-35")

  2. If STI is low, measure RT60: rtsummary = rt60(ir, fs)

  3. Examine frequency-dependent RT60 — which bands are too long?

  4. Cross-reference with MTI output from STI: low MTI at specific bands + long RT60 at those bands = reverberation-driven problem

  5. Recommend treatment: add absorption in the frequency bands where RT60 exceeds the target

Scenario: Concert Hall Evaluation
  1. Measure at multiple source-receiver positions (≥6 per ISO 3382-1)

  2. Compute per-position RT60 and EDT

  3. Report: mean T30 across positions (spatial average), EDT for perceived character

  4. Compare T30 to genre target (1.8–2.2 s for symphony, 1.4–1.8 for chamber)

  5. Check frequency balance: flat or gently rising at LF is preferred for warmth

Troubleshooting

Visual inspection of decay curves

The primary troubleshooting step is to call rt60 with no output arguments to generate the convenience plot. The plot shows:

  • Top panel: RT60 values (EDT, T20, T30, Topt) across octave bands — click a band to inspect it

  • Bottom panel: The energy decay curve (EDC) for the selected band with linear fit lines overlaid

Inspect the fit lines against the EDC to identify:

  • Noise floor intersection — where the EDC flattens, indicating the usable decay range

  • Double-slope decay (coupled rooms) — a "hump" or change in slope in the tail, where energy from an adjacent coupled space arrives. This appears as a concave EDC that doesn't follow a single straight line.

  • Poor fit — the linear regression doesn't track the actual decay

Adjusting parameters for better fits

If the decay curves show poor fits, adjust FilterOrder, FilterDirection, and NoiseCompensation and monitor DegreeOfNonLinearity and Curvature to find the combination that best characterizes the decay:

ParameterOptionsWhen to adjust
FilterOrder2 (default), 4, 6, ...Higher order gives sharper band separation — try when adjacent bands bleed energy
FilterDirection"forward" (default), "backward"Backward filtering eliminates filter ringing at the start of the decay — try when EDT looks unreliable
NoiseCompensation"truncate-correct" (default), "subtract-truncate-correct"Subtract mode reduces bias from high noise floors — try when T30 shows large DegreeOfNonLinearity
Common issues
ObservationLikely CauseAction
T30 varies wildly between bandsNormal if room has frequency-dependent absorptionExpected behavior; focus on mid-frequency average for compliance
T30 > T20 by large marginNoise floor contaminating the lower part of the decayTrust T20; re-measure with higher source level if T30 needed
Large Curvature with concave EDCCoupled room — energy returns from adjacent spaceReport T20 (less affected); note coupled-room behavior in results
EDT much shorter than T30Strong early reflections near measurement positionIndicates non-diffuse field; measure at more positions and average
Very short RT60 (<0.1 s)IR too short, or measurement captured direct sound onlyVerify IR contains the full decay; use longer measurement window
RT60 result shows NaN or unreliableInsufficient signal-to-noise ratio in that bandCheck noise floor; use T20 instead of T30; re-record with stronger source
Different results from different positionsNormal room mode behavior — spatial variation is expectedAverage across ≥3 positions per ISO 3382; report range
RT60 doesn't match subjective impressionEDT correlates better with perception than T30Report EDT alongside T30 for perceptual assessment
Measured RT60 seems implausible for the roomMeasurement error, or unexpected room conditionsUse predictRT60 with known room dimensions and materials as a sanity check against the measured value

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