Group Delay Graph

How group delay is displayed in milliseconds and why it is useful for comparing low-frequency alignments.

Direct answer

The group delay graph shows frequency-dependent delay in milliseconds derived from the simulated phase response.

What it measures

• Group delay in milliseconds over frequency.
• Delay changes introduced by enclosure resonance and filtering.
• Relative delay differences between alignments.

Why it matters

• It helps compare time-domain tradeoffs between sealed, vented, and passive-radiator designs.
• It can reveal delay peaks around tuning or filter corners.
• It adds context when two SPL curves look similar but behave differently.

How to read it in 00 Simulator

• Look for broad delay increases in the intended playback band.
• Compare designs on the same axis and frequency range.
• Use SPL and phase views alongside group delay before judging audibility.

What good, warning, and bad usually look like

Good

Delay remains controlled through the intended band and does not add large narrow peaks.

Warning

Delay rises near tuning in a way that may be acceptable for sub-bass but worth comparing.

Bad

Large delay peaks occur in the range where timing or crossover integration matters.

Common false conclusions

• Group delay has no single universal audible threshold for every system.
• Lower group delay is not useful if the design fails output or excursion requirements.
• The graph should not be read without considering the system crossover and listening context.

App behavior notes

• The UI graph id is `group-delay`; the internal graph key is `groupDelay`.
• Values are displayed in milliseconds.