To send a Winamp radio playlist to YouTube Live with OBS, play the playlist in Winamp, capture its audio in OBS, then send OBS’s stream to YouTube using the stream URL and key from YouTube Studio. Check the Live Control Room preview and listen to the result before you make the broadcast public.
This setup carries the sound Winamp is playing into an OBS broadcast; it does not set up a SHOUTcast server. You can capture Winamp directly on supported Windows systems, or capture the audio output device that Winamp uses if application capture is unavailable or does not work with that audio path.
What a Winamp playlist contains
A playlist is an ordered set of items for Winamp to play. It might contain local tracks, internet radio entries, or other media resources. Winamp’s playlist help describes the playlist as a way to organise and order media; it is the playback sequence, not by itself a broadcast to YouTube.
That distinction matters when you say “radio playlist”. You might mean a list of songs that Winamp plays in order, or a list of internet radio stations or streams that Winamp opens. In either case, the practical chain is the same: Winamp plays the selected items, Windows outputs the resulting sound, OBS captures that sound and encodes the live programme, and YouTube receives the OBS feed.
A playlist does not grant rights to the recordings or station streams it contains. YouTube says live streams are scanned for third-party content. A match can affect the broadcast, and even licensed material may need the rights owner to allowlist the channel through Content ID. Check that you have the necessary permissions for every item, and consult YouTube’s current guidance rather than relying on a public, unlisted, or private setting as a substitute for rights.
This is also different from operating a SHOUTcast server. A server-based internet radio setup distributes a station feed to listeners through its own radio-streaming arrangement. Here, Winamp is simply the player, OBS is the encoder and YouTube Live is the destination. You do not need to create or configure a SHOUTcast server to follow this guide.
If the playlist is intended to run for long periods, check how it behaves at the end of its queue. Confirm whether Winamp repeats it, advances to the next entry, or stops, and test that behaviour before scheduling a long broadcast. The aim is to know what the source will do unattended, not to assume that an ordered list automatically loops.
Prepare the playback and scene
First load or create the playlist in Winamp. You can use its Playlist Editor or Media Library, depending on your version. Start playback and confirm that you can hear it through the Windows output device you intend to use. Winamp’s help documents DirectSound Output as a normal playback option in the versions it covers, but its legacy controls may not match every current build. Use the output setting available in your own installation and verify the sound rather than assuming it is routed correctly.
In OBS, create a scene for the broadcast. A scene can include an image, text, a captured window or other visual sources. If viewers should see a station name, devotional artwork, a schedule, or a simple still image while listening, add that visual and check its framing. A music playlist does not require a visualiser; choose a presentation that suits your channel and that you have permission to use.
Keep the first scene straightforward. A still image and a clear station title are easier to inspect than several moving sources. Check that the title remains readable at the size YouTube viewers are likely to see, and that any image is not cropped unexpectedly. If you want a playlist-driven visual presentation rather than a single still, test that as a separate part of the setup before adding it to an unattended broadcast.
For a broader comparison of continuous video playback approaches, see this guide to streaming an FFmpeg playlist with a static image. FFmpeg is a different playback route; it is not required when Winamp is already playing the audio you want.
How Winamp audio gets into OBS
OBS must receive the sound from Winamp as an audio source. The source can be the Winamp application itself, where supported, or the output device carrying its sound. The difference is selectivity: an application source aims to capture one programme, while an output-device source captures sound from that device and can therefore include other applications using it.
Before configuring capture, note which output device Winamp is using. If you switch headphones, speakers, or Windows output devices later, OBS may still be listening to the old route. The visible Winamp playback indicator does not prove that OBS is receiving the same audio. Watch the OBS audio meter while a track is playing, then listen to the resulting preview as a separate check.
OBS’s Application Audio Capture guide documents per-application audio sources for OBS Studio 28 and later on Windows 10 version 2004 or later, and Windows 11. That does not mean the feature is available on every system or compatible with every audio path. If Winamp does not appear as a selectable application, or the meter remains silent, use the output-device fallback described below.
Choose one primary route for Winamp’s sound. Capturing the application and also capturing the same output through Desktop Audio or a device source can send the signal twice. Depending on the setup, that can sound like an echo or create a doubled level. The goal is one clear route from the player into the OBS mix.
OBS capture is not a Winamp-specific compatibility guarantee. If the meter is silent, check in order: Winamp is playing, its selected output is the one you expect, the OBS source matches the application or device, and no mute control is enabled. Then use the alternative capture method and check the meter again.
Capture Winamp or the output device
On a supported Windows system, add an Application Audio Capture source to the scene or use the application-audio option available in your OBS version. Select Winamp from the application list. Play a track and confirm the meter responds. This is the more selective method when it works, because it captures Winamp rather than all sound coming through the chosen output device.
If the application source is missing, incompatible, or silent, add an Audio Output Capture source and choose the Windows device that plays Winamp. OBS describes these options in its audio sources documentation. This method is broader: other sounds sent to that device may also enter the broadcast. Close or mute notifications and unrelated applications if you do not want them in the programme.
| Capture method | What enters OBS | When it fits | Main check |
|---|---|---|---|
| Application Audio Capture | Audio from the selected application, when supported and compatible | You want Winamp separated from other desktop sounds | Confirm Winamp appears and its meter moves during playback |
| Audio Output Capture | Audio from the selected output device | Application capture is unavailable or does not receive Winamp | Confirm the device is the one Winamp uses and account for other sounds sent there |
The table describes the intended routing, not a promise that either method will work identically on every machine. If you use the output-device fallback, avoid capturing the same device a second time through OBS’s global audio settings. OBS warns that a device captured in a scene can echo if it is also selected globally in Settings → Audio. Likewise, when using application audio capture, disable global Desktop Audio if it would capture the same Winamp sound again.
After changing the route, check both the source list and the mixer. A source may exist but be muted, hidden from the active scene’s audio mix, or pointed at the wrong device. If the meter moves but the preview is silent, inspect OBS’s audio output and monitoring choices, then confirm the stream preview rather than relying on the local mixer alone.
For another useful OBS preflight, see how to verify audio channels and sample rate. The details of that check are particularly relevant when the source is a video file; for this Winamp workflow, begin by confirming the capture meter and listening to the stream preview.
Connect OBS to YouTube Live
Your YouTube channel must be able to use live streaming before OBS can send a broadcast. YouTube says the channel needs to be verified and must not have had live-streaming restrictions during the previous 90 days. First-time activation may take up to 24 hours, so check access ahead of the day you plan to stream. See YouTube’s current live-streaming eligibility guidance for the latest requirements.
In YouTube Studio, open the Live Control Room and create or select the stream you plan to use. Copy the server or stream URL and stream key shown there into OBS’s stream settings. YouTube’s encoder setup instructions walk through providing those details. If you are using a scheduled stream, make sure OBS is connecting to the intended event rather than another stream entry on the channel.
Treat the stream key as a credential. YouTube describes stream keys as password-like information for the broadcast. Do not include the key in a screenshot, public post, or message to someone who does not need it. If it is exposed, reset it through the Live Control Room and replace the saved value in OBS before you reconnect.
This basic setup does not require you to choose an advanced ingestion protocol or add settings just because they appear in a separate encoder guide. Use the connection details YouTube provides for the stream and the options OBS presents, then check the Live Control Room. If YouTube reports a connection issue, use the current instructions in its help pages rather than guessing at settings.
Check the preview and audio
Start the OBS stream so the encoder sends a feed to YouTube, but do not immediately treat that as proof that the public broadcast is ready. Wait for the Live Control Room preview to appear. YouTube recommends preparing the encoder in advance and monitoring audio and video quality. For a scheduled broadcast, inspect the preview and confirm the presentation before selecting Go live.
Listen to the preview with headphones or another monitoring method that will not feed the stream back into itself. Check that Winamp is audible, the beginning of the track is not clipped, and there is no unwanted desktop sound, distortion, or doubled music. A moving OBS meter proves that OBS sees a signal; it does not tell you whether YouTube is receiving a clean, intelligible version of it.
Look at the picture as well as the sound. Confirm the intended scene is active, the station title is visible, and the image is not blank or unexpectedly cropped. If you use a static image, make sure it is the one you meant to send. A successful connection can still carry the wrong scene or an audio source that is muted.
If the preview has no audio, return to the signal chain rather than changing several controls at random. Confirm Winamp is playing and audible on the selected Windows device, then inspect the OBS source and mixer. If application capture is silent, try the matching output-device source; if a device route produces an echo, disable duplicate capture in the scene or global audio settings. Check the preview again after each change.
A related issue is the display between playlist items. This guide focuses on Winamp audio, but if your scene uses video items and goes blank between them, see the advice on preventing a blank scene between playlist videos. Do not assume that a playlist’s audio behaviour determines what viewers see.
Go live and monitor playback
Once the preview is present and you have checked the sound and picture, click Go live in the Live Control Room when you are ready to begin the public broadcast. Keep OBS and the YouTube control room available while it runs. Watch for a stopped Winamp playlist, a muted source, a lost device, or a YouTube warning. A long-running broadcast needs observation; this setup does not promise uninterrupted audio.
Plan how you will respond if playback stops. Keep the playlist and OBS controls accessible, and know how to pause or replace a track without broadcasting a desktop notification or an unintended source. If the connection drops, check whether Winamp is still playing and whether OBS remains connected before restarting anything. Make one change at a time, then verify the preview again.
At the end, stop the stream from OBS and end the broadcast in YouTube’s Live Control Room as appropriate. Confirm that the event has ended before leaving the setup unattended. YouTube’s help describes what happens to completed live streams, but platform behaviour can change; check the current guidance if you rely on an archive being available afterwards.
If you need a channel that continues while your computer is switched off, this local Winamp-and-OBS chain is not designed to do that: it depends on your computer playing the source and sending the encoder feed. StreamNeo is relevant to that specific unattended-computer problem because it takes an uploaded video and runs it as a YouTube live stream without leaving your computer on; it does not capture a live Winamp playlist.
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
How do I stream Winamp audio to YouTube?
Play your playlist in Winamp, capture its audio in OBS using application capture or the output-device fallback, and connect OBS to YouTube with the stream URL and key from YouTube Studio. Check the Live Control Room preview and listen before going live.
How do I capture Winamp in OBS if the application source is unavailable?
Use an Audio Output Capture source and select the device Winamp is sending sound to. It can capture other audio from that device too, so close or mute sounds you do not want in the broadcast and avoid capturing the same device through a second OBS route.
Does this set up a SHOUTcast radio server?
No. Winamp plays the playlist, OBS captures and encodes the sound, and YouTube Live is the destination. This guide does not configure a SHOUTcast server or a separate internet radio distribution service.
Can I stream any music playlist if I set YouTube to unlisted?
No. An unlisted setting does not grant music rights. YouTube scans live streams for third-party content, so check your permissions and YouTube’s current copyright guidance before broadcasting.