Live sound engineering is no longer confined to the physical mixing console. Almost every major tour, theater production, and festival stage requires a multi-track recording. These recordings serve multiple purposes: archiving the show, creating broadcast mixes, or running virtual soundchecks to tune the PA during pre-production. However, running out of hard drive storage space halfway through a headliner's set is a catastrophic failure. The **SoundEngg Audio File Size Estimator** is designed to guarantee you have the necessary storage and write speeds before the first note is struck.

1. The Math of Uncompressed PCM Audio

Uncompressed digital audio (such as standard broadcast WAV or AIFF files) has a highly predictable data footprint. Unlike compressed MP3 or AAC files, uncompressed Pulse Code Modulation (PCM) audio records every single voltage sample at a fixed rate, meaning the file size depends entirely on three parameters:

  • Sample Rate (Hz): The number of times per second the analog voltage is sampled (e.g., 48,000 times for 48kHz).
  • Bit Depth (bits): The resolution of each sample, determining dynamic range (e.g., 24-bit).
  • Channel Count: The number of discrete tracks recorded simultaneously.
  • Duration (seconds): The length of the recording.
The mathematical formula to calculate the size of an uncompressed audio file in bytes is:


Size (Bytes) = Sample Rate × (Bit Depth / 8) × Channels × Duration

To convert this into Megabytes, divide the result by $1,048,576$ (since $1 ext{ MB} = 1024^2 ext{ bytes}$). Let's look at how this plays out in real-world scenarios.

2. Real-World Scenarios: 48kHz vs. 96kHz

Many modern professional consoles (such as the Allen & Heath dLive, DiGiCo Quantum, or Yamaha Rivage) operate natively at 96kHz / 24-bit. While this offers incredible high-frequency resolution and low internal processing latency, it places a massive demand on your recording drive. Additionally, some digital interfaces and software recorders support **32-bit floating-point** recording, which provides virtual immunity to digital clipping at the file stage, but increases file sizes by 33% relative to 24-bit.

Consider a standard 64-channel multi-track recording for a 3-hour festival set:

  • At 48kHz / 24-bit:
    Each second of a single channel consumes: $48,000 imes (24 / 8) = 144,000 ext{ bytes} approx 140.6 ext{ KB/sec}$.
    For 64 channels over 3 hours (10,800 seconds), this requires **roughly 93 Gigabytes** of storage space.
  • At 96kHz / 24-bit:
    Doubling the sample rate doubles the data throughput. The same 64-channel, 3-hour recording now requires **roughly 186 Gigabytes** of storage space.
  • At 96kHz / 32-bit float:
    Each sample requires 4 bytes of data instead of 3. The data throughput jumps to $384,000 ext{ bytes/sec}$ per channel.
    The 64-channel, 3-hour recording now requires **roughly 248 Gigabytes** of storage space.
If you connect a standard 128GB USB drive to record a 96kHz festival set, the drive will run out of space halfway through the show. Using our calculator helps you predict these storage demands instantly, allowing you to choose the appropriate sample rate and bit depth for your hardware configuration.

3. Disk Write Speeds: The True Bottleneck

File size is only half the battle; your storage drive must be fast enough to write the incoming data stream in real-time. If you record 64 tracks at 96kHz/24-bit, the data rate is approximately **17.2 Megabytes per second** ($138 ext{ Mbps}$).

While this number seems low compared to modern USB SSD transfer rates, the bottleneck is **sustained write speed**. Cheap flash drives have high burst speeds but thermal-throttle under continuous use, dropping their write speed to single digits. When the drive slows down, the DAW buffer overflows, resulting in dropped samples, clicks in the audio, or a crashed recording. Always use a dedicated, external Solid-State Drive (SSD) connected via USB 3.0 or Thunderbolt, and format it to **exFAT** or **NTFS** to bypass the 4GB file size limit of legacy FAT32 systems.

4. The 20% Safety Buffer

Pro Tip: Never calculate your storage down to the exact gigabyte. Always add a **20% safety buffer**. Filesystem overhead, partition tables, and directory structures consume disk space. Additionally, live shows rarely run on schedule; a 2-hour set can easily stretch to 2.5 hours with encores and stage delays. If your calculation indicates you need 100GB, carry a 250GB or 500GB SSD to ensure the recording never clips the drive limit. Running out of space will corrupt the index file, rendering the entire recording unreadable.

(Editor’s note: Need to estimate storage space or write speed limits for your next tour? Open our interactive Signal Generator to run line checks on your inputs, and check real-time levels using our web-based RTA Spectrum Analyzer).

Summary

Multi-track recording is a standard expectation in pro audio. By calculating uncompressed PCM size demands, using high-speed SSDs formatted to exFAT to avoid write speed bottlenecks, and maintaining a 20% safety margin, you can ensure a flawless multitrack recording of every show.