Log in
Log in

or
Learning
Comment

Compression in the Volume Wars

The Loudness War - Part 2

Today we'll continue our series on the volume wars. This time, we'll focus on mainly on compression.

View other articles in this series...

[If you haven’t yet read part 1, you can read it here.]

After proving indispensable for radio (and incipient TV) broadcasters, the compressor/limiter started to take a much more important role in musical productions. The advent and standardization of multitrack recording, in which the band wasn’t a single entity anymore, but rather a group of musicians being separately recorded, allowed better control of the volume and dynamics of each recording. The ability to focus on individual multitrack tracks opened up more processing options like EQ, panning, etc.

Multitrack recording made possible a more eclectic combination of instrument types. The mix of acoustic, electronic and synthetic music (due to the arrival of the first synthesizers and electric and electromechanical instruments) called for a different approach to mixing, and a different treatment of the elements available. The sound of a band or an orchestra no longer depended entirely on the art of orchestration and the position of the musicians with respect to each other, but rather on the introduction of instruments that could be amplified to eclipse all the others together.

Home on the dynamic range

“Now that’s what I call dynamic!” How many times have you heard people use that term to describe overcompressed music ─ that is, music that sounds pretty loud, even at low volumes — when they’re actually describing the exact opposite of what dynamics means? Dynamics, or to call it by its full name, dynamic range, actually comprises everything between the loudest and quietest parts of a song or sound. 

La loudness war

Good dynamics are the responsibility of the musicians, first and foremost, because they’re the ones who create the nuances in the music, which are at the core of any performance. I often mention the absurd example of a pianist who plays all notes with the same intensity and an audio engineer who records him or her with 88 microphones, one per key, and creates dynamics by lowering or increasing the level of each mic (which would obviously not be enough, but remember that I resorted to the absurd to make a point). Audio overcompression (which shouldn’t be mistaken with data compression, which makes files smaller in size) downright annihilates the expressiveness of a musician, the nuances in music, with dramatic consequences to sound itself and to our ears.

What can justify going ─ in only 30 years, and after many decades of careful and dedicated work with audio ─ from this:

To this?

Compressing what?

As obvious as it seems, you can still find people confused about the notion of “compression” today. That’s due to the same word being used to describe two totally different processes. One is dynamic range compression, which results from using dynamics processors like compressors, limiters, expanders, transient shapers, etc. And the other is data compression, which is a process applied to a file when you wish to reduce its size to facilitate its transmission, especially online.

Dynamic range compression allows you to reduce the difference between the loudest and quietest passages of an audio file, which results in the potential increase of the overall volume. One of the fundamental causes of the loudness wars is that everyone wants their song to sound at least as loud, if not louder, than songs that are heard before and after it on the radio, in the club, or mobile devices. As a result, mixers and mastering engineers are squeezing every decibel they can out of the songs they work on, via the heavy use of limiters, which produce the most extreme form of compression. The result has been an escalation in volume and a consequent reduction of dynamic range, as the volume peaks get crushed in order to get the average level as high as possible without clipping. The two waveforms shown above are a testament to how things have changed in terms of loudness.

The other type of compression, data compression, is a completely different animal, and is not an audio processing effect. It was conceived to find a solution to the low transfer rates of the first communication protocols on the Internet. It allows you to significantly reduce the size of a file and, thus, the necessary transfer rate to send it from one point to another (or to stream it).

For audio, as for any other media, the rate is measured in kilobits per second (kbit/s or kb/s, except for multi-channel transfers at very high resolutions). For example, the transfer rate for a 16 bit/44.1 kHz stereo Wav or AIFF file is about 1412 kb/s (and 2117 kb/s for the same file with a 24-bit resolution). When you say 128 MP3, 256 AAC, what you are actually saying is the file has a transfer rate of 128 kb/s and 256 kb/s, respectively. When you compare that to non-compressed audio files (remember we are talking about data compression here), it’s easy to understand that lots of things have gotten lost on the way. And what are the consequences, in terms of audio? We’ll look at that in the next installment.

Next article in this series:
Louder Doesn't Mean Better →

Would you like to comment this article?

Log in
Become a member
cookies
We are using cookies!

Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent
These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
Audience analysis (Google Analytics)
We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
Advertising (Google Ads)
This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.
Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

Our cookies
Cookies not subject to consent

These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

Audience analysis (Google Analytics)

We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

Advertising (Google Ads)

This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

Marketing (Meta Pixel)

On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


You can find more details on data protection in our privacy policy.
You can also find information about how Google uses personal data by following this link.