For a 24/7 YouTube music radio stream, put loudness control in the audio chain before the live encoder. Measure integrated loudness and true peaks, then listen to transitions between representative tracks; no single setting can make every playlist sound even.
You can process a changing playlist live in one pass, or prepare a stable music library offline in two passes. Broadcast standards help you choose a reference, but they are not evidence of a YouTube live-stream requirement.
Why normalise a continuous music stream
A playlist assembled from different albums, sources or eras can vary substantially in perceived volume. One track may sound forceful while the next seems quiet, even if their sample peaks look similar. Loudness normalisation helps bring programme level into a more consistent range so that listeners are less likely to reach for the volume control each time a song changes.
This matters particularly when a channel runs unattended. A person listening while studying or working may leave the stream on for a long time; sudden level jumps can be more disruptive than a small difference between individual tracks. A devotional playlist that moves between a softly recorded bhajan and a densely mastered recording is one example. The useful goal is a listenable sequence, not making every song equally loud at every moment.
Normalisation has limits. It does not remove clipping already present in a source file, guarantee that encoding will never create a peak problem, or repair an abrupt edit between tracks. Nor does it make quiet and loud passages within a song identical. It adjusts level according to a measurement model; dynamics and transitions still need judgement.
First decide whether you are treating individual files or the stream as a whole. If the playlist is fixed, file preparation gives you a chance to analyse every track before broadcast. If tracks enter dynamically or you change the playlist often, a live processor can respond as material passes through. The two approaches solve different operational problems, and neither is automatically best for every station.
Put loudness control before the encoder
The processing order is important: audio source, loudness processing, then the live encoder. That way, the encoder receives the adjusted signal. If you measure or process only after the final encode, you may discover an output problem without being able to correct it in the actual signal path.
For a computer-based setup, the relevant point is wherever the audio is mixed before it is sent to YouTube. If you use OBS, check the audio source and filters in the chain rather than assuming the mixer display alone tells you perceived loudness. OBS describes its mixer meter as a sample-peak programme meter; its VU display is an RMS measure over 300 ms, not an integrated LUFS reading. See the OBS audio mixer documentation and use a loudness-aware meter or analyser for LUFS work.
Make sure the processor receives the same programme audio that will be encoded. If the music passes through a separate mixer, virtual cable or playback application, placing a filter on the wrong source will not affect the broadcast. Verify by listening to the outgoing programme and, where practical, analysing the encoded output rather than relying only on a pre-encoder meter.
There is a trade-off between preparing files and adding live processing. Offline preparation reduces what must be done during broadcast, but it takes library management and rework when source files change. A live processor accommodates changing input, but it is part of the real-time chain and should be monitored as such. For more on choosing a continuous playback arrangement, see how to make a 24/7 YouTube music stream with OBS in India.
Measure loudness and true peaks
Integrated loudness and true peak answer different questions. Integrated loudness estimates perceived programme level over time, commonly expressed in LUFS. True peak estimates the highest reconstructed waveform level, including peaks that can occur between digital samples. A track can have a moderate integrated loudness and still contain a high peak; one reading cannot stand in for the other.
Use a loudness-aware meter or analyser that reports integrated loudness and true peak. Do not infer LUFS from the height of OBS mixer bars. A meter that shows only sample peaks can help identify a level approaching the digital ceiling, but it will not tell you how loud the whole programme sounds on average. The EBU publishes a loudness metering specification, which is useful background on what proper loudness measurement involves.
Also distinguish the signal level before encoding from the level after it. OBS warns that its output should remain below 0 dBFS, the digital maximum, because output above that point clips. That is an output ceiling concept, not a recommended integrated loudness target. Leave headroom rather than setting a processor so aggressively that ordinary variation pushes the signal into clipping.
A sensible check uses more than one track. Include material that is quiet, dense, dynamic and strongly peaked, and listen at the joins. Record the processor settings and the loudness and peak readings you observe. If peaks approach the ceiling or one transition sounds conspicuously uneven, revise the settings and repeat the check. A meter can reveal a risk; listening helps identify whether the result serves the programme.
Use FFmpeg loudnorm for live single-pass processing
FFmpeg's loudnorm filter supports single-pass operation for livestreams and double-pass operation for files. The single-pass mode is intended for material passing through continuously: the processor works on the audio as it arrives rather than first analysing a complete file. Consult the FFmpeg loudnorm filter documentation for the filter's parameters and current behaviour.
Before configuring it, choose an operating target for your own programme and a maximum true-peak target appropriate to your source and encoding chain. loudnorm exposes controls for integrated loudness, loudness range and maximum true peak. Those controls are not a recipe that can be copied blindly: a highly varied devotional playlist and a tightly mastered lofi station may need different treatment. Start from a considered reference, then assess the actual output.
In single-pass use, the processor does not have a complete advance analysis of the entire programme. That makes it practical for a live-changing playlist, but it is not equivalent to measuring every track and preparing files individually. Test a representative sequence that includes the quietest and loudest material you expect to play. Listen through the start of songs as well as the middle: a level change that seems reasonable on a long average may still be noticeable at a transition.
Keep a copy of your working command or filter settings and document the target you selected. Change one relevant setting at a time when diagnosing the sound; if you alter target loudness, range and peak ceiling together, it becomes harder to identify what improved or worsened the result. For an unattended channel, the operational burden is not only choosing a filter but knowing that it is applied to the correct audio path after a restart.
If the live chain is the fragile part of your setup, removing dependence on a home computer can address a separate continuity problem: StreamNeo takes an uploaded video and runs it as a 24/7 YouTube broadcast, so the computer can be off while the channel continues. That does not choose your loudness target or replace checking the programme audio before it goes live.
Prepare files with a two-pass workflow
When the library is stable, a two-pass workflow can give you more control. In the first pass, analyse a file to gather loudness and peak measurements. In the second, process it using those measured values and the chosen settings. FFmpeg documents this double-pass mode alongside its single-pass livestream mode, so you can use the same filter family for different jobs.
The main benefit is advance knowledge: you can inspect how each file relates to your intended programme level before it enters the live playlist. This is useful when a station repeats a carefully curated set of tracks or when you have time to prepare an album or batch in advance. It also makes it easier to find source files that are unusually quiet or have problematic peaks.
Preparation has a cost. If you replace a track, edit a file or switch to a new playlist, the processed copy may no longer reflect what you intend to broadcast. Maintain a clear distinction between original and processed assets, and make sure the live playlist points to the right version. Avoid repeatedly processing already processed files without a reason; each conversion step can complicate troubleshooting and may alter the sound.
Do not assume that matching each song to one integrated number will create seamless albums. Track-to-track relationships may be intentional: a quiet introduction, a pause, or a deliberately softer devotional passage can be part of the programme. Decide whether your station should preserve those contrasts. Normalisation is a level-management tool, not an instruction to erase musical dynamics.
Offline preparation is not compulsory. If files are added by another person or the playlist changes at short notice, live single-pass processing may be easier to maintain. If files are known and repeatable, analysis ahead of time can reduce guesswork during operation. The choice is about where you want the work and checking to happen.
Check transitions across representative tracks
A 24/7 station is heard as a sequence, so evaluate the joins as well as the tracks. Put together a short test playlist containing the quietest material, the loudest material, a track with pronounced dynamics, and songs with different recording or mastering styles. Listen at a normal playback level, not only while watching meters. Pay attention to whether the next song seems to leap forward or recede, whether a fade changes level unexpectedly, and whether silence or overlapping fades behave as intended.
Check several kinds of transition: a direct cut, a crossfade if you use one, and any hand-off between playlists or playback sources. Loudness processing cannot fix a badly timed edit or a gap caused by the player. If a transition is abrupt, the cause may be the playlist or edit rather than the loudness setting. Keep those diagnoses separate so you do not over-process the entire channel to compensate for one awkward join.
Listen for dynamics within songs too. A processor that makes perceived level more consistent can still leave verses and choruses distinct; that is often desirable. If the quietest passages become hard to hear or the louder sections lose their impact, reconsider the target, range setting or source material. The right result depends on how the channel is meant to feel and the conditions in which people listen.
Finally, review the actual encoded stream or a recording of its output. Processing, mixing and encoding form one chain, and the final signal is what your audience hears. Note the observed integrated loudness and true peak, together with the tracks used for the check. That record gives you a baseline when you later change the playlist, encoder or source application. For broader continuity issues, troubleshooting a YouTube RTMP stream that drops after encoder changes can help keep audio testing separate from connection problems.
Treat standards as context, not YouTube requirements
A published standard can provide a defensible starting point, but it does not answer every platform-specific question. The European Broadcasting Union's EBU R 128 version 5.0 lists an average programme loudness recommendation of -23 LUFS. Its companion streaming recommendation, EBU R 128 S2 version 3, describes a baseline in which programmes are streamed unchanged at -23 LUFS. These are EBU recommendations, not a verified numeric target for YouTube live music streams.
EBU R 128 S2 also discusses a different distribution situation: where metadata is not used to manage device gain and content dynamics, and a broadcaster wants to control dynamic treatment before streaming, it allows an interim distribution loudness above -23 LUFS, in the -20 to -16 LUFS range. That is conditional context, not an instruction to set every music channel within that range. The listening environment, programme dynamics and editorial intent matter.
The research available for this article did not establish an authoritative YouTube statement specifying a current loudness target for continuous live streams or explaining whether the platform normalises them in a particular way. Do not treat a number repeated in forums or general advice as a YouTube rule without an official source. Check current YouTube Help for live streaming for platform guidance, and keep your own audio measurements distinct from any platform processing you cannot verify.
A practical choice is to state what informs your settings: for example, a broadcast reference, preservation of the source dynamics, or a listening test across your own playlist. Record the choice and revisit it when the programme changes. Do not select a number merely because it is familiar, and do not raise levels until peak headroom becomes an afterthought.
For related planning around continuous playback, see how to stream a church hymn playlist continuously on YouTube Live. It is a useful reminder that the audio chain sits within a wider operation: the files, transitions and unattended playback all need to work together.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does YouTube require a particular LUFS target for a 24/7 live stream?
This research did not verify an official YouTube numeric target for continuous live streams. Treat EBU figures as broadcast context, not a YouTube requirement, and check current official YouTube guidance rather than relying on repeated third-party claims.
Should I use single-pass or two-pass loudness normalisation?
Use single-pass processing when audio changes dynamically and must be handled as it arrives in the live chain. Use a two-pass workflow when you can analyse and prepare a stable set of files ahead of broadcast; the choice depends on your playlist and how much library maintenance you want.
Is the OBS meter enough to measure LUFS?
No. OBS documents its mixer display as a sample-peak meter, with a VU display based on RMS over 300 ms, rather than integrated LUFS. Use a loudness-aware analyser for LUFS and true-peak checks, and treat the OBS output ceiling as a separate clipping check.
Will loudness normalisation prevent clipping or rough transitions?
No. It can help manage perceived level, but it does not remove clipping already in a source or guarantee that encoding will not introduce a peak problem. Listen to transitions and inspect output headroom as separate checks.