A clipped radio stream usually starts before YouTube receives it. Trace the audio from the player or mixer through the interface and OBS, then lower the gain at the first stage that overloads.
Use OBS's limiter only as the last protection for the stream mix. It can catch peaks that escape your normal settings, but it cannot repair distortion already created by an overloaded source, interface input, or earlier software filter.
Map the radio-to-YouTube signal path
Treat the audio as a chain rather than as one YouTube setting. A typical radio-style live stream has this path:
radio files or live input → player or automation software → mixer or interface → operating-system input → OBS source → OBS filters and fader → OBS final mix → encoder → YouTube
Some setups are simpler. You may play a playlist directly in OBS, use a USB microphone or mixer, or feed a completed programme mix from another computer. The names change, but the diagnostic question stays the same: where does the waveform first become too large?
An overload at one stage is passed to the next stage as damaged audio. If the radio automation output is already clipped, reducing the OBS fader makes the damaged signal quieter but does not make it clean. If the interface input clips while its digital signal is being created, no setting in YouTube can reconstruct the missing peaks.
This is why the final OBS meter is useful but not sufficient. It tells you about the level reaching that point in the chain. It does not prove that an earlier input, plug-in, mixer bus, or software player was operating cleanly.
Draw the path for your own station on paper. Include every gain control, such as a player volume setting, mixer channel trim, interface input knob, operating-system input level, OBS source volume, filter gain and mixer fader. If two applications are routing audio through a virtual device, include that device as another checkpoint.
For an always-on channel, also note which controls affect every route. A mixer master may feed headphones, a local recording and OBS at the same time. An OBS fader may affect only the YouTube output. That difference matters when choosing where to correct the level.
If your wider setup includes a long playlist or rotating programme, keep the audio path documented alongside the video schedule. The guide to scheduling different videos on a 24/7 YouTube livestream covers the content side, but the same principle applies: know which part of the chain is responsible for each job.
Recognise clipping rather than another audio fault
Digital clipping happens when a signal reaches the available ceiling and peaks are cut off. On a radio stream, it may sound like a harsh crackle on drum hits, a gritty edge on music, or a voice that becomes flat and brittle when someone speaks loudly. It is often most obvious on a transition, station ident or live microphone segment because those moments can be louder than the normal programme.
A clipped signal may remain distorted even after you turn it down later. That is the key difference between clipping at an early stage and a final mix that is simply too loud. The later control changes level, not the shape of peaks that have already been cut.
Not every unpleasant sound is clipping. A loose cable can produce crackling or intermittent noise. Electrical interference may create a hum or buzz. A poor microphone position can cause breath noise, plosives or room reflections. A sample-rate or routing problem may produce clicks, dropouts or speed changes. A codec or network problem can create interruptions without the source itself being clipped.
Use timing to separate these faults. If distortion follows only loud musical peaks or loud speech, investigate levels. If it appears when a cable moves, investigate the physical connection. If the local recording is clean but the remote playback is not, compare the encoder output, stream health and playback path rather than immediately changing source gain.
Listen to the same short passage at several points in the chain where that is possible. A local recording from the mixer, an OBS recording and the YouTube preview can reveal where the sound changes. Use the same loud passage for each comparison. Quiet background music will not expose a peak problem that a station ident or presenter microphone does.
The digital ceiling is expressed as 0 dBFS. OBS's audio mixer guidance says streamed and recorded audio should remain below that ceiling because peaks at or above it can cause clipping distortion. Do not use a meter that is merely close to the top as proof that you have comfortable headroom. OBS also explains that its peak meter behaviour can indicate a peak higher than the displayed reading, so leave room rather than aiming at the ceiling.
Check the source and interface first
Start the test with representative radio material. Play the loudest music you normally use, a station ident, a transition between tracks and any live microphone segment. If your channel carries devotional programmes, local announcements or talk between songs, include the loudest of those parts rather than testing only a quiet bhajan or ambience bed.
Watch or listen at the radio player and mixer before making changes in OBS. Check the player or automation output, each relevant mixer channel and the master output. If the mixer has a channel trim or input gain separate from its fader, adjust the trim carefully. A fader position that looks moderate does not guarantee that the input stage is receiving a sensible level.
Then check the audio interface. An interface input knob controls how strongly the analogue signal is converted into the computer's digital signal. If that conversion overloads, lowering the level in OBS cannot undo it. Reduce the interface input gain and repeat the loud passage. If the interface has a signal or peak indicator, use it as an additional clue, but still verify the sound in a recording.
If the source is coming from a phone, another computer or a mixer output, check the output level of that device as well. A high output from the source combined with a high interface input can overload even when either control looks reasonable on its own. Make one change at a time and note what it affects.
The first useful correction is usually upstream gain reduction. Lower the earliest control at which the signal is clearly excessive, then listen again at the next checkpoint. This preserves more headroom for every stage that follows. It also avoids asking a later limiter to reduce every normal musical peak.
There is a trade-off. Lowering the source may make the programme quieter relative to other material, while leaving it high and relying on a limiter can create frequent gain reduction. For a station with uneven files, correct obviously hot files or source feeds where practical, then use the final limiter for occasional unexpected peaks.
If your computer is doing more than one job, avoid adding extra gain simply because the monitoring level feels low. Headphone volume is not the same as signal level. Set monitoring volume for your ears, but diagnose the signal using the source, interface and software meters.
Inspect OBS on the loudest material
Once the physical and source stages are behaving, open OBS and inspect each relevant source. Play the same loud material while watching the source meter and the final audio mixer. Look for a source that reaches the ceiling before the final mix does, and check whether the final mix becomes excessive when two sources overlap.
A radio channel may have more than one active source. For example, a music source can continue underneath a microphone, an alert or a short video. Each source may be acceptable alone while their combined mix overloads. Test the combinations that occur during normal operation, not just each source in isolation.
Check the OBS source volume and every filter that can add gain. A filter, plug-in or processing stage can change the level after the original source has entered OBS. If the level indicator appears healthy but the recorded sound is distorted, temporarily disable filters one at a time and repeat the test. This helps distinguish an overloaded incoming signal from processing that is adding gain later.
OBS's input indicators and mixer meters describe particular points in the software path, so do not assume that one green or yellow meter represents every stage. Observe the relevant source, then the final mix. Record a short sample if your ears and the moving meter disagree.
Keep the programme running for long enough to reach an actual loud section. A music file may begin quietly and become much louder at the chorus. A presenter may speak normally for several minutes before raising their voice. For an overnight channel, inspect transitions, because a player fade, ident or live input can briefly combine with another source.
Do not chase a particular colour or number as a universal loudness target. The important result is clean audio with room below the digital ceiling, not a meter that is as high as possible. The documented OBS values and YouTube delivery recommendations serve different purposes from your station's creative loudness choice.
If OBS itself is stable but the computer or connection is not, keep the issues separate. A guide to YouTube Live dropped frames and encoder settings can help with delivery symptoms, but dropped frames are not a reason to raise audio gain or to treat clipping as a network problem.
Lower gain at the earliest overloaded stage
When you find the first stage that overloads, reduce gain there and test forward again. Suppose the mixer output is already harsh before it reaches the interface. Lower the mixer channel trim or master feed, depending on which part is excessive. Suppose the interface input is the first point that clips. Reduce its input gain. Suppose the source reaches OBS cleanly but a filter raises it too far. Correct that filter or source setting.
The choice of control should match the location of the fault:
| First overloaded point | Practical correction | Why it is the right first move |
|---|---|---|
| Player or automation output | Reduce the player output or correct unusually hot files | Prevents an excessive signal entering the rest of the chain |
| Mixer channel or bus | Lower channel trim, bus level or feed level | Stops the mixer from passing a clipped or unnecessarily hot feed |
| Audio-interface input | Reduce the input gain | Prevents overload during analogue-to-digital conversion |
| OBS source or filter | Reduce source gain or remove added gain | Corrects the software stage without hiding an earlier fault |
| Final OBS mix | Lower the relevant fader or source combination | Leaves more room when multiple clean sources are combined |
The table is a troubleshooting order, not a rule that every control must be low. A source may need a healthy level for noise performance, while a mixer or interface provides the correct place for adjustment. Follow the signal and confirm the result by listening.
Avoid lowering only the final OBS fader when an upstream meter or recording is already distorted. That makes the output quieter but preserves the distortion. Similarly, avoid raising other sources to match a clipped source. Bring the hot source down, then decide whether the overall programme needs a modest level adjustment.
When audio comes from a consumer device, its volume control can be a useful upstream adjustment, but its scale is not a calibrated measurement. Make a small change, repeat the same loud passage and check the next stage. Record the final setting so another operator does not restore the old level during a restart.
For a station with frequent changes between music and speech, upstream correction may not be enough to handle every unexpected peak. That is where a limiter has a role, after the normal gain structure is clean.
Add a limiter last as a safety net
In OBS, add the Limiter filter to the relevant source or mix and place it last in that filter chain. OBS documents the limiter as a control that prevents peaks above its threshold from causing clipping and distortion. Its documented default is a threshold of -6.00 dB and a release of 60 ms.
Those are software defaults, not a universal target for every radio channel. A threshold lower than the ceiling gives the limiter room to catch a peak, but it also means the limiter may reduce gain more often. If it is working constantly, the source or mix is probably too hot or too uneven. Go back upstream rather than treating continuous gain reduction as normal operation.
Release controls how quickly the limiter stops reducing gain after a peak. A short release can recover quickly but may be more noticeable on some material. A longer release can keep gain reduced for longer. Use the documented default as a starting point, then listen to representative music and speech. The right result is clean, stable audio without obvious pumping or flattened transitions.
A limiter is not a repair tool for clipping that has already happened. If the radio player, mixer, interface or an earlier filter has cut off peaks, placing a limiter later only limits the already-damaged waveform. It can stop new peaks in the later mix from crossing its threshold, but it cannot restore information removed earlier.
Place the limiter after other filters that may change level. If you put gain or processing after the limiter, that later stage can create new peaks beyond the protection you intended. Recheck the order whenever you add a filter, change a source or copy settings to a second scene.
Use the limiter as a final safety net, not as permission to run every source at maximum level. For a small station, correcting gain upstream and using OBS's built-in limiter may be enough. A hardware compressor or limiter can be considered when peak control is specifically needed before the computer, but it is not required simply because a stream is always on, and it cannot undo upstream clipping either.
Separate YouTube delivery settings from level control
YouTube's live encoder guidance lists AAC or MP3 for audio, stereo at 44.1 kHz and a stereo audio bitrate of 128 Kbps for the documented RTMP or RTMPS settings. Check the current YouTube encoder settings guidance before configuring a new encoder because platform documentation can change.
These are compatibility and delivery settings. They do not repair a source that was clipped in the radio player, interface or OBS. Changing the audio bitrate can alter how the encoded programme is delivered, but it does not recreate peaks that were cut off before encoding. Changing the sample rate is not a substitute for correcting gain either.
This distinction prevents a common loop of unhelpful adjustments. If your local OBS recording is harsh on loud passages, fix the signal path. If the local recording is clean but YouTube playback has a different fault, compare the encoder output, stream health and playback path. Do not use a codec setting as the first response to a meter that is already reaching the ceiling.
YouTube also recommends pretesting and monitoring the live event. Its streaming tips advise checking the stream before going live and continuing to watch it during the event. That is particularly important for radio-style channels because the loudest content may occur hours after the initial setup.
Test the complete path before going live
A full-path test should use the same routing, OBS scene, filters, encoder settings and programme type as the real broadcast. Do not test a spare scene with one quiet file and assume it represents an overnight devotional, music or local-news loop.
Use this sequence:
- Play representative material, including the loudest music, transitions, IDs and speech.
- Listen and inspect the player, mixer and interface before OBS.
- Watch each relevant OBS source meter and the final mix.
- Confirm that the limiter is last in the intended filter chain.
- Make a short local recording and listen to the loud sections.
- Check the encoder preview or test output, then compare it with the local recording.
- If available, listen to the YouTube playback from a separate device or connection.
- Repeat after any change to routing, filters, scenes or source files.
Keep notes about what you changed. If reducing the interface gain solved the distortion, write down the new position or setting. If a particular file is hot, identify it in the playlist or replace it. A written test record is more useful at two in the morning than relying on memory.
If the local recording and encoder output are already distorted, trace the source routing and gain again. If they are clean but the platform playback is not, investigate the outbound path and platform diagnostics. YouTube's troubleshooting guidance for live streams recommends comparing the encoder output and local archive when investigating bad sound, along with checking routed sources and encoder health.
Once live, keep someone listening during the periods most likely to change: scheduled handovers, microphone inserts, advertisements, live announcements and playlist transitions. A stream that sounded clean at launch can clip later when a different source becomes active. If no one can monitor continuously, at least arrange checks around known changes and keep a local recording running where practical.
If operating the stream from a computer overnight is itself the weak point, consider whether a hosted workflow better fits your routine. The article on using a hosted video streaming service instead of a 24/7 streaming PC explains the operational trade-off. Whatever method you choose, clean source gain and a tested final mix still matter.
For a simpler YouTube-only workflow, StreamNeo removes the need to leave your computer running after you upload the prepared video and connect the channel, while you still need to verify the audio in the file before starting the broadcast.
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
Can YouTube bitrate settings stop radio audio clipping?
No. Codec, sample rate and bitrate settings affect delivery and compatibility, not distortion already created by an overloaded source or input. Correct the first overloaded stage, then use supported YouTube encoder settings for the clean signal.
Should I lower the OBS fader when the source is already distorted?
Not as the main fix. A lower fader reduces volume after the distortion has occurred, so the clipped waveform remains damaged. Find the earliest overloaded player, mixer, interface or filter stage and lower gain there.
Where should the OBS limiter go?
Place it last in the relevant software filter chain so later filters do not create new peaks beyond its protection. It is a final safety net for the stream mix, not a way to restore audio clipped earlier in the chain.
What should I test before leaving a 24/7 stream unattended?
Use the actual routing and representative programme material, including the loudest music, speech and transitions. Check the source and OBS meters, make a local recording, compare the encoder or preview output, and monitor the live stream during the event where possible.