--- title: "Spatial Averaging" slug: "spatial-averaging" updated: 2026-05-07T14:32:47Z published: 2026-05-07T14:32:47Z canonical: "doc360.rationalacoustics.com/spatial-averaging" --- > ## Documentation Index > Fetch the complete documentation index at: https://doc360.rationalacoustics.com/llms.txt > Use this file to discover all available pages before exploring further. # Spatial Averaging Unlike [Temporal Averaging](/v1/docs/averaging-over-time-temporal-averaging), spatial averaging involves averaging measurements taken at different locations. Temporal averaging refers to the average buffer of an individual measurement engine. Spatial averaging can help get a clearer picture of system response by “averaging out” localized acoustical anomalies. It can also be helpful for getting a broader, more statistical picture of background noise or the overall tonality of a loudspeaker or audio system - rather than a single point in space. ## Spatial Averaging in Smaart ![](https://cdn.document360.io/a725c8f7-3a1a-4c09-9518-5d15d09a2ae2/Images/Documentation/image(161).png?sv=2026-02-06&spr=https&st=2026-11-18T17%3A23%3A56Z&se=2026-11-18T18%3A23%3A56Z&sr=b&sp=r&sig=T0zDV7qP294873P1AcnMIJpNqfotFBY6Hyi3q1U7rws%3D)Smaart enables you to create spatially averaged measurements by averaging live measurement data in real-time or by capturing Spectrum or Transfer Function measurements at multiple locations and averaging the results. Spatial averages can help to give you a better idea of how your system is performing across an area, and averaging measurements may also help to “wash out” some position-dependent artifacts such as comb filters caused by discrete reflections. Both live and offline spatial averages created from captured data can be calculated as a Decibel (dB) or power average. Additionally, spectrum (RTA) power averages can be calculated with or without normalization and transfer function decibel averages can be performed with or without coherence weighting. In this topic we focus on spatial averaging of captured data averages however the the options for live and captured data averages are identical. For specifics on configuring spatially averaged real-time measurements please see the articles for the *New Spectrum Avg* and *New TF Avg* commands. ![](https://cdn.document360.io/a725c8f7-3a1a-4c09-9518-5d15d09a2ae2/Images/Documentation/image(56).png?sv=2026-02-06&spr=https&st=2026-11-18T17%3A23%3A56Z&se=2026-11-18T18%3A23%3A56Z&sr=b&sp=r&sig=Ffe0JQFkottkXY8nDr4ays1dQ1XfD7nhWpyyEm3aX4E%3D)To create a new averaged measurement from captured data, click the hamburger (≡) menu button on the Data Bar and select *Average* from the menu (or right-click in the library pane of the Data Bar and select *Average* from the pop-up context menu). When you do this, one of two things happens depending on your current selection(s) in the data library pane. If a single trace data file is selected or there is currently no selection, the *Average* command opens the full version of the *Trace Average* dialog, where you can select individual trace data files to include in your averaged measurement by clicking the check boxes next to their names. If a folder and/or multiple trace data files are selected, Smaart simply offers to average the selected traces, including all traces contained in any selected folder(s). To multi-select files and folders in the data library, either hold down the [Ctrl/Cmd] key on your keyboard while clicking the objects that you want to select with your mouse, or hold down the [Shift] key while selecting a contiguous group of objects. In either case, Smaart will suggest a default name for your new averaged measurement, which you can change by clicking in the *Name* field and typing whatever you want the name to be. The program will also assign a trace color automatically and this can also be changed by clicking on the color tile below the name field to open the color picker dialog. Additional options affect how the average is calculated, depending on the data type (see below for more details). With one exception, these are identical regardless of which version of the *Trace Info* dialog that you invoke. The exception is that normalized spectrum trace averaging is accessible only through the full *Trace Average* dialog; it is not available when using the multi-trace selection shortcut. ![](https://cdn.document360.io/a725c8f7-3a1a-4c09-9518-5d15d09a2ae2/Images/Documentation/image(57).png?sv=2026-02-06&spr=https&st=2026-11-18T17%3A23%3A56Z&se=2026-11-18T18%3A23%3A56Z&sr=b&sp=r&sig=sgVovxE8Qws%2FdpjqaYoq2ovqMs6K0iEZViUIttzgNHE%3D)To create a normalized spectrum power average, make sure a spectrum display (*RTA* or *Spectrograph*) is selected as the active graph in the graph area, so that captured spectrum trace data is visible on the Data Bar, and that no more than a one trace is currently. (If you have multiple traces selected you can click once on any trace or click on a spectrum graph to clear the selection.) Click the *Average* button at the bottom of the Data Bar to open the *Trace Average* dialog, then click the *Normalize* checkbox. Notice that a third column of round "radio buttons" appears in the list of traces when this box is checked. Select the traces that you want to average by clicking their (square) check boxes and then, click the (round) radio button for the trace that you want to use as the reference level for normalization. In all cases, when you have made your selections, click *OK* to create the averaged measurement and exit the *Trace Average* dialog. Your new averaged trace should immediately appear in the data library pane on the Data Bar and on applicable graphs in the graph area. ## Decibel (dB) vs Power Averaging Both spectrum and transfer function trace averages can be calculated using decibel (dB) or Power averaging. In mathematical terms, decibel averaging is a simple arithmetic average of the decibel magnitudes for each frequency point in each contributing measurement. Power averaging is an RMS average of the squared linear magnitudes for each frequency point in each contributing measurement, expressed in decibels. In practical terms, power averaging tends to be biased toward the highest level measurements and the frequencies with the most energy. Decibel averaging tends to give you more of a consensus view, where all frequency data points in all measurements being averaged have equal weight in the average. Decibel averaging has the advantages of being straightforward, easy to use, and produces an intuitively reasonable result in applications where you want all measurements and all frequencies to be given equal weight. Its single biggest potential disadvantage is that it gives as much weight to the nulls in comb filters – which tend not to be very audible and are highly position-dependent – as it does to more clearly audible and stationary features of system response measurements. In spatial averages this can sometimes result in averaged measurements with "dips" in the apparent frequency response that look problematic on a graph but aren't really indicative of any real systemic issues. Smaart provides two options for spatial averages that can help mitigate this problem: coherence-weighted decibel averaging for transfer function data and normalized power averaging for both spectrum and transfer function data. ## Coherence Weighted Decibel Averaging When averaging transfer function traces, you have the option of using coherence weighting for decibel averages. Coherence weighting gives more weight in the average to the frequencies in each measurement that have the highest coherence values. Since coherence tends to be an indicator of signal-to-noise ratio in transfer function measurements, higher coherence suggests that the data may be more trustworthy. Coherence weighted decibel (dB) is the default selection for transfer function spatial average and will typically give you as good or better results than normalized power averaging, in terms of de-emphasizing the nulls in comb filters. Although the results tend to be very similar in practice, the coherence function is also sensitive to factors other than comb filtering, such as uncorrelated noise and distortion that would be undetectable by power averaging the magnitude data alone. Also, coherence weighted averaging requires no normalization step and so the frequency range of the system under test is not a concern. ## Normalized Power Averaging Smaart offers normalized power averaging for both spectrum and transfer function spatial averages. In acoustical system response measurements, when there are significant comb filters in the data traces being averaged, the tendency of power averaging to be biased toward the higher magnitude values and to de-emphasize lower values can work to your advantage, provided that all the measurements being averaged are similar in overall level. Smaart can ensure that this is true by normalizing (level matching) the individual traces going into the averaged measurement prior to calculating the average. Transfer function spatial power averages are always normalized, since we can reasonably assume in that case that we are averaging frequency response measurements and can simply reference to 0 dB. In the context of spectrum averages, however, unadjusted (i.e., not normalized) power averaging is *required* for certain applications such as background noise surveys, where the objective is to estimate of overall sound level throughout a given area. When normalization *is* desirable for spectrum averages, because magnitude levels are absolute not relative, we also need to pick some reference level to normalize to and so neither of the assumptions we could make for transfer function measurements apply. Two additional steps are therefore required. You have to explicitly turn normalization on and then select one of the traces being averaged as the reference level to adjust the others to. When you perform a normalized average Smaart calculates the average magnitude level across a specific frequency range and for each trace selected for inclusion in the average, then adjusts the overall level of all traces to match that of the baseline reference. The frequency range for normalization in spectrum averages is from 125 Hz to 4 kHz because the feature was designed primarily with cinema systems in mind. For transfer function power averages, the low end of the normalization range is moved up to 225 Hz to prevent low-frequency build-up common in music reproduction/reinforcement systems from overly influencing normalization offsets and it extends up to to 8.8 kHz on the high end (there being no assumption that the system is tuned to the cinematic X curve). Note that for spectrum spatial averages, normalization can be used for both power and decibel averages. In decibel averages however, normalization affects only the overall level of the resulting averaged trace and in no way affects the shape of the resulting averaged spectrum. It is just a convenience in that case. The frequency content of a given signal. The frequency (magnitude and phase) response of a system, function or network. The transfer function of the linear time invariant (LTI) system can be measured directly, using techniques such as dual-FFT transfer function measurements that compare the output of the system to its input signal in the frequency domain, or by taking the Fourier transform of the system’s impulse response. The decibel, often abbreviated as dB, is a logarithmic ratio between two values. In electronics and acoustics, decibels most commonly refer to the ratio between a given amplitude value and the number 1, where some reference value such as the maximum output of an A/D converter (dB Full Scale or dBFS) or the threshold of audibility for human hearing (for dB SPL) is scaled to equal 1. The decibel value for an amplitude is then calculated as: dB = 20·Log10(A) = 10·Log10(A 2 ), where A is linear amplitude. In this case, amplitude values greater than one yield positive decibel values and numbers smaller than one become negative dB values. This is why dB FS values are most often negative and dB values in sound level measurements are nearly always positive.