Use OBS Studio to send the radio programme and an audio-reactive visualiser to YouTube Live. The visualiser must listen to the same OBS source that carries the programme; a moving graphic alone does not confirm that viewers will hear the right audio.
Before building the scene, confirm that you have permission to retransmit the station and its music on YouTube. A feed that plays publicly is not, by itself, permission to rebroadcast it, and YouTube warns that licensed third-party material can still interrupt a live stream if the channel is not allowlisted.
The audio-to-visualiser workflow
The broadcast has three parts: an audio signal, an OBS scene and an encoder connection to YouTube. Your radio programme enters OBS through an audio source, the visualiser reads that source and turns its levels or frequencies into movement, and OBS sends the combined picture and sound to YouTube Live. The visualiser belongs in the scene as a video source; it does not replace the audio source or carry the programme to viewers on its own.
First identify where the radio audio actually exists. It might be playing in a browser or another application, coming from a receiver or mixer, or arriving through an audio device. There is no single routing choice that fits all of these. Choose an OBS source that can receive the signal in your setup, then watch the OBS mixer while the station is playing. You need to see the programme’s level change before you configure the visualiser.
Next create a scene with a background, station image or other permitted visual, the visualiser, and the programme audio. The important connection is explicit: select the OBS source carrying the programme as the visualiser’s input. If the visualiser listens to a microphone or desktop audio instead, it may react to room noise or system sounds rather than the radio. This workflow is for producing a live audio-and-video feed; it is separate from a looping video file or playlist workflow such as creating a looping YouTube Live stream with a playlist.
The local software route uses OBS on a computer that remains on, with its power and network connection available for the broadcast. YouTube also supports standalone hardware encoders, but neither an external interface nor a dedicated encoder is automatically necessary for a basic scene. Choose equipment based on the signal path you already have and the way you intend to operate. Changing the encoder does not change the rights checks: the station and relevant rightsholders must permit the intended use whichever route you choose.
Confirm permission before preparing the broadcast
Treat permission as a prerequisite, not a task to revisit only after YouTube raises a warning. Check with the station operator and the relevant music or other rightsholders that the material may be retransmitted to YouTube Live. Ask whether the permission covers the territories you intend to reach, the planned live use, and any saved recording or later playback. The answer depends on your circumstances; a playable stream does not establish those rights.
YouTube says it scans live streams for matches to third-party content, including another live broadcast. A match can lead to a placeholder and a warning to stop using the material. If it remains, YouTube may temporarily interrupt or terminate the stream. These are platform actions to plan for, not proof that a feed is licensed or that permission has been correctly arranged. Read YouTube’s live-streaming copyright guidance before proceeding, and check the current official guidance for your channel and content.
There is a further practical distinction between having a licence and avoiding an automated interruption. YouTube advises creators to ask the rights holder to add their channel to the Content ID allowlist when using licensed third-party material. YouTube also says a live stream may still be interrupted without that allowlisting, even if you have a licence or restrict the stream to territories where you own the relevant rights. Do not assume that permission automatically triggers allowlisting. Confirm with the rightsholder that the correct channel is covered, and retain the written response.
If you plan to archive the broadcast, ask about that separately. YouTube says Content ID claims on archived live streams are made after the stream ends if you choose to archive it. Live retransmission permission should not be taken to include recording and playback unless the terms confirm it. Decide whether the archive is enabled only after you have checked its coverage, including any intended later viewing or monetisation.
These checks are not interchangeable with choosing a quiet or less recognisable visual, changing the audio source, or using different streaming software. None of those steps grants permission. If the station cannot confirm the relevant rights and any allowlisting request, pause before scheduling a public broadcast and seek clarification from the appropriate parties.
Create or schedule the YouTube Live event
In YouTube Studio, open the Live Control Room and create a stream or schedule one for later. YouTube’s official guide to creating a live stream explains the control-room steps and the encoder information you will need. When YouTube presents the server URL and stream key, keep them available for OBS. A stream key gives access to your broadcast destination, so do not publish it or show it in a screenshot.
If live streaming has not been enabled on your channel before, YouTube says first-time enablement may take up to 24 hours. Allow for that process rather than arranging a broadcast around an assumption that the channel will be ready immediately. Check the channel’s current live access in Studio before you announce a time. Creating or scheduling an event does not itself start the encoder; OBS will send the programme when you connect it.
Set the event’s title, description, visibility and schedule to match what you are authorised to broadcast. If the radio programme contains material whose rights are limited by territory or use, do not treat a visibility setting as a substitute for checking the licence. Decide whether YouTube should archive the event based on the separate recording permission. Keep the event in the control room while you configure OBS so that you can compare its preview with the local scene before going live.
Add the radio audio source in OBS
Open OBS and choose the scene you intend to broadcast. Add or select an audio input that receives the station programme in your particular setup. The source might be an application or device output, an input from connected audio hardware, or another signal available to OBS. The right choice depends on how the station is being played and how the signal reaches the computer; do not select a source merely because it appears in the list.
Play the station and watch the OBS audio mixer. The meter for the intended source should move in time with the programme. If it stays still, the signal is not reaching that source. Check that the selected input is the one carrying the station, that the application or device is playing, and that the operating system has not muted or redirected it. Make one change at a time, then check the meter again so you can identify what fixed the route.
Listen to the output as well as watching the meter. A meter can show activity without telling you whether the correct sound is being sent, whether it is clear, or whether another source is mixed in. Use OBS monitoring or a local test recording in a way that lets you hear the actual broadcast mix. If you are also using a microphone or other audio, check whether it belongs in the scene; unneeded inputs can introduce room noise or duplicate sound.
Keep the programme source consistent through the next step. Name it clearly in OBS, such as “Radio programme”, so it is easy to distinguish from desktop audio or a microphone when selecting the visualiser input. A clear source name is a small safeguard against building a scene that looks active but follows the wrong signal.
Make the visualiser react to that source
Add a visualiser source to the scene and choose the OBS audio source carrying the radio programme in its settings. OBS provides scenes containing image and other sources, while visualiser plugins provide the audio-driven display. A Waveform resource listed on the OBS Project Forums offers displays including spectrum curves, bars, circular variants, meters and waveforms. Check its current resource page against your installed OBS release and operating system before installing it. Plugin requirements and compatibility can change.
After selecting the source, play the radio and watch the visualiser while the OBS meter moves. If the meter is active but the graphic is static, inspect the visualiser’s source selection and settings rather than assuming that the audio route is sound. If the graphic moves when the station is silent, it may be listening to a different input, system noise or another active source. The movement should correspond to the same programme that will reach viewers.
A visualiser is a design element as well as a signal check. Keep it readable against the background, leave room for any station identity or on-screen text, and avoid covering the picture with several competing elements. If you select a plugin, use its own documentation and check compatibility before installing; for example, the separate Live Audio Visualizer repository documents different display modes and states its OBS version requirement on the project page. Do not assume that a plugin built for one OBS release will work with another.
For a short station ident or still image behind the visualiser, add an image or other visual source to the same scene. Confirm that you have permission to use any logo, artwork or other image as well. The audio-reactive display makes the stream visually responsive, but it does not make an otherwise unauthorised image or audio track permissible.
Connect OBS and check meters and preview
In OBS, open the stream settings and choose YouTube as the service if it is available in your version. Enter or connect the server URL and stream key from the event’s Live Control Room, following the current YouTube and OBS instructions. Treat the key as private. If you use a scheduled event, make sure OBS is connected to the intended event rather than another stream destination.
Start the encoder connection from OBS and wait for YouTube’s preview to show the scene. Check three things separately: the expected source moves in the OBS mixer, the visualiser responds to that source, and the YouTube preview displays the intended picture and receives sound. A good local scene is not sufficient if YouTube has not received the signal. Likewise, a preview that looks right does not prove that the intended radio programme is audible.
Use a short private or otherwise appropriate test before a public broadcast. The OBS Quick Start Guide encourages testing for a few minutes rather than starting a first stream without a check. Listen to the test from a viewer’s perspective if possible, and confirm that the audio is neither absent nor accompanied by unwanted desktop or microphone sound. Check that the graphic follows the programme throughout a quieter passage as well as a louder one.
If the preview has no audio, return to the OBS mixer and verify the programme source and its routing before changing visualiser settings. If the audio is present but the graphic does not react, revisit the plugin’s source selection. If both work locally but the YouTube preview does not, review the encoder connection and the event selected in Studio. Changing one part at a time makes troubleshooting clearer than rebuilding the whole scene.
A local OBS workflow depends on the computer, power and network remaining available while it runs. A hardware encoder or managed approach may suit a production that needs a separate operating arrangement, but it brings its own compatibility and cost considerations. For this software path, check the practical operating plan as well as the scene: who will notice a disconnect, who can restart the broadcast, and what happens if the computer or connection needs attention? For background on the connection itself, see what RTMP ingest does.
Go live and monitor the stream
Once the preview, audio and visualiser have passed your checks, use the Live Control Room to start the scheduled event or confirm the live broadcast, as appropriate to the event flow. Keep OBS and YouTube Studio open so you can see whether the encoder is still connected and whether the control room reports a problem. Do not leave the first minutes unattended: check that the programme continues to reach the stream and that the visualiser remains tied to it.
Monitoring should include the sound, not just the picture. A browser tab can stop playing, a device can be muted, or the audio source can change while the image continues. If the OBS meter goes quiet, check the station playback and input route. If the station continues but the visualiser freezes, check its selected source. If YouTube reports an interruption or third-party-content warning, follow the current notice and address the rights issue; do not treat repeated reconnection as a way around a rights match.
For an extended broadcast, decide in advance how someone will respond if OBS, the computer or the connection stops. A local encoder cannot keep sending the scene when the computer is switched off. If you expect an unattended or 24/7 operation, compare that requirement with this local workflow rather than assuming a short successful test proves overnight reliability. A test before you go live can reveal routing and preview problems, while keeping a playlist playing after an OBS reconnect concerns a different recovery case and does not remove the need to monitor the radio source.
If you retain the archive, check that the final recording contains the programme and scene you intended, then watch for any post-stream copyright notices in Studio. If you do not have recording permission, do not assume that the archive is harmless simply because the live transmission was authorised. Make the live-versus-recorded decision before broadcasting, based on the terms you have confirmed.
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 I add any radio station stream to OBS?
OBS can receive audio that is available to your computer or connected equipment, but technical access is not permission to retransmit it. Confirm the station and relevant rightsholders allow your intended YouTube use, and check whether channel allowlisting is needed.
Why does the visualiser move but viewers hear nothing?
The visualiser may be listening to a source that is not the programme audio being sent to YouTube. Verify the programme source in the OBS mixer, select that same source in the visualiser, and check the YouTube preview or a test from a viewer’s perspective.
Does a music licence guarantee that YouTube will not interrupt the stream?
No. YouTube says licensed third-party content may still interrupt a live stream if the channel is not on the rightsholder’s Content ID allowlist. Ask the rights holder about allowlisting and check YouTube’s current guidance.
Can I keep the live stream as a recording?
Only if your permission covers the recording and later playback as well as the live transmission. YouTube says Content ID claims on archived live streams are made after the broadcast ends when the creator chooses to archive it.