Skip to content
Advanced Measurement Techniques

Averaging Measurements

Combine multiple measurements to get accurate representation of your system's performance across different positions

What is Measurement Averaging?

When you measure at multiple positions in a venue, averaging lets you combine those measurements into a single representative response. This is crucial for understanding how your system performs across the listening area rather than at just one point.

When to Use Averaging

  • •You've captured measurements at multiple listening positions
  • •You want to create tuning that works across your entire coverage area
  • •You need to identify consistent system characteristics vs position-specific issues

Creating an Average

1

Select Your Measurements

In the Measure tab, select multiple measurements by clicking while holding Shift (range) or Cmd/Ctrl (individual). You can select entire measurement sets by clicking on the set name.

2

Right-Click to Open Menu

Right-click on any selected measurement and choose Create Average.

3

Configure Averaging Options

A dialog will appear with three important settings. Choose the options that match your measurement scenario.

Averaging Options Explained

1. Averaging Method

This determines how the frequency response data is mathematically combined.

RMS Average (Default)

Averages magnitude only, discards phase information.

Best for:

  • •Multiple listening positions (non-coherent)
  • •Different distances from speakers
  • •Creating system tuning for coverage area

This is the most common choice for venue measurements

Vector Average

Preserves both magnitude and phase information.

Best for:

  • •Single position, multiple captures
  • •Coherent measurements (same distance)
  • •Reducing measurement noise

Use when phase relationships are consistent

2. Grouping

This determines how measurements are organized when averaged.

Average by Source (Default)

Creates separate averages for each source channel.

Example:

If you measured Left and Right speakers at 10 positions each:

  • →Creates "Left Average" from 10 left measurements
  • →Creates "Right Average" from 10 right measurements

Ideal for multi-channel systems to maintain source separation

Single Average

Creates one average from all selected measurements.

Example:

If you measured Left and Right at 10 positions:

  • →Creates one "System Average" from all 20 measurements

Use for overall system response regardless of source

3. Level Matching

This option normalizes SPL levels before averaging to ensure equal weighting.

Apply Level Matching (Default: ON)

Aligns the SPL of all measurements before averaging to ensure each position contributes equally.

With Level Matching (Recommended):

Measurement at 5 meters (quieter) = same weight as measurement at 1 meter (louder). Focuses on frequency response shape, not level.

Without Level Matching:

Louder measurements dominate the average. Only useful if you want level differences to affect the result.

Tip: Keep this enabled unless you have a specific reason to weight measurements by their SPL level.

Common Averaging Workflows

Venue Tuning Workflow

You measured 15 positions across your venue, each with both Left and Right sources.

Recommended Settings:

  • Averaging Method: RMS Average (different positions = non-coherent)
  • Grouping: Average by Source (maintain L/R separation)
  • Level Matching: ON (equal weighting regardless of distance)

Result: Two averages ("Left Average" and "Right Average") representing coverage-wide response

Noise Reduction Workflow

You captured 5 measurements at the exact same position to reduce measurement noise.

Recommended Settings:

  • Averaging Method: Vector Average (same position = coherent)
  • Grouping: Average by Source or Single (doesn't matter for same source)
  • Level Matching: OFF (all same position, same level)

Result: One cleaner measurement with reduced noise and better signal-to-noise ratio

Pro Tips

  • Check before averaging: View your individual measurements first to identify and exclude any obvious outliers or bad captures
  • Use RMS for tuning: When creating averages to feed into the Tuning tab, RMS is almost always the right choice
  • Keep originals: Averages don't delete your original measurements - you can always go back and adjust
  • Compare approaches: Try both RMS and Vector averages to hear the difference and understand when each is appropriate

What's Next?

Now that you know how to combine measurements, you're ready to optimize your system with measurement-based tuning.