How to Calculate Sound Background Noise Level Between Rooms

How to Calculate Sound Background Noise Level Between Rooms

By James Hartley ·

1. Project overview: what, where, who, and why

In late February, our team at Sonus Gear Flow was brought into a retrofit project at a mid-size post-production facility in Portland, Oregon. The site had two adjacent rooms on the second floor of a converted warehouse: a dialogue edit suite (Room A) and a small live-record room used for ADR and voiceover (Room B). The facility manager had already upgraded monitors and room treatment but kept losing time to a recurring complaint: “The edit suite is quiet until someone records next door. Then the noise floor changes and the dialogue cleanup gets harder.”

The client asked for a concrete answer to a deceptively simple question: What is the background noise level from Room B as heard in Room A, and how does it compare to our target? They wanted the methodology documented so their project manager could re-run the calculations after future gear changes or construction. The team on this job included:

The “why” was business-critical: the studio booked ADR in two-hour blocks and delivered TV mixes on tight deadlines. They needed predictable noise behavior so editors could set consistent denoise thresholds and avoid revisiting sessions due to shifting background conditions.

2. Challenges and requirements at the outset

The facility’s baseline targets were aligned with common post-production expectations: Room A needed a low, stable noise floor equivalent to roughly NC-20 to NC-25 during critical work, with no intermittent intrusions from Room B when normal ADR prep was happening (talkback, cue playback at modest level, and occasional footfall).

The constraints were typical of a retrofit:

The key requirement was not just “measure noise.” It was to calculate the background noise contribution between rooms in a way that the team could repeat. That meant combining measured levels, instrumentation calibration, and a clear distinction between:

3. Approach and methodology chosen

We used a method that’s practical for real facilities and aligns with how standards-based work is often validated in the field:

  1. Establish baseline background noise in Room A with Room B silent (doors in normal operating position).
  2. Create a controlled noise source in Room B using pink noise at stable levels, measured at a reference position.
  3. Measure the resulting level in Room A in 1/3-octave bands (or octave bands when time is limited) to see frequency-dependent transmission.
  4. Calculate the transmitted contribution by energy subtraction: Ltrans = 10 log10(10Ltotal/10 − 10Lbase/10).
  5. Assess impact against targets using A-weighted levels for operational decisions, and band data for diagnosing pathways (low-frequency issues typically indicate structural/duct paths; mid-high often indicates door/seal leaks).

Equipment choices were aimed at repeatability. We used:

For timelines: one day for measurements and calculations, two days for interpreting results and proposing fixes, then a one-week window for minor construction if needed.

4. Step-by-step execution narrative

Step 1: Confirm operating conditions and calibrate

Measurements are only as good as the operating assumptions. We first set “normal use” conditions:

We calibrated the M23 with the NTi calibrator at 94 dB SPL, 1 kHz and confirmed the software chain level. We then checked that REW’s RTA was reading consistently with the NTi XL2 (within ~0.7 dB A-weighted for steady noise), which was acceptable for this field assessment.

Step 2: Measure Room A baseline background noise

In Room A, we placed the mic at the primary listening position (mix chair), 1.2 m above the floor, pointing upward to reduce directional bias. We logged 90 seconds of A-weighted and 1/3-octave data and captured the Leq (equivalent continuous level).

Room A baseline (Room B silent):

That baseline was actually respectable for a retrofit. The issue wasn’t “Room A is loud,” it was “Room A changes when Room B is active.”

Step 3: Generate a controlled noise source in Room B

In Room B, we placed a Genelec 8030C approximately where the talkback/cue monitor usually sat: 1.3 m off the floor, 0.6 m from the demising wall. We played pink noise and set a reference level of 78 dBA at 1 m from the speaker (measured with the M23 in REW, cross-checked with the XL2).

This level was chosen for two reasons: it was above the Room A baseline enough to make energy subtraction stable, and it represented a “moderate operational noise” scenario (cue playback at a level that doesn’t endanger hearing but reflects real session behavior).

Step 4: Measure Room A total noise with Room B active

With Room B playing pink noise continuously, we repeated the Room A measurement at the same position, logging for 90 seconds.

Room A total with Room B noise active:

The “total” number by itself isn’t yet actionable. The calculation step is where the transmitted component becomes clear.

Step 5: Calculate transmitted background noise contribution

We used energy subtraction to estimate the noise attributable to Room B transmission:

Formula: Ltrans = 10 log10(10Ltotal/10 − 10Lbase/10)

Plugging in the A-weighted levels:

Converting to linear energy:

This result often surprises teams: the transmitted component (26.8 dBA) is not the same as the delta between total and baseline (4.8 dB). Because decibels are logarithmic, a seemingly small increase can indicate a substantial additional energy contribution.

We repeated the same subtraction in octave bands to identify pathways. The largest transmitted contributions were in the 63–125 Hz bands, with secondary contributions around 250 Hz.

5. Technical decisions and trade-offs made

Several practical trade-offs came up during the day:

The trade-off was clear: we were not producing a formal lab-grade STC or ISO 16283 report. We were producing a field-calculation method that answered the operational question and pointed to fixes.

6. Results and outcomes with specific details

The main finding was that Room A’s baseline was fine, but the transmitted background from Room B during moderate activity was ~26.8 dBA at the mix position, with disproportionate low-frequency energy (63–125 Hz).

Diagnostics revealed two dominant transmission paths:

  1. Door/corridor flanking: At the Room A door location, levels were 2–3 dB higher than at the mix position in the 500 Hz–2 kHz range, suggesting leakage and flanking via the corridor. Door seals were incomplete at the threshold; there was a visible 3–5 mm gap in places.
  2. HVAC return coupling: When we temporarily blocked the Room B return grille with a dense temporary panel (not a permanent solution, strictly a diagnostic), Room A’s 63–125 Hz transmission dropped by ~2 dB. That indicated shared duct/return paths were contributing to the low-frequency change.

The client opted for a “fast intervention” package rather than opening the demising wall:

After the upgrades, we repeated the same test protocol one week later.

Post-fix measurements (same conditions and levels):

In practical terms, the edit suite’s noise floor still rose slightly when Room B was active, but the shift was smaller and less low-frequency heavy. Editors reported they no longer had to change denoise thresholds mid-session, and the re-recording mixer stopped hearing “the room change” during quiet dialogue passages.

The schedule impact was minimal: measurement day (Friday), approvals (Monday), door seals (Tuesday), HVAC work (Wednesday/Thursday nights), re-test (next Friday). Total downtime in either room was kept under six hours.

7. Lessons learned and what could be done differently

The project reinforced a few realities that don’t show up in simplified isolation discussions:

What we would do differently with more time: run a fuller set of positions (four corners plus mix position) and log longer averages (3–5 minutes) to capture HVAC cycling. We would also measure the corridor as a separate receiving space to quantify flanking more explicitly.

8. Takeaways applicable to other projects

If you need to calculate the background noise level transmitted between rooms in a way that supports decisions, the workflow from this case study is portable:

  1. Measure a baseline in the receiving room under real operating conditions (HVAC on, gear on).
  2. Introduce a stable, repeatable noise source in the source room (pink noise is fine) and document the reference level at a fixed distance.
  3. Measure the new total in the receiving room at the same mic position and with the same averaging time.
  4. Calculate the transmitted component with energy subtraction (A-weighted for impact, banded data for diagnosis).
  5. Use the frequency signature to choose fixes:
    • Mid/high leakage often points to doors, seals, penetrations, or weak flanking through corridors.
    • Low-frequency dominance often points to HVAC paths, structure-borne transmission, or insufficient decoupling.
  6. Re-test using the identical protocol after any change. If your method isn’t repeatable, your conclusions won’t be either.

The most valuable deliverable on this job wasn’t a single number; it was a documented, field-friendly method that connected subjective complaints (“the room changes”) to a measurable transmitted noise component and a targeted mitigation plan. That combination is what keeps post rooms predictable—and keeps schedules from slipping.