OBS can send a continuous deep house programme to YouTube Live, but it does not make the stream or music rights automatic. Before you launch, check that your channel can go live, clear the recordings and compositions for the uses you intend, and decide how you will monitor the broadcast and preserve a separate archive.
The setup is a sequence: prepare a rights-cleared programme, create or select a broadcast in YouTube Studio, connect OBS, then test the preview and playback before making it public. A continuous broadcast also needs a plan for reconnects; YouTube’s automatic archive guidance does not promise a complete recording of a stream that runs beyond 12 hours.
Check channel eligibility and live access
Start with the channel, not the encoder. YouTube’s live-streaming requirements include channel verification and no live-streaming restriction in the previous 90 days. YouTube also states that creators must be at least 16 to live stream. Requirements and account status can change, so check the current YouTube live-streaming eligibility guidance and the Live Control Room before preparing a public launch.
Sign in to the Google account that owns or manages the channel and open YouTube Studio. Check whether the channel can create a live stream. If live access has not been enabled, complete the required verification and activation steps and allow for any waiting period shown by YouTube. Do not assume that a channel which can upload videos is already able to broadcast.
Also confirm that you are working in the intended channel if your account manages more than one. A stream key belongs to a particular channel and broadcast context; a valid key copied from a different channel will not connect the programme to the destination you expect. Keep access to the account and key limited to people who need them. Treat a stream key like a password: do not place it in public notes, screenshots or a shared chat.
If you are using a computer that will run OBS around the clock, check the practical basics before you build the scene: it must remain powered, connected to the internet and available to OBS. There is no source-backed hardware specification here that guarantees a 24/7 stream. A machine that handles a short test may still need observation over a longer period, so do not confuse a successful first connection with proof of unattended operation.
Clear rights for the recordings and compositions
A YouTube live stream of deep house needs permission for the music it transmits. For every recording, establish who controls the recording and who controls the underlying composition, and whether your permission covers the intended territories and live transmission. If you plan to leave a replay available, confirm separately that the permissions also cover the archived or on-demand use.
A track purchased, downloaded, or available in a personal streaming subscription is not automatically cleared for a public YouTube broadcast. Nor does a credit in the description replace permission. Ask the rights holder or authorised licensor for terms that specifically cover your intended use, and keep the evidence together: track title, version, rights contact, permitted uses, territories, term and any conditions on attribution or reporting.
YouTube scans live streams for third-party material. Its copyright guidance for live streams warns that a licensed live stream may still be interrupted if the rights holder has not allowlisted the channel through Content ID. Ask the rights holder whether they need to add your channel to an allowlist and how long that process takes. A licence and an allowlist are distinct matters: permission may exist, but automated detection can still affect the broadcast until the channel is recognised.
Make a simple track register before loading the playlist. Note whether each item is an original work, commissioned recording, licensed track or another permitted source, and record the evidence that supports that classification. If a DJ mix combines tracks, clearance for one track does not cover the others. Avoid launching first and hoping to resolve claims later; a rights dispute can interrupt the stream, affect the archive or require you to change the programme.
YouTube’s guidance for artists going live is useful context, but it does not grant rights to someone else’s catalogue. When permissions are unclear, leave the track out until you have confirmation. Do not treat a successful private test, an absence of an immediate claim or a licence from a source you have not checked as proof that all intended uses are cleared.
Prepare a deep house playlist and visual
Build the programme before opening OBS. For a station that loops a prepared sequence, use a playlist whose files are all cleared for live use and arranged so that playback can continue without manual intervention. Listen through the transitions, check for silence or abrupt changes, and make sure the final item leads back to the opening without an unwanted gap or sudden jump in level. If the show is a DJ mix, retain a track list and verify the rights for every recording in it.
Decide what listeners should see while the music plays. A static cover, a restrained animated visual or a scene with station name and current programme information can all work, provided you have rights to the artwork and any motion elements. Make text large enough to read on a phone and keep it away from the edges where different screens may crop it. Avoid visual claims such as “copyright free” unless you can substantiate them for every relevant recording and use.
In OBS, the visual is a scene, and sources within that scene supply the image, text and audio. For a simple radio layout, prepare one scene with a background or visual, a station identifier and the programme audio source. Fewer moving parts make it easier to identify what has failed if the stream is silent or the image freezes. You can add a ticker or logo later; first verify that the basic programme is stable. For a separate walkthrough of on-screen elements, see the guide to adding a logo and ticker to a pre-recorded YouTube live stream.
Check that the source you intend to play is actually continuous. A playlist that reaches its end and stops is not a 24/7 programme, even if OBS continues sending a scene. Test the final-to-first transition and determine how playback resumes if the media source or computer restarts. If you are comparing a file-based programme with a radio feed, the VLC internet-radio-to-YouTube guide describes a different playout route; choose based on how your audio is produced, not on the assumption that one method removes monitoring needs.
Create the YouTube Live broadcast
In YouTube Studio, open the Live Control Room and create or schedule the broadcast. Set its title, description, privacy and thumbnail, and check any other details presented for that stream. For a first run, use private or unlisted visibility if that suits your test and rights arrangements. A private test still sends the music to YouTube, so it is not a substitute for permission.
Choose whether to schedule the programme or start a broadcast when you are ready. Scheduling gives you a prepared destination and lets you check the public-facing details in advance. An immediate broadcast can be simpler for a one-off test, but you still need to select the right stream in the control room before making it public. Read the current prompts in YouTube Studio because labels and controls can change.
YouTube’s live production guide describes copying the stream key to the encoder and checking the signal and preview. Keep the Live Control Room open while setting up OBS. Copy the key carefully, and verify that it belongs to the broadcast you have just created or selected. Do not paste a key from an old setup simply because it worked previously.
The stream key is sensitive. If it is exposed, use YouTube’s controls to reset or replace it, then update OBS with the new value. This can interrupt an active signal, so handle key changes deliberately and confirm that the new connection appears in the intended Live Control Room. Before going public, recheck the title, visibility and destination channel. A successful encoder connection does not itself mean you have selected the correct public settings.
Connect OBS and configure the stream
Install OBS Studio from the official project source and open it on the computer that will send the programme. OBS’s interface changes over time, so use the current controls rather than relying on screenshots for an older version. The OBS project’s YouTube setup guide outlines the general connection flow; the names of specific options may differ in your installed release.
There are two ordinary connection approaches. OBS may offer a YouTube account integration, which connects your account and lets you work with a broadcast from within OBS. Alternatively, choose a YouTube RTMPS service and enter the stream key from YouTube Studio. Account integration reduces manual key handling, while a manual key setup is useful when you want to select the destination in Studio and control the connection explicitly. Either way, verify the selected channel and broadcast before sending a public programme.
Create or select the scene prepared for the station. Add the visual source and audio source, then check OBS’s audio mixer while the programme is playing. Confirm that the meter responds to the music and that no unintended desktop audio, microphone or notification sounds are included. A radio channel with an otherwise finished visual can still be unusable if the encoder is capturing silence or the wrong sound source.
For video and encoder settings, follow the options OBS and YouTube currently expose for your channel and connection. The research available for this guide does not establish a tested resolution, bitrate or minimum computer specification for every deep house station, so do not treat a particular preset as a universal guarantee. Start with settings your machine can sustain, then observe the output and viewer playback during a test. Avoid changing several variables at once; if the picture breaks up, you want to know which adjustment caused it.
When the scene and destination are selected, start streaming from OBS and watch for the signal in YouTube Studio. A connection indicator in OBS is only one part of the check. The Live Control Room should identify the incoming signal for the expected broadcast, and its preview should show the correct picture and sound before you make the stream public.
Test audio, video and stream preview
Run a private or unlisted test before announcing the station. Watch the YouTube preview, then open the stream as a viewer on another device or browser. This checks the actual delivery path rather than just the local OBS canvas. Listen at ordinary volume and check the start, a transition and a later section of the playlist; confirm that the picture remains visible and any station text is readable on a small screen.
Look for audio that is too quiet, clipped, interrupted or doubled. If the meter in OBS moves but viewer playback is silent, check the selected audio source and the YouTube preview rather than raising levels blindly. If sound is doubled, inspect whether the same source is captured through more than one route. Make one change, then test again so you can distinguish the cause from the symptom.
Check the preview for a black screen, frozen artwork or the wrong scene. Confirm that the intended visual is selected and that the media source is playing. A static image is expected to remain still; the problem is an unintended blank or a scene that does not show the station identity you prepared. Also verify the stream title and visibility from a viewer’s perspective.
Keep a short checklist near the computer: correct channel and broadcast, incoming signal, picture visible, audio audible, playlist running, and intended privacy setting. Record what you observe and the settings you used. A test is not evidence that the stream will run indefinitely; it is a way to catch avoidable setup mistakes before listeners arrive.
If you are diagnosing a stream that reconnects but appears offline, compare YouTube’s status with the OBS connection and broadcast state. The guide on why a YouTube radio livestream can show offline after reconnecting covers that specific symptom. Avoid repeatedly changing keys or creating new broadcasts without checking which one OBS is sending to, as that can make the original mismatch harder to trace.
Plan monitoring and separate recording for long streams
OBS can send the live programme, but a 24/7 channel remains dependent on the running computer, its power, its network connection, the media playback and the encoder. YouTube or OBS should not be treated as a guarantee that the stream will remain uninterrupted. Decide who will notice a failure, how they will check it, and what they will do if OBS stops sending or YouTube reports the broadcast offline.
Write down a recovery sequence that another person can follow: check whether the computer is awake and connected, confirm that the playlist is still playing, inspect OBS for an error, then check the Live Control Room for the incoming signal and broadcast status. If you restart OBS or reconnect, verify the destination and preview again. The article on fixing a YouTube live stream that goes offline by itself can help when you need to investigate a recurring stop, but no checklist removes the need to observe the system.
Treat live playout and recording a copy as separate jobs. A stream may be visible to viewers while no complete local archive is being saved. YouTube’s production guide says streams under 12 hours are automatically archived and recommends separate recording and manual upload for longer streams. That guidance is not a promise of a complete archive for an uninterrupted 24/7 programme. If you need a replay, preserve your own recording and check that you have rights for the recording and its later upload as well as the live transmission.
In OBS, local recording is distinct from the outgoing live signal. You can configure recording separately, but it adds work for the computer and creates files that need storage, checking and management. Decide whether you need a continuous copy, shorter segments, or selected programme recordings; each approach has trade-offs in file handling and completeness. Test recording during a private stream and play the resulting file back. A recording indicator is not enough to confirm that the file contains the expected audio and image.
Choose a recording format and a process for recovering a file if the computer stops unexpectedly. OBS supports different recording formats, each with its own handling characteristics; the comparison of MKV and MP4 for pre-recorded live streaming explains why format choice matters when a recording is interrupted. Whichever format you use, test the conversion or upload workflow before relying on it for an important archive.
There is a trade-off between keeping one long file and dividing recordings into manageable parts. Long files are straightforward to think about but harder to inspect and move; shorter segments are easier to replace or upload individually but need consistent naming and continuity checks. Set a routine for confirming available storage, verifying that recording is active and reviewing sample files. If uninterrupted archiving matters, assign someone to check the process rather than assuming the live status covers it.
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 OBS play deep house music to YouTube 24/7?
OBS can encode and send a programme to YouTube Live while the computer and playback remain active. That does not grant music rights or guarantee an uninterrupted broadcast. Clear the music for live use, test the full playback path and plan for monitoring and reconnects.
Will YouTube archive a 24/7 live stream?
YouTube’s production guide says streams under 12 hours are automatically archived and advises separate recording and manual upload for longer streams. Do not rely on YouTube to provide a complete archive of a continuous 24/7 programme. Record a separate copy if you need one, and confirm that your rights cover the archive and upload.
Do I need a licence if I bought the tracks?
Buying a track does not by itself establish permission to transmit it publicly on YouTube or retain an on-demand replay. Check the rights for the recording and composition, territories and intended uses. Ask about Content ID allowlisting as well, because a live licence may not prevent automated interruption.
Is OBS account integration better than using a stream key?
Neither approach is universally better. Account integration can make selecting a YouTube broadcast more direct, while manual RTMPS setup gives you the stream key and destination details to manage explicitly. Choose the workflow you can verify, protect the key if you use one, and check the resulting signal in YouTube Studio before going public.