To add a now playing track name to a 24/7 Gurbani stream, first decide whether listeners should see it in an audio player, viewers should see it on the video image, or both. Those destinations use different paths: a broadcaster sends metadata to an audio stream server, while OBS needs a source that reads the current title and renders it as text.
The instructions below are generic streaming guidance, not a Gurbani-specific metadata standard. Your server, playout application and OBS setup determine the exact controls; preserve the title and artist or performer details supplied by your trusted playlist source rather than inventing labels.
Decide where the track name should appear
An audio player’s “Now Playing” field usually comes from metadata associated with the audio stream. A viewer watching a YouTube video sees pixels in the video frame; the video needs an on-screen text element that changes when the track changes. Updating one destination does not automatically update the other.
You can configure both outputs, but plan and test each separately. If your only goal is to tell YouTube viewers what is playing, concentrate on the OBS overlay. If people also listen through a radio player or directory, check whether your audio server receives usable metadata. A static title card may be adequate for a single recording, but it cannot identify items as a playlist advances.
| Where the name appears | What supplies it | Main trade-off |
|---|---|---|
| Audio player or directory | Broadcaster or automation sends current-track metadata to the stream server | Player support and server configuration affect what listeners see |
| OBS video image | A reader obtains current-track information and updates an OBS text source | Requires an active reader, a usable information source and a refreshed text output |
| Both | Separate metadata and on-screen-text paths, tested independently | More setup, but the outputs can serve different listeners |
A useful first check is to note your audio server, active mount, encoder or playout application, and whether OBS is on the same machine as the software that knows the playlist. The Tamil track-name guide covers a related YouTube overlay use case; the underlying distinction between stream metadata and text in a video still matters here.
How current-track metadata reaches a radio player or directory
For audio-player metadata, the playout or encoder must provide the current title to the audio stream server as each item changes. Depending on the setup, an application may send a title automatically, a separate tool may send an update, or an operator may enter it manually. A directory or player can display only information it receives and supports.
On Icecast, runtime source statistics can include title and artist fields. Icecast documents /status-json.xsl as a JSON statistics endpoint and notes that available fields can vary with stream type and runtime. Its documentation warns against treating the HTML statistics page as a stable API. Prefer the documented JSON output, raw XML, or a deliberately configured XSLT output when a program needs to read server information. See the Icecast server statistics documentation.
That status endpoint is a way to inspect what the server knows; it does not itself make an OBS overlay or ensure every player displays the same fields. Start by identifying the active mount and opening the player or status output while a track is running. Check whether the displayed title changes when the playout application advances. If it does not, the missing link is upstream of OBS: the application may not send metadata, may send it to another mount, or may use a method your host does not accept.
Metadata transport also depends on stream format and tool support. The What's Now Playing Icecast guidance describes reading tags carried in Ogg Vorbis and Ogg Opus, while MP3 and other formats may require separately sent metadata. Read the reader’s Icecast input notes alongside your own broadcaster and host documentation; do not assume that a particular format or encoder supplies titles just because audio is playing.
Configure the broadcaster or automation to update metadata
Look first for a current-title or now-playing setting in the playout or encoder application. Some applications can pass the artist and title from the playlist item to the server when playback changes. If this is supported and configured for the correct mount, automatic updates reduce the need for an operator to watch a continuous playlist. Confirm the result in the audio player or server status rather than trusting a setting label alone.
If your application cannot send the required information, check whether the host supports an authenticated metadata-update endpoint or whether its own control panel provides a manual update field. Icecast metadata updates generally involve an active mount, an update action, a metadata string, valid credentials and URL encoding; exact request paths and authentication vary by host. SharpStream’s metadata endpoint guidance is an example for that provider, not a universal endpoint recipe. Follow your own host’s instructions, including its UTF-8 handling requirements.
Keep administrative credentials private. Do not place them in a public web page, browser-visible overlay code, a scene viewers can inspect, or a shared file that does not need them. If an integration needs credentials, use a suitable protected configuration mechanism and limit access to people responsible for the stream. A text overlay reader should normally consume a safe output containing the title, not hold the stream server’s admin password.
A manual control-panel update can be useful when a person is present to introduce a programme or correct a title. SoundCast’s manual documents a Now Playing field that can send artist and title information to Icecast. Manual entry has a simple failure mode: when the programme changes and no one updates the field, the old title remains. For a genuinely unattended playlist, use a tested automatic path where available. For a scheduled live programme with an operator, a manual change may be reasonable if the operator knows when and how to make it.
The church hymn playlist guide is relevant if your channel moves between recorded items or programmed segments. Playlist continuity and title accuracy are separate jobs: a playlist can continue correctly while a metadata field remains stale, so check both behaviours.
How OBS can display a changing title
OBS can show changing text when a plugin or other reader obtains current metadata, formats it, and writes it to a text file that OBS uses as a text source. The source then displays the contents of that file in the scene. A basic setup has three links to verify: the reader sees the current item, the reader writes the expected text, and OBS reads the same file and refreshes its display.
One documented option is Tuna, whose OBS resource page describes file outputs and formatting fields such as artist and title. You can add the resulting file as an OBS text source and position it in the scene. Check the Tuna resource documentation for its current requirements and supported input choices. The fields available to format depend on the source that the plugin can actually read, and updates stop if the reader or plugin stops running.
Choose a title format that fits the image and the information your playlist provides. For example, a source might produce an artist followed by a track title, but only if both fields are present and trustworthy. Keep the text readable over the video and avoid adding fields merely because they are available. If a title is long, test how it wraps or is clipped in the scene and decide whether to shorten it using a consistent rule.
Use a neutral fallback such as “Live Gurbani stream” if the current track cannot be identified. Do not guess a shabad, raagi or transliteration from the audio and present it as verified metadata. A clear general label is more useful than a confidently displayed but incorrect attribution.
If you are preparing a looped video as the visual background, keep its embedded file metadata separate from the live title overlay. The guide to removing metadata from video files discusses file metadata; a changing title is a separate text layer that must be updated during playback.
Connect the player or server information to an OBS text source
Decide which component is the reliable source of the current track. It could be the media player or playout system, an Icecast status feed, or a supported reader that already sees the audio metadata. Then configure the reader to write a plain text output in a location OBS can access. Add that file as a text source, select the option to read from a file, and confirm the path is exactly the one the reader updates.
The exact menu labels can differ by OBS version and plugin. The important detail is that OBS must display the changing file, not a one-time text entry. If the reader uses a template, test how it behaves when a field is blank, when a title contains punctuation, and when a new title is shorter than the old one. A stale suffix or an empty line can make the overlay look broken even though the reader is running.
Keep the output file and reader available for as long as the live scene needs updates. If OBS runs on a different computer from the playout system, the file path may not refer to the same file on both machines; use an arrangement supported by your software and confirm OBS can read the actual updated output. Do not expose a private admin endpoint or its credentials just to make a title visible. If your reader cannot safely obtain metadata from the server, use a supported local output or another documented connection method.
This overlay is independent of YouTube’s stream key and does not send a title to radio players. If your channel uses a local OBS machine for the video, review the always-on OBS stream-key settings guide for the separate task of keeping a broadcast configured. A working broadcast does not prove that either metadata path is working.
Test track changes in each destination
Test before relying on the overlay or player listing during an unattended run. Use a short, controlled sequence with known titles and observe the transition from one item to the next. First verify the playout application knows the expected current item. Then check the audio player or server status, if that destination matters. Separately watch the OBS preview or a suitable private test output to confirm the on-screen text changes.
Do not infer that both destinations work because the audio sounds correct or because one player displays a title. An audio player can receive server metadata while OBS remains static; the video overlay can change from a local file while the audio server has no title to pass on. Record which test confirms each output, so you know where to look if a later change breaks only one.
Check representative cases from your playlist: a title with both artist and track, one with a missing field, and one with a long name. Confirm that the displayed text is not clipped, and that a blank value triggers your intended fallback rather than leaving an old title on screen. If items are manually selected, include a programme change and verify the operator’s update process.
For a continuous channel, leave the full chain running long enough to observe more than one transition and include the conditions expected during ordinary operation, such as a scene change or a restart of the reader. This is a practical test, not a guarantee that future updates will work. Keep a note of the active mount, source file and responsible process, so a person covering the channel can identify them without reverse-engineering the setup at night.
Troubleshoot missing or stale titles
Work from the source towards the display, changing one part at a time. This avoids adjusting OBS when the actual problem is that the broadcaster never sent a new title. The following order follows the dependencies described by Icecast, metadata endpoint and OBS reader documentation; it is diagnostic reasoning, not a report of hands-on testing.
- Check the current item. Confirm the playlist or playout application itself shows the correct title and fields. If it does not, fix the source data first.
- Check transmission. Determine whether the encoder sends title changes automatically or whether a separate update is required. A title entered once will not follow every item unless something sends each change.
- Check the mount and server output. Verify that the update targets the active mount and inspect the supported status output or an audio player. On Icecast, prefer the documented JSON or XML output over scraping the HTML statistics page.
- Check the update request. For a host-supported endpoint, review credentials, the required action, URL encoding and character handling against that host’s instructions. Never paste private credentials into a public overlay or ask viewers to help test an admin URL.
- Check the reader and OBS source. Confirm the reader sees the same input that has current metadata, is running, writes the expected file, and that OBS reads that exact file with refresh enabled. A plugin that has stopped will not keep updating the text.
- Check formatting and fallback behaviour. If the file changes but the on-screen text does not, test the OBS source path and format. If text appears but is wrong, compare the formatted fields with the original source rather than editing the title by guesswork.
If the title updates in the radio player but not on video, focus on the overlay reader and OBS file source. If the text changes in OBS but the radio player remains stale, focus on the broadcaster-to-server metadata path. Keep a neutral fallback visible while you investigate rather than displaying a title you cannot verify.
Choose a maintainable setup
For a channel with a reliable playlist and a supported encoder, automatic title updates are usually less operator-dependent than changing each title by hand. Manual updating can suit a small channel with a person present, especially when the programme changes occasionally, but it demands a clear handover and a habit of making every change. For a channel that runs through the night, test what happens if the reader, encoder or OBS process restarts; the exact recovery behaviour depends on the tools you use.
The display destination also changes the work involved. Audio metadata is useful to compatible players and directories, while OBS text is visible in the video frame. If you only need the latter, do not build an audio-server metadata path unless it serves another purpose. If you need both, treat the sources as separate outputs and verify each independently. This distinction is especially useful when you are trying to reduce the number of moving parts in a small operation.
For a 24/7 video channel, a separate practical concern is what happens when a local computer must remain on to keep the broadcast running. If that is the pain you are addressing, StreamNeo takes an uploaded video and keeps the YouTube broadcast running with the computer switched off; the title metadata and OBS overlay still need to be configured for the destination where viewers should see track names.
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
Will the audio player’s track name automatically appear in my OBS video?
No. The player or server metadata and the text rendered into the video are distinct outputs. OBS needs a reader or other mechanism that obtains the current title and updates a text source.
Is there a special metadata format for Gurbani streams?
This guidance does not establish one. Use the trusted title and artist or performer information available from your playlist source, and check what your broadcaster, server and display tools support rather than assuming a Gurbani-specific convention.
Can I update the title by hand?
Yes, if your server or playout application provides a manual update method and an operator is available to use it. You must repeat the update when the programme changes; otherwise the old title can remain visible. For an unattended playlist, test an automatic update path.
What should I check if the title stops changing overnight?
Check in order whether the playout source has the right item, the broadcaster sends it, the active mount receives it, and the server status shows it. Then check that the OBS reader is running and updating the file OBS reads. Keep credentials private, and use the host’s current instructions for its update endpoint.