To show the current track on a 24/7 YouTube lofi stream, connect the player’s track metadata to a visible overlay in your scene. YouTube Live does not automatically pass the source playlist’s now-playing title into OBS, so the playback source and overlay workflow must be chosen together.
The simplest route depends on how you play the music: a browser overlay may read supported YouTube or YouTube Music inputs, while a desktop-app bridge can write metadata into OBS sources. Either way, test changes, pauses and long titles before leaving the channel unattended.
Identify the playback source
Start by identifying the exact source that plays the audio in your broadcast. It might be a YouTube video in a browser, a YouTube Music tab, the YouTube Music desktop app, a folder of local audio files, or a managed media library in a playout platform. The source matters because a title overlay can only show metadata that its workflow can read.
Keep the source distinct from the live broadcast. OBS or another encoder captures and sends your scene to YouTube; it does not necessarily know which track is playing in the browser or playlist. YouTube’s encoder guide explains that an encoder converts video into a digital format for streaming. It describes connecting the encoder to YouTube Live, not exposing a source playlist’s current song as an OBS text field.
Write down how the stream actually runs: which app plays the music, which app or device encodes the scene, and whether both stay open continuously. A workflow that detects a desktop music app is not automatically useful when audio comes from a separate browser, and a browser extension’s advertised inputs do not prove that every playlist format works.
For a file-based channel, also decide whether the tracks rotate individually or are embedded in one long video. With separate tracks, a media library may have title and artist data for each item. A single long video may provide no per-song metadata unless you maintain a separate source, such as chapter titles. For background on continuous file-based broadcasts, see what push VOD means for a live channel; the title-display problem still requires its own metadata connection.
Choose a metadata workflow
A useful workflow has three parts: a playback source, a metadata input, and something that renders the result on screen. The metadata input might be chapter or description text, a player plugin reporting the current song, or fields stored with media files in a library. The display might be a browser overlay, OBS text and image sources, or an element in a playout editor.
| Workflow | Playback assumption | Metadata input and display | Main operational trade-off |
|---|---|---|---|
| Browser extension overlay | Music is played in a browser or supported service in the extension’s supported way | Supported YouTube chapters or description playlist inputs; browser overlay added to OBS | Quick to try, but verify the exact player and playlist format; extension updates and permissions need attention |
| Desktop-app bridge | YouTube Music is played in the documented desktop app | App/plugin reports track data to a local helper; OBS text and image sources display it | More control in OBS, but depends on the app, helper process and its stop/close behaviour |
| Local player-detection overlay | Music comes from a player and browser combination the overlay recognises | Detected title and artist appear in a local web overlay | Avoids writing a bridge, but exact compatibility and ongoing maintenance need checking |
| Managed media-library element | Tracks rotate from a platform’s own library or playout system | Media-file metadata feeds a built-in Now Playing element | Coherent for library-based playout, but does not directly solve metadata from an unrelated browser playlist |
The OBS Project Forum’s Music on stream listing says its Chrome extension supports YouTube and YouTube Music and can use YouTube chapters or description playlists as title inputs. Those are the listing’s claims, not a guarantee that any playlist or playback arrangement will work. Its browser-overlay approach is a reasonable first test if your source and title data match those supported inputs.
A separate GitHub bridge example is specifically aimed at YouTube Music desktop playback through the th-ch desktop app and its Tuna OBS plugin. It writes track-title and cover files for OBS sources to read. This is a community project, not a feature supported by Google or OBS, so assess its instructions and maintenance before relying on it overnight.
A third style is a local overlay application that detects supported music players and serves an overlay for streaming software. Streamling’s repository describes this approach and lists YouTube and YouTube Music among its sources. Check its current instructions and the exact player/browser combination; the repository description does not establish unattended long-run reliability.
If your channel rotates tracks from a managed library, a platform’s own Now Playing element may be simpler than bridging a browser player. A vendor’s guide to a media-library Now Playing element describes metadata drawn from media files and an editor element that changes with each item. Confirm the current workflow and terms in the vendor documentation; it is not a direct method for reading a YouTube playlist in OBS.
Use a browser overlay with supported inputs
A browser extension overlay suits a channel where the music genuinely plays through a supported browser or service and the title data is available in a format it accepts. The Music on stream listing describes using YouTube chapters or a video-description playlist as inputs, along with an overlay that can be styled. In that arrangement, the chapter or description data is the metadata source; YouTube Live itself is not supplying the current title to OBS.
Before making it part of an unattended stream, follow the extension’s own current installation instructions and add its provided overlay as an OBS browser source. Do not assume an arbitrary YouTube playlist will be parsed correctly. Test the specific video, chapter format or description list you plan to use, and verify what happens when the source changes to another video.
Check whether the display changes at the right moment. If the underlying content contains several songs but the overlay reads only the current video’s title, it may display that one title throughout the video. A chapter-based input may be more appropriate if you have reliable chapter entries for individual tracks, but you still need to confirm the extension recognises them.
The listing says the overlay can hide when music is paused and scroll long titles. Those behaviours can help, but try them in your own scene rather than treating a resource description as a test of your setup. A paused source that leaves a title visible can mislead viewers; a scrolling title can be distracting if it never settles or is too small to read.
Browser extensions can request access to browser data, and their permissions or behaviour may change with updates. Review the extension’s current permissions and remove access you do not need. If the browser profile or machine must remain logged in and open for playback, include that as part of your overnight plan rather than assuming the overlay is independent of the player.
Connect YouTube Music metadata to OBS
If you specifically play music in the th-ch YouTube Music desktop app and are comfortable running a local helper, the GitHub bridge provides a different route. In its documented flow, the app’s Tuna OBS plugin reports current track details to a local Python receiver. That receiver writes a title text file and cover image file, and OBS reads those files through native text and image sources.
This arrangement makes the dependency chain explicit: the desktop app must be playing, the plugin must send the metadata, the receiver must be running, and OBS must be pointed at the files it updates. If any link fails, the audio may continue while the title stops changing. Treat the repository’s README as the authority for installation and configuration rather than guessing settings from another version.
The README calls for Python 3.8 or later and says Pillow is optional. Those are project requirements reported by that repository, not general OBS requirements. The project documents running the receiver manually or as a user service; choose a method you understand and test after a restart, since a helper that runs only in an interactive terminal may disappear when you close that session.
There is a particularly important stale-title limitation: the README notes that if the desktop app is fully closed, the last track remains visible because the bridge has no staleness timeout. Plan for that behaviour. You can add a suitable clearing or timeout mechanism, or make closing the player an explicit alarm condition in your checks. Do not present a frozen title as evidence that the stream is still playing that track.
This path is narrower than a general-purpose overlay. It assumes the documented desktop player and plugin route; it does not mean OBS can read metadata from every browser, music app or YouTube playlist. If your source is a browser tab instead, choose a workflow designed for that source and test its exact input.
Add and position the label
Once metadata reaches the scene, make the label readable without competing with the music or artwork. Use a short field such as track title and artist, where both are supplied, and place it where it does not cover a focal point in the background. For a lofi scene, that may be a clear corner away from the main illustration or visual loop, but check the crop on the actual live output rather than only in the OBS preview.
With the browser-overlay route, use the overlay’s own theme controls where available. With the desktop bridge, add a text source that reads the generated title file and an image source for the cover file if you want artwork as well. Confirm OBS refreshes the image when the file changes, as documented by the bridge, and keep the image optional if it distracts from the scene or causes a blank box when artwork is missing.
Long titles need a deliberate treatment. A scrolling label can fit more text but moves continuously; wrapping can take more vertical room; truncation is compact but can remove a useful part of the title. The media-library guide also advises correcting file metadata and handling overflow. Fix spelling and inconsistent artist/title fields at their source where possible, then test an unusually long title in the final layout.
Use adequate contrast against both bright and dark parts of the video. A subtle background panel or shadow can help, but avoid a translucent treatment so faint that white text disappears over a lamp or window in the loop. Preview the scene at the size viewers are likely to see and check that the label remains legible when YouTube’s player controls are visible.
For a local detection overlay, follow its instructions for the local web address and add that page as a browser source in OBS. The overlay’s web page and its player-detection helper are separate dependencies: an OBS browser source may render correctly while the helper fails to detect a changed track. Keep the display simple enough that a missing title does not look like a broken panel across the scene.
Test track changes and fallback behaviour
Test a complete cycle before leaving the stream unattended. Start playback, confirm the expected title appears, then let the source move to another track or chapter. Verify that the title and artwork change together if both are present. A label that works only on the first item has not yet demonstrated that its metadata path handles the playlist.
Then test pause, stop, player close, and a temporary loss of the metadata helper where practical. Decide what should appear in each case: hide the label, show a neutral message such as “Music stream”, or clear the title. A last-known title can be acceptable briefly, but if it remains after playback has stopped it is misleading. The bridge example’s documented lack of a timeout makes this test essential for that workflow.
Also test an item with no title or cover, a long title, and a switch between videos if your playlist includes separate videos. The fallback should not imply more than the system knows. For example, “Now playing” above a blank value is less useful than a hidden label, and stale artwork beside a new title can suggest the wrong track.
Finally, observe the actual outgoing scene and audio together. Ensure the label is not hidden behind another source, cropped, or located beneath player controls. If your production includes a microphone, webcam or headset, those are choices based on the programme; they are not requirements for a text overlay. YouTube’s encoder guidance discusses connecting audio and video hardware when a stream uses it, not as prerequisites for showing track metadata.
For broader continuity checks, consider how the playback arrangement itself loops and changes files. The practical differences between an FFmpeg loop and a concat playlist can affect where track boundaries occur, while a video-format playlist on a continuous channel is a separate playback question from how titles reach an overlay.
Troubleshoot stale or missing metadata
If the title is blank, follow the data path in order rather than changing several scene settings at once. Confirm that the intended player is actually playing the track, then confirm that the chosen workflow supports that specific player and input. For a chapter-based overlay, inspect the chapter or description data; for the desktop bridge, check the plugin, receiver and generated files; for a media-library element, check the file’s title and artist metadata.
If the right title appears once but never changes, the source might be a single long video without per-track metadata, or the helper may have stopped updating. Check whether a new track actually begins in the player, whether the bridge process remains active, and whether OBS is still reading the same text file. A display cannot infer track boundaries that the metadata source does not provide.
If the previous title remains after a stop, look for the workflow’s pause/stop behaviour and timeout options. Some overlays may hide on pause; the documented desktop bridge retains its last title when the app closes. Where there is no clear-on-stop setting, add a deliberate clearing mechanism if appropriate or choose a workflow whose fallback behaviour you can monitor.
If the title is wrong rather than stale, correct the metadata where it originates. A file-library element reflects what is stored with the media, and a chapter-driven source reflects the chapter labels. For a description playlist or browser overlay, compare the displayed item against the input the tool is actually reading. Correcting the scene font will not repair incorrect source data.
If the label is unreadable, inspect size, contrast, placement and overflow independently. A title may be technically current yet unusable if it blends into the background or scrolls too quickly to read. Make one adjustment at a time and preview a light scene, a dark scene and a long title before settling on the layout.
For a broadcast that must keep running when your own computer is off, distinguish the title workflow from the playout workflow. StreamNeo turns an uploaded video into a YouTube live broadcast without keeping your computer on, which removes the need to leave a personal machine running for that file-based stream; a now-playing label still needs metadata available from the playback arrangement you choose. A local overlay or helper that depends on a desktop player is not automatically moved into that separate workflow.
If your system is based on a continuous loop, test the interaction between track boundaries and the overlay before relying on it overnight. A title that changes only on a new video will not necessarily follow separate songs inside one file. Where you need per-track labels, use source material or a managed library that actually exposes per-track titles to the selected overlay.
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
Does YouTube Live show the source playlist’s current song in OBS?
No. Do not assume the live stream exposes the playlist’s now-playing metadata to OBS. Connect a metadata source, such as supported chapter inputs or a player-specific bridge, to an overlay or OBS source.
Can I display a track title if my lofi mix is one long video?
Only if your chosen workflow has track-level metadata to read, such as usable chapter labels supported by that overlay. A video title by itself may identify the mix rather than the song currently playing. Test the exact source and title input before depending on it.
Why does OBS keep showing the previous song?
The metadata helper may have stopped, or the selected workflow may leave the last value visible when playback stops. The documented YouTube Music bridge has no staleness timeout when its app is closed. Test stop and close behaviour, and add a clearing or timeout method if the workflow allows it.
Do I need a microphone or webcam to show the title?
No. A title label needs metadata and a visible scene source, not a microphone or webcam. Those devices are only relevant if your programme uses them for audio or video.