To show the current track on a 24/7 YouTube music stream, put a changing label or card into the video before it is sent to YouTube. The label needs both track metadata from the player or playback app and a visual overlay in OBS or comparable streaming software.
Changing the YouTube broadcast title or description updates the video’s YouTube metadata; it does not create a changing label inside the picture. For an on-screen display, use a playback source that exposes the current track and connect it to an overlay. If your player does not provide track information or an accessible API, an overlay cannot invent it.
How an on-screen now-playing label works
Think of the outgoing picture as a composition. Your background video, artwork or visual loop sits beneath a layer containing the track title, artist, and, if supported, perhaps album art or progress. Streaming software combines those layers into the picture sent to YouTube. The audio can continue as before; the new part is the information shown on screen.
There are two separate jobs. First, something must know which track is currently playing and provide its metadata. Second, a visual element must display that metadata. A text file, browser overlay or player integration can connect those jobs, but only if it can read from the playback source you actually use.
YouTube’s own fields serve another purpose. Google documents title and description as fields on a live broadcast or its associated video resource. Its Live Streaming API documentation describes the broadcast and stream resources used to manage a live event. Those fields identify and describe the YouTube video; they are not a feed of changing track data for your on-screen graphics.
This distinction matters on a station that plays a sequence of bhajans, lofi tracks or local radio programming. You can set a broadcast title that describes the overall channel or current programme, but editing it as tracks change will not, by itself, put a now-playing label into the transmitted image. Make the label in OBS, or another part of your video composition, and source its text from the playback app.
If your music is organised into scheduled blocks, it is also useful to distinguish a playlist schedule from the track currently playing. A schedule tells you what should play next; the player’s metadata tells you what it reports as playing now. For planning the former, see how to schedule playlists by time of day. Do not treat that schedule as proof that a player API is reporting the current item correctly.
Choose a metadata source
Start by writing down the playback path from the audio file or service to the stream. Is VLC playing local files? Are you using YTMDesktop2? Is another application, a browser tab or a playlist tool responsible for playback? The right integration depends on that answer. The documentation reviewed for the routes below does not establish a universal bridge that reads metadata from every player or browser tab.
If playback runs through VLC local files, the OBS resource VLC Now Playing Monitor / Metadata Display describes a script that detects the current item from a VLC Video Source and reads tags such as title, artist and album. It can format fields into text and export the current song to a text file for an OBS text source. Its documented requirements include Linux, OBS 27.0 or higher with Python scripting enabled, and Python 3. Mutagen is optional and recommended by the resource for better metadata reading. Check the resource’s current instructions and compatibility before relying on it.
This path is only useful when VLC is the playback source the script can inspect. It is not a general-purpose listener for unrelated music software. The resource also describes a filename fallback when tags are absent. A filename may at least identify a file, but it is not equivalent to clean artist and title fields. If your files are named track_07_final.mp3, that is what a fallback may have to show unless you improve the source data.
If playback runs through YTMDesktop2, its OBS integration documentation explains how to enable the app’s API, use its OBS settings to copy an OBS URL, and add that URL as a Browser Source in OBS. The documented overlay offers several layouts and lets you choose elements such as artwork, title, artist and progress. This is a direct fit only when the music is actually playing through that app and its integration is configured; do not assume it can read a different player.
For a different source, investigate that application first. Look for an official API, an OBS integration, a now-playing output file, or documented support for exporting the current item. Establish whether it reports title and artist, how it handles transitions, and whether its connection is available while playback is running unattended. Do not build the graphic first and assume data will appear later.
There are also metadata-enrichment tools and alternate now-playing applications. The What’s Now Playing resource history on OBS Forums describes features including MusicBrainz support, templates and artwork, but an update-history page is not a complete current setup guide. Treat it as a lead to investigate: verify current compatibility and follow the software’s own setup instructions rather than assuming a feature or fix will work in your configuration.
| Playback setup | Route to investigate | What to verify first |
|---|---|---|
| Local files in VLC | VLC-aware OBS script and text file | Linux and OBS scripting requirements, plus populated file tags |
| Music playing through YTMDesktop2 | App API and OBS Browser Source | API enabled, correct app playback, and the documented OBS URL |
| Another player or service | That player’s own API or now-playing output | Whether it actually exposes the current track and works with your OBS setup |
This is a compatibility choice, not a ranking. A text-file path may be enough if the source is VLC and you only need readable title and artist text. A browser overlay can suit you if your playback app provides one and you want its supported layouts or artwork. For audio-oriented setup questions, preserving audio quality when encoding for YouTube Live is a separate concern from making track information visible.
Add an app-provided OBS browser source
For the YTMDesktop2 path, first confirm that the app is your actual playback source. In its documented flow, you enable the local API in the app, open the OBS settings there, copy the provided OBS URL and create a Browser Source in OBS using that URL. Follow the app’s current instructions for its controls and connection details; a copied URL should be treated as a connection to that app, not a generic URL that will read any music session.
The documentation describes a default local URL and notes that a paired client token is needed in the URL if authentication is enabled. If your setup uses such a token, keep it private. Do not place it in a public overlay, a screenshot, a shared configuration or a message posted to a public forum. The browser source needs the configured URL to retrieve the supported display, while other viewers need to see only the resulting graphic in your stream.
Once the source has been added, size and position it in the OBS preview. Choose a supported layout that suits the composition: for example, title-and-artist text or a compact card where the background already contains important imagery. A fuller card may suit a plain visual loop. The app documentation lists options including a badge, fullscreen artwork, vertical stack and ticker, as well as controls for artwork, title, artist and progress. The exact options and their presentation should be confirmed in the app’s current settings.
Do not use the preview alone to conclude the source is working. Check that the player is actively playing a track and that the app is reporting the track details. If the source appears empty, first verify the app-side API and playback state, then the URL and browser source configuration. A graphic cannot display information the app has not made available.
A Browser Source is one way to include a visual layer; it is not required for every metadata route. With the VLC script, the documented workflow can export text to a file and OBS can show that file through a text source. The choice is shaped by the player and the information it exposes, not by a general rule that every now-playing display should use a browser page.
Style the track label or card
Make the two fields people need to identify a track easy to read: title and artist. On a devotional stream, a long transliterated title or a title containing language and version details can take more room than a short English song name. A ticker or compact card may suit a crowded frame; a static title-and-artist treatment is easier to scan when the text fits. Choose from layouts the integration actually supports rather than planning around a feature you have not verified.
Place the label where it does not cover a face, lyrics, a visual focal point or other important information. Check it against both light and dark portions of the video. If the background changes, text that is readable over one image may disappear over another. A solid or translucent backing can improve contrast, but keep it restrained enough that the track label remains a secondary part of the frame rather than obscuring the content.
Artwork and progress are optional additions, not substitutes for a legible title. They depend on the playback app exposing the relevant data and the overlay supporting those fields. If artwork is missing for some tracks, the display should still make sense without it. Likewise, progress may be useful for a single track but less informative for a continuous mix or a long playback item.
Test the shape of the data as well as the visual design. A short title can hide a layout problem that becomes obvious with a long one. Check a title in the language and script your channel uses, a long artist credit, punctuation, and a file with incomplete tags. If your overlay supports a ticker, confirm that it moves at a readable pace and does not clip or overlap other text.
For a VLC text-file route, decide on a simple format such as title - artist only after confirming those tags are supplied. If the source falls back to a filename, the result may be less useful or may include file extensions and internal naming. Improve the metadata in the source files when practical; styling cannot turn an inaccurate filename into verified artist information.
Test updates during playback
Test the complete path from playback to the final transmitted picture. Start a track and check that the expected title and artist appear in the OBS preview. Move to another track and watch for a change. If the text stays fixed, identify whether the playback app is reporting stale data, the integration is not polling or refreshing as expected, or OBS is displaying a static file or page that is not being updated.
Then check the programme output, not just the editing workspace. If you can use a private or unlisted test broadcast appropriate to your channel, view the result as a viewer and confirm the label is visible in the encoded picture. YouTube’s liveBroadcasts API reference covers broadcast resources and their metadata; the overlay itself remains part of the outgoing video composition. Avoid mistaking a changed broadcast title in a dashboard for a changed label in the picture.
For an always-on stream, a brief preview is not evidence of long-duration behaviour. Include a practical checklist: watch a track transition, leave the setup running long enough to observe the normal playback pattern, and check what happens after restarting the player or OBS. If the stream is operated remotely, confirm that you can recognise a missing label or stale track and know which application needs attention. The cited resources describe metadata and overlay capabilities; this article does not claim independently tested long-run recovery, timing or reliability.
Also check audio and visual continuity separately. The label may update correctly while the audio path has a different problem, or the music may continue while the text source stops changing. Keep a record of which source was playing and which OBS source provided the label during your test. That makes later troubleshooting more concrete than changing several settings at once.
If your format uses playlists, compare the displayed track with the player’s actual current item rather than the planned playlist position. A skipped file, a failed item or a transition can make the schedule and playback diverge. For a channel combining language blocks, scheduling Hindi and English playlists on one 24/7 channel can help organise the programme, but a now-playing label still depends on metadata from the active source.
Troubleshoot missing or stale metadata
When the label is blank, work from the source outward. Confirm that music is playing in the expected application. Check whether that application shows the current title and artist itself. If it does not, the problem is likely upstream of OBS: the source may not expose those fields, the file tags may be absent, or the app may not have metadata for that item.
For VLC, inspect the local file tags and confirm the script is configured for the VLC Video Source it is meant to read. The forum resource lists Linux, OBS 27.0 or higher with Python scripting enabled, and Python 3 as requirements, with Mutagen as an optional recommendation. Check the resource’s current setup details if a requirement or script behaviour is unclear. If the title is actually coming from a filename fallback, correct the filename or metadata rather than expecting the text source to infer an artist.
For YTMDesktop2, confirm that playback is happening in YTMDesktop2, that the app API is enabled and that OBS uses the URL copied through the app’s OBS settings. If authentication is enabled, follow the app’s current token instructions and keep any private token out of public view. A Browser Source attached to a different player will not acquire YTMDesktop2’s track data merely because it is in the same OBS scene.
If the label updates late or not at all after a transition, compare what the playback app reports with what the overlay shows. A mismatch points towards the connection or refresh path; matching but incorrect details point back to the source metadata. Restarting a player or OBS can be a useful diagnostic, but it is not a substitute for observing the transition and verifying that the setup resumes as expected.
If only artwork or progress is missing, test with a track that the app reports with those fields and review which overlay elements are enabled. Do not infer that a blank artwork area means title metadata is unavailable, or vice versa: these can be separate fields. If the source reports no artist or title, use a clear fallback you can support or omit that field rather than displaying a guess as fact.
Keep the operating path maintainable
A now-playing layer adds another dependency to an always-on channel: the playback application must expose data, the integration must receive it, and OBS must include the visual source. Keep a short note of the source application, the relevant OBS scene and source name, and where to check the current title. If someone else operates the channel, that note can prevent them from treating an empty overlay as a YouTube metadata problem.
Keep changes small when adjusting a running setup. Change one part at a time, then verify the result in the outgoing picture. If you alter the playback application, API settings or OBS source, repeat the track-transition check. A display that looked correct before a software change may not behave the same way afterwards, and the source documentation should be consulted for current compatibility.
If leaving a computer running solely to keep a player and OBS active is the specific operational problem, StreamNeo removes that computer-running burden by turning an uploaded video into a 24/7 YouTube stream that can run with your computer switched off. That is a different workflow from a live player whose changing API metadata drives an OBS overlay, so choose it only if a fixed uploaded video suits the channel rather than assuming it supplies live now-playing data.
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 changing the YouTube title show the current song on screen?
No. The broadcast title and description are YouTube video metadata, not an overlay in the transmitted picture. To show a changing track label, add a visual source to OBS or your comparable streaming software and connect it to metadata exposed by the active playback source.
Can OBS show a track if my player does not provide metadata?
Not automatically. An overlay needs a source for the track details, such as player tags, an app API or a documented now-playing output. If none is available, you can improve local file tags or use a playback application that exposes the information, but do not assume an integration can read an arbitrary player.
Will the VLC script work with any operating system or player?
The cited OBS resource describes a VLC Video Source workflow and lists Linux, OBS 27.0 or higher with Python scripting enabled, and Python 3 among its requirements. It is not documented as a universal player integration. Check its current instructions and confirm your files have useful tags before relying on it.
How can I tell whether the overlay is reliable enough for a 24/7 channel?
Check that the label changes on track transitions, then observe it after the restarts you expect to occur in your operating routine. A short test cannot establish long-term behaviour, so include the playback app, OBS source and viewer-facing picture in your checks. The cited documentation describes capabilities, not a guarantee of continuous operation.