STREAMING GUIDE / CREATOR PROJECTS

Use YouTube Player with OBS: playback, capture, and control

Get browser playback working first, capture it deliberately, and only then enable OBS stream-control features.

START HERE

Run yt-player with OBS integration disabled until Chrome plays the intended playlists. Add that Chrome window and one audio capture path to OBS, make a recording, then decide whether stream restarts should be enabled. Playlist automation does not itself add video or audio sources to OBS.

Know which part each program handles

This guide covers the source-based YouTube Player project reviewed at commit d7c72fe. It launches Chrome, discovers playlists, chooses among eligible playlists, and monitors playback. OBS remains responsible for composing the image, mixing sound, recording, and broadcasting.

Use videos you own or are authorized to broadcast. The player does not grant content rights or remove YouTube restrictions. Begin with a short, known playlist and an offline OBS rehearsal scene, so a configuration mistake cannot expose a login page or unintended video to viewers.

Prove browser playback before connecting OBS

  1. Download the project's source, extract it to a writable folder, and install Google Chrome and uv separately.
  2. Edit config.py. Set PLAYLISTS_LOCATION to the playlist-listing page you intend to use and set ENABLE_OBS = False.
  3. Keep PAUSE_FOR_BROWSER_LOGIN = True for the first run. Open a terminal in the folder containing main.py and run uv run main.py.
  4. In the Chrome window the program opens, complete any required sign-in or consent step. Return to the terminal and continue at its prompt.
  5. Confirm a playlist is selected and video actually starts. Observe at least one transition before adding OBS to the test.

The app uses its own profile directory. Signing in to your ordinary Chrome window does not necessarily prepare this one. Do not share that profile directory; it can contain signed-in browser state.

Capture the controlled Chrome window and its audio

For the Windows workflow, add an OBS Window Capture source and select the Chrome window launched by the player. Verify the picture as the video changes. An OBS Browser Source runs a separate embedded browser; pasting a YouTube URL there does not connect it to the Chrome session being automated.

Use one intentional audio capture route. On supported Windows versions, OBS can capture an application's sound separately; see the application-audio isolation guide. If that source already carries Chrome sound, do not also capture the same sound through Desktop Audio. Video capture success alone does not prove audio is included.

Record a short sample containing video playback and a playlist transition. Listen to the saved file and check for missing sound, doubling, unwanted notifications, and the wrong browser window. macOS uses its own screen/audio capture sources rather than these Windows-specific source choices.

Enable only the stream-control behavior you want

Once playback and capture pass, configure the authenticated OBS WebSocket connection if you want the helper to monitor OBS. Set ENABLE_OBS = True and supply the matching host, port, and password. Use the connection checklist if the player reports an OBS failure.

The reviewed configuration has two separate policies: RESTART_INTERVAL = -1 disables scheduled restarts, while RESTART_ON_UNEXPECTED_END = False disables restart-after-stop recovery. Disabling only the interval does not disable the second policy. A manual Stop after streaming has begun can be seen as an unexpected end while recovery remains active.

For the first integrated test, leave both restart policies disabled. There is no universal need to restart a healthy stream on a fixed schedule. Enable a policy only for a specific operating requirement you have tested.

Rehearse the beginning, transition, and shutdown

  • Start from a closed player and verify the intended Chrome profile, playlist page, and OBS sources recover correctly.
  • Keep at least two eligible playlists if you expect continuous rotation; the player deliberately avoids immediately selecting the same playlist again.
  • Put unwanted playlist IDs or URLs in PLAYLIST_BLACKLIST and test the result rather than assuming a video-level URL blocks only one video.
  • Pause a video deliberately and confirm you understand the difference between a manual pause and failed playback.
  • Stop the player and verify OBS's stream state yourself. Stopping this helper does not itself stop an already active OBS broadcast.

Keep a simple holding scene ready while you change accounts, fix a failed page, or replace playlist settings. To dip playlist music automatically while you talk, set up OBS audio ducking under your microphone, and check the OBS multitrack & Twitch VOD audio planner if you need separate live and recording tracks. If the source is blank or the player stops progressing, continue with the stage-by-stage troubleshooting guide.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.