Audio normalization, often called loudness normalization, is the process of adjusting playback gain according to the measured loudness of a track, album, or program so different recordings play at a more consistent level. A streaming service or media player typically analyzes audio or reads loudness metadata, then applies a gain adjustment during playback. The source master is not normally rewritten simply to implement this playback adjustment.
This is why two songs mastered at very different levels can emerge from a playlist at a similar listening level, and why making a master louder does not guarantee that it will play louder on a streaming service. The exact result depends on the platform, the playback device, the listener’s settings, how the material is grouped, and whether the software is permitted to raise quiet tracks. Loudness normalization is not the same as normalizing an audio file in a DAW.
Table of Contents
What audio normalization does during playback
A playback normalizer needs three things: a measurement of the audio’s loudness, a reference playback level, and a rule for the gain change. In the simplest implementation, the service measures the integrated loudness of a track and compares it with its target. If the track is louder than the reference, playback gain is reduced. If it is quieter, the system may raise it, but only if the platform permits upward gain and can do so without unacceptable overload or additional processing.
Integrated loudness is commonly described in LUFS (Loudness Units relative to Full Scale), also called LKFS in some standards. Unlike a sample-peak measurement, integrated loudness is designed to represent the average loudness of a program across time. The calculation uses a defined measurement method, not the listener’s physical volume knob or the sound pressure level in a room. The measurement framework comes from ITU-R BS.1770-5; its K-weighting, channel weighting, gating, and measurement details belong in the separate article on loudness.
The basic gain calculation is:
Playback gain (dB) = Reference loudness (LUFS) − Measured loudness (LUFS)
For example, consider a purely gain-based system using a −14 LUFS reference:
- A master measured at −10 LUFS receives −4 dB of playback gain, ending at approximately −14 LUFS.
- A master measured at −17 LUFS would require +3 dB to reach the reference, but a real player might cap that boost to preserve headroom.
- A master measured at −14 LUFS needs 0 dB of compensation under this simplified model.
These are calculated examples of the gain rule, not claims that every service uses the same target or that every quieter master will be amplified. Equal integrated LUFS also does not mean that two pieces of music have identical tone, punch, short-term loudness, or subjective impact.
When is the gain applied?
A streaming service may measure a submitted master when it ingests the file, then store a loudness result or gain instruction. A player can read those values and adjust playback in its digital signal path. A local music player can do something similar using ReplayGain metadata that was analyzed beforehand. The source track and the playback gain are two different things, even when they ultimately reach the same speaker.
Some systems prepare compressed and lossless versions of a submission for distribution. That transcoding process is separate from loudness normalization. For example, Spotify explains that it analyzes submitted songs but applies loudness adjustments during playback and also processes supplied audio to create delivery formats. An artist should not interpret the phrase “normalization doesn’t alter your master” to mean a streaming service performs no other audio processing whatsoever.
Is normalization the same as turning down the volume?
A negative playback gain is mathematically a level reduction, but the important difference is how the gain is selected. A normal volume knob gives the listener control over the entire playback system. Loudness normalization selects a compensation from measurements, often separately for tracks or groups of tracks. The listener can still change the device volume afterward. A normalization target of −14 LUFS is not a command for an amplifier to deliver a fixed acoustic level in dB SPL.
Turn-down-only, turn-up, and peak-limited normalization
A service has to decide what to do with songs that are quieter than the reference. This is where descriptions such as “every track is played at −14 LUFS” become misleading.
Turn-down-only normalization reduces recordings above a reference but does not amplify recordings below it. This avoids introducing additional peak-overload risk through positive playback gain. Quiet masters may remain quieter than the nominal reference.
Bidirectional normalization allows both positive and negative gain. A quiet song can be boosted, provided there is enough room for its peaks or the player has another way to manage them. The result may still fall short of the reference if a headroom cap stops the boost.
Normalization with limiting can push some quieter, dynamic material closer to a louder reference by reducing peaks as needed. Once a limiter acts, the processing is no longer just a constant gain offset. It can affect transients and internal dynamics. The important technical distinction is between level matching and changing the waveform to meet two competing constraints.
A real example: why upward normalization can stop short
Spotify provides a useful documented example. Its creator documentation describes a track measured at −20 LUFS with a maximum true peak of −5 dBFS. Raising it all the way to a −14 LUFS target would require +6 dB, placing its existing peak above the desired headroom margin. Spotify instead describes raising this example only to −16 LUFS, preserving approximately 1 dB of headroom. The difference is not a malfunction: the requested loudness increase conflicts with peak safety. Spotify’s explanation illustrates why an integrated target cannot be discussed separately from true peak.

Spotify loudness normalization: the verified rules
Spotify is unusually explicit about the behavior of its playback normalization. Its Spotify for Artists documentation, checked October 31, 2026, states that the service uses −14 LUFS as its Normal playback reference and that it applies gain during playback rather than rewriting the supplied song to that level.
Spotify distinguishes the listening context. When an album is played as a coherent album, its tracks share a gain adjustment so the intended differences between the quieter and louder tracks remain. When a playlist combines material from different albums, or an album is shuffled, it can normalize tracks individually. That is a meaningful artistic distinction, not merely a different way of organizing the music library.
Spotify Loud, Normal, and Quiet
Spotify’s Premium settings document three options:
| Spotify setting | Documented playback reference | Practical significance |
|---|---|---|
| Loud | −11 LUFS | Intended for noisier listening environments; Spotify documents a limiter for dynamic material that needs peak control. |
| Normal | −14 LUFS | Default reference; positive gain is restricted by available headroom. |
| Quiet | −19 LUFS | Lower playback reference, useful where high overall playback level is unnecessary. |
These are playback reference settings, not mastering presets. Their availability and the setting location depend on the app and subscription. Spotify documents the Loud-mode limiter as engaging at −1 dB in sample values, with a 5 ms attack and 100 ms decay. That is a specific statement about Spotify’s Loud mode, not evidence that its Normal and Quiet modes apply the same limiting behavior.
Spotify also notes that its web player and third-party playback devices such as some TVs and speakers do not use Spotify loudness normalization. Consequently, a Spotify listening comparison is not automatically equivalent on the desktop app, browser player, receiver, and connected speaker. The documentation applies to compressed and lossless audio formats, but support depends on the playback path. A creator cannot reliably hear every possible consumer outcome by testing one Spotify client.
Should a Spotify master be exactly −14 LUFS?
Spotify’s mastering tips recommend targeting −14 LUFS integrated and keeping maximum true peak below −1 dBTP, with more conservative true-peak headroom for louder masters. Those are genuine platform recommendations. They are not an upload requirement that invalidates every master louder or quieter than −14 LUFS, and they do not supersede the musical goals of a release or the specifications of other distribution destinations.
A track mastered at −9 LUFS can be attenuated during Spotify playback. That does not mean the mastering engineer made a technical error simply by choosing −9 LUFS. It means the original gain advantage may not survive normalization. Conversely, mastering everything at exactly −14 LUFS does not guarantee a pleasing sound, a compliant peak ceiling, or comparable dynamics across different songs.
Apple Music Sound Check: what Apple actually documents
Apple’s playback-leveling feature is called Sound Check. Apple’s support documentation says it adjusts loudness between songs to reduce substantial level differences, and its Apple Digital Masters technical brief explains that loudness information can be stored as metadata and used to raise or lower playback level.
Apple also documents an album-aware possibility: Sound Check can preserve level differences between songs that were designed to be heard together. This is an important qualification to the familiar statement that streaming “makes every song equally loud.” Uniformity between unrelated songs and preservation of an album’s internal dynamics serve different purposes.
A commonly circulated estimate for Apple Music Sound Check is around −16 LUFS. However, Apple’s general consumer support and Apple Digital Masters technical brief do not present this as one universal, version-independent Apple Music playback target across all devices, formats, and settings. The widely repeated number is therefore not an official platform-wide guarantee. Apple’s podcast guidance does specify approximately −16 LKFS as a production recommendation, which is a different claim and belongs to the podcast section below.
How to find Sound Check
In current iPhone instructions, Apple places Sound Check under Settings > Apps > Music > Sound Check. On Mac, Apple documents the Music app > Settings (or Preferences) > Playback > Sound Check control. Other operating systems and output routes can differ. These locations come from Apple’s instructions, not from an assumed universal menu layout.
Apple Digital Masters is not a loudness target
Apple Digital Masters concerns the preparation and delivery of high-quality masters, encoder auditioning, and avoiding clipping. It is not another name for Sound Check and does not mean every release must be mastered to the same LUFS value. Apple’s technical guidance supplies tools such as AAC round-trip auditioning and clipping checks so an engineer can assess the effects of encoding while retaining creative control over loudness and dynamics.
YouTube: normalization versus Stable volume
YouTube needs an especially careful distinction because it has more than one type of audio-level adjustment.
Playback loudness adjustment refers to the player reducing the level of material that is louder than its reference behavior. Third-party investigations often estimate a reference around −14 LUFS for ordinary YouTube playback, but that estimate should not be presented as a fixed, universally published YouTube delivery requirement. The platform may change playback processing, and the result can vary by content type and playback path.
Stable volume, by contrast, is a user-facing feature that YouTube describes as continuously balancing variations between quieter and louder portions of a video. It is not simply a one-time gain offset for the whole track. YouTube says Stable volume is unavailable on some videos and is turned off for YouTube Music and official music videos. The two functions should not be conflated when judging a music master.
YouTube also provides a Stats for nerds diagnostic overlay in supported players. Its available fields and interpretation depend on the client, so displayed loudness information is useful evidence for a specific playback test, not proof that all YouTube content is measured, normalized, or delivered using exactly the same parameters. YouTube’s help page documents how to access the diagnostic information.
If a listener hears a dramatic change in transient behavior when toggling Stable volume, that says something about the optional continuous-level processing. It is not evidence that the uploaded master was destructively rewritten or that all other YouTube loudness compensation has stopped.
Other music platforms: what can and cannot be stated reliably
TIDAL, Amazon Music, Deezer, SoundCloud, Qobuz, Pandora, and various connected-device playback systems do not necessarily share one reference level, one default normalization mode, or the same behavior when playing albums. Their interfaces, firmware, and processing policies can change independently. Historical charts that assign a neat LUFS number and a true-peak “requirement” to every service often combine official documentation, third-party listening measurements, delivery recommendations, and speculation.
For a producer, the useful policy is not to rely on an unverified universal platform chart. Check the current destination-specific delivery specification, then preview the finished master using a relevant loudness meter, a true-peak meter, and, where feasible, the playback client in question. If the client or distributor supplies no public numeric rule, avoid inventing one. A mastering target derived from a third-party measurement is not automatically a platform requirement.
| Service or playback system | What official sources confirm | What they do not establish |
|---|---|---|
| Spotify | Official Normal, Loud, and Quiet references; album context; device caveats | That every device follows identical settings or that −14 LUFS is mandatory for upload |
| Apple Music | Sound Check loudness leveling and album-aware behavior in Apple’s technical documentation | A universal, officially guaranteed −16 LUFS target for every Apple Music client |
| YouTube | Stable volume’s purpose and exclusions; Stats for nerds availability | An official universal −14 LUFS upload specification |
| Other music services | Policies must be checked separately at the destination and device level | Unverified per-platform target numbers or claims that normalization is always enabled |
The distinctions above reflect official information checked October 31, 2026. They are not a substitute for rechecking platform documentation when preparing a release later.
Track normalization versus album normalization
The difference between track and album normalization matters whenever quieter songs are intentionally placed next to louder ones.
Suppose an album has a quiet interlude at −20 LUFS and a louder song at −10 LUFS. Their integrated loudness levels differ by 10 LU. Under an illustrative track-normalization system with a −14 LUFS reference, the interlude would receive +6 dB and the louder song −4 dB, assuming adequate peak headroom and no limiting. Both would then measure approximately −14 LUFS, eliminating the original level contrast between tracks.
With album normalization, one gain value is applied across the sequence. If the whole album requires −4 dB of compensation, the quieter interlude becomes −24 LUFS and the louder song becomes −14 LUFS. Their 10 LU separation remains. The album measurement and adjustment may follow a more complex algorithm than simply anchoring the loudest track; the point is that the same gain is applied to all tracks to preserve their relative levels.

Spotify documents this distinction explicitly for albums versus shuffled tracks and mixed playlists. Apple’s technical brief describes Sound Check’s ability to preserve album-relative levels. However, the choice of playback mode and the exact behavior can still depend on implementation and listening context.
Does album normalization preserve an album’s dynamic range?
It preserves the relative loudness differences between tracks when one constant gain applies to the album. That is not exactly the same claim as preserving every property of the signal. If downstream processing introduces limiting or dynamic-range control, individual transients and within-track dynamics can change. Keep the distinction between dynamics within a recording and loudness relationships between recordings.
What about shuffle and playlists?
A shuffled playlist needs to transition smoothly between unrelated masters, so individual-track adjustment is an understandable choice. A carefully sequenced album may depend on contrast, such as a quiet introduction followed by a loud full-band track. Album-aware normalization respects that intended relationship better. The listener’s playback context is therefore part of the engineering story.
What is ReplayGain?
ReplayGain is a metadata-based approach to estimating and compensating for playback loudness differences. David Robinson published the original ReplayGain proposal on July 10, 2001, with subsequent revisions that year. Its goal was already familiar: avoid repeated trips to the volume control when listening to recordings mastered at different levels. The original specification describes loudness analysis, gain metadata, and clipping prevention during playback.
ReplayGain distinguishes between track gain and album gain. The stored information may also include a peak value useful for checking whether an upward playback adjustment would exceed an available limit. A compatible player uses the metadata to choose playback gain; the metadata does not inherently require changing the PCM samples in the underlying recording.
Not every file format stores this information in the same way, and not every player honors the same metadata fields. Also, ReplayGain’s original loudness estimation method is not identical to the later ITU-R BS.1770 method. They share a purpose, not necessarily every measurement detail or reference level.
Does ReplayGain affect audio quality?
A gain adjustment implemented in a digital player can change the level and may require adequate numerical headroom. It does not by definition perform compression or destructive re-encoding. However, clipping prevention options, integer playback paths, limiting, and output-device behavior can change the practical result. A claim that ReplayGain is always perfectly transparent in every player would be too broad.
Broadcast standards and streaming delivery are not one system
Broadcast standards address program exchange, commercial transitions, loudness measurement, permissible peaks, and the conditions under which different programs are transmitted. Their recommendations are not interchangeable with music streaming playback references.
The measurement basis is ITU-R BS.1770-5, approved in November 2023. This ITU recommendation defines methods for calculating program loudness and true-peak level. It does not require Spotify, Apple Music, every television station, and every podcast player to use one identical LUFS target.
EBU R 128 in European broadcast workflows
The European Broadcasting Union’s R 128 recommendation, version 5.0 from November 2023, uses a nominal −23 LUFS program-loudness target. Its related production guidance discusses tolerances, maximum true peak, and situations such as live programs where practical compliance differs from a pre-produced file. The EBU has a separate R 128 s2 supplement for broadcast content delivered by streaming, because device headroom, background noise, and metadata-aware playback introduce different needs.
The existence of an EBU broadcast target does not imply that a piece of music must be mastered to −23 LUFS for a commercial music streaming service. The target belongs to a specific distribution and monitoring context.
ATSC A/85: the July 2026 revision matters
In the United States, ATSC A/85:2026-07 supersedes older versions of the recommended practice. Its Annex M quick reference uses a −24 LKFS reference for certain television delivery or exchange cases without loudness metadata and lists a −2 dBTP maximum true peak. It emphasizes that long-form material requires appropriate dialogue-based measurement and that metadata-based workflows are different.
Crucially, the new reference also discusses a −23 to −27 LKFS range for certain streaming-delivery services in its broadcast-oriented scope, unless trading partners agree otherwise. This is not the same thing as a Spotify, YouTube, or Apple Music music-playback target. Quoting the ATSC values without identifying the television-delivery context would create precisely the confusion loudness standards are intended to prevent.
Podcast delivery is another separate requirement
Apple Podcasts for Creators recommends preparing podcast content to approximately −16 LKFS, within ±1 LU, and keeping the true-peak value below its published ceiling of −1 dB FS, evaluated using BS.1770-5. The wording is a pre-encoding production recommendation, not evidence that every podcast host will normalize every episode to that number during playback.
This distinction also matters for audiobooks. An audiobook platform may validate the levels of submitted files and reject nonconforming assets. That is file delivery compliance, not the same operation as a music player adjusting gain while somebody listens. The precise limits depend on the distributor’s current contract and should be checked before delivery.
What loudness normalization means for mastering
The first mastering consequence is that playback gain can erase a master-level advantage. If two tracks are played under the same target and both are above it, the louder master is turned down more. The listener can still perceive differences in tone, punch, distortion, and dynamics, but the louder file does not automatically win because its integrated LUFS is numerically higher.
For example, compare a master at −8 LUFS with one at −12 LUFS. Under the illustrative −14 LUFS reference, one would receive −6 dB and the other −2 dB. Both would move toward the same integrated playback loudness, despite the four-LU difference in the supplied masters. The first recording’s compression or limiting, if any, was applied before normalization and is not reversed by turning it down.
Equal loudness does not mean equal punch
Transient contrast, spectral balance, arrangement, distortion, stereo image, and short-term loudness contribute to what a listener perceives. One master can feel more aggressive than another after integrated loudness matching, while another can feel less open or less impactful. The direction and size of that subjective difference cannot be established from integrated LUFS alone. Any claim that every highly limited master is always less punchy at equal LUFS would require additional listening or signal evidence, not an assumption.
In other words, playback normalization changes the level playing field, but it does not reconstruct dynamics removed by a limiter. A master that has already lost a transient cannot recover it merely because a service reduces the volume by 5 dB.
Did streaming normalization end the loudness war?
Normalization reduces the reward for making a master louder solely to stand out in a playlist. It does not erase the creative or commercial reasons some releases still use dense dynamics, strong saturation, or loud mastering. Streaming services are not every listening environment, normalization may be disabled or unavailable, and the same track might also reach radio, clubs, broadcast, local files, or social-media players. It is therefore too sweeping to say that the loudness war is definitively over. The better conclusion is narrower: in normalized playback, extra integrated loudness is less reliable as a competitive advantage.
True peak still matters after normalization
The highest stored digital sample and the highest reconstructed waveform peak are not necessarily identical. True-peak measurement estimates peaks that can occur between samples. Streaming encoding and later decoding can introduce additional peak behavior, so a positive playback gain may consume more headroom than a file’s sample peak suggests. The ITU true-peak guidance explains the measurement principle; Spotify publishes practical headroom recommendations in its artist documentation.
It is incorrect to say that every master reaching 0 dBFS must audibly distort during every playback, just as it is incorrect to guarantee that a 0 dBFS sample-peak ceiling is safe for every encoding and output path. Check the actual destination, codec, and true-peak requirements. Spotify’s recommendations for −1 dBTP and more conservative headroom on louder masters are useful examples, not universal standards for all delivery formats.
A reliable release-checking workflow
- Finish the mix and master for the music. Evaluate tonal balance, transients, fades, sequence, and intentional level contrasts before choosing a number to satisfy an upload checklist.
- Measure integrated loudness and true peak. Document both readings, along with the actual rendered format and channel layout. Neither reading replaces the other.
- Check the destination’s specifications. Distinguish required deliverable constraints from optional playback-target recommendations and from unverified third-party platform charts.
- Preview at matched playback loudness. When comparing masters, level-match them reasonably so a louder preview does not bias the decision. Then also check the actual delivery or service behavior where practical.
- Audition the encoded version where relevant. For AAC delivery, for example, Apple’s encoder auditioning tools help reveal clipping or changes that a source-file meter alone may not predict.
- Recheck the finished export. A limiter, resampler, final gain move, or encoder can change the values measured earlier in the chain.
The goal is a release that sounds intentional and meets its actual delivery constraints, not a number optimized to a screenshot of one app’s player.
Listener controls and why results differ across devices
For Spotify Premium listeners, Spotify’s current instructions locate volume normalization in the Playback controls on mobile, and in Audio Quality settings on desktop. Users can select Loud, Normal, or Quiet where available, or switch normalization off. Spotify notes that audio settings cannot necessarily be changed for playback routed through Spotify Connect to another device. The documentation also warns that the web player and some third-party devices do not use Spotify’s normalizer.
On Apple devices, the Sound Check toggle controls Apple’s loudness-leveling behavior in supported Music apps. Playback over different speakers or through third-party players is not proof of identical behavior in every listening path.
On YouTube, Stable volume can be toggled where supported, but that toggle should not be treated as a master switch for every other platform loudness adjustment. It is specifically an adaptive continuous-level feature, not simply album- or track-level gain compensation.
Should listeners leave normalization enabled?
For ordinary playlists that switch between unrelated songs, leaving playback normalization enabled usually makes listening more convenient. Listeners who want to compare original file levels, audit a master, or understand a device’s exact processing may deliberately turn it off when that option exists. Neither setting is universally more accurate as a way to compare artistic quality. The important point is knowing which mode was active during the comparison.
Does downloading music change the result?
Downloaded files can still be played through software that applies loudness metadata or gain compensation. Offline playback is therefore not inherently exempt from normalization. But actual behavior depends on the app, stored data, playback mode, and device. No general claim that all offline downloads behave identically to streamed tracks is warranted.
Audio normalization versus normalizing a file
The two concepts share the mathematics of gain but differ in who initiates the operation and what happens to the result.
| Question | File normalization in a DAW | Playback loudness normalization |
|---|---|---|
| Who initiates it? | Editor, producer, or automated file-processing workflow | Player, streaming service, or listener setting |
| When does it happen? | While editing or rendering a file | During playback, using analysis or loudness metadata |
| What sets the target? | Chosen file metric such as peak, RMS, or LUFS | Service- or player-defined reference loudness |
| Is the delivered master rewritten? | It can be rendered into new audio data | Usually no, not for the normalization gain itself |
| Can it change dynamics? | Pure constant gain cannot; optional limiting can | Pure gain cannot; playback limiting or dynamic processing can |
For detailed procedures in Audacity, Logic Pro, Ableton Live, REAPER, Pro Tools, and other editors, see Normalization. That companion page explains file processing rather than platform behavior.
Common mistakes about loudness normalization
“Every streaming platform wants a −14 LUFS master.” A reference used by one playback system is not an industry-wide file-delivery rule. Spotify publishes −14 LUFS as a reference and recommendation; other services and contexts require separate verification.
“Turning down a loud master fixes the compression.” Gain reduction makes the material quieter but does not restore previously removed peaks or re-create dynamics.
“A quieter master will always be boosted to the platform target.” Some systems may limit positive gain, turn down loud recordings only, or engage a limiter to manage overload. The final level depends on the actual implementation.
“Apple Digital Masters means mastering to −16 LUFS.” Apple Digital Masters is a delivery-quality program. Sound Check is a playback feature. Apple’s podcast loudness recommendation is a different context again.
“A playlist and an album are normalized the same way.” Spotify explicitly distinguishes them. Album-aware normalization preserves intentional level differences between songs by applying common gain.
“YouTube Stable volume is just its track normalization setting.” Stable volume is an adaptive level-balancing feature; YouTube states that it is disabled for YouTube Music and official music videos.
“Matching LUFS makes two masters sound identical.” LUFS is a useful loudness measurement, not a complete description of timbre, dynamics, distortion, arrangement, or listening preference.
Frequently asked questions
Does Spotify normalize every song to −14 LUFS?
Spotify documents −14 LUFS as its Normal playback reference, but headroom may prevent some quiet songs from being boosted all the way to that value. The web player and some third-party playback devices also do not apply Spotify’s loudness normalization.
What does Sound Check do on Apple Music?
Sound Check helps reduce playback loudness differences between songs. Apple’s technical documentation also describes album-aware behavior that can preserve intended level differences between tracks.
Is −14 LUFS required for Spotify or YouTube uploads?
No universal upload requirement follows from the fact that a service uses a playback reference. Spotify publishes −14 LUFS as mastering guidance, not proof that all other masters are rejected. YouTube’s exact reference should not be stated as a universal official requirement without a current primary source.
Can a quiet track be made louder by normalization?
Yes, if the player supports positive gain and there is enough peak headroom, or if it employs additional peak management. A player may cap the increase or leave the track below the reference.
Will normalization undo limiting or distortion?
No. Simple playback gain changes overall level. It cannot restore signal peaks that were already limited or clipped in the supplied master.
Should an album be normalized track by track?
Not if its track-to-track loudness contrasts are intentional. Album-aware normalization can apply one common gain value, preserving those relative levels. Some players choose individual normalization when songs are shuffled or added to playlists.
What loudness should a podcast have?
Follow the current destination requirements. Apple Podcasts recommends approximately −16 LKFS with ±1 LU tolerance and its specified true-peak ceiling for preconditioned audio. This should not be generalized into a universal playback rule for every podcast service.
Can I turn normalization off?
Often yes, in the relevant playback application’s settings, such as Spotify or Apple Music Sound Check. Some playback systems provide fewer controls, and one toggle may not disable every form of audio-level processing.