Some broadcasters have found that a metadata issue can occur when using Digital Jukebox On-Air 2 (DJB On-Air) to drive their Live365 station in LiveDJ mode. The issue is that metadata (song name and artist) is not being correctly sent from Digital Jukebox On-Air 2, so the metadata does not show on the Live365 player. 

Having a text metadata display on your station dashboard and the Live365 players is key to your station remaining in compliance with the DMCA. It’s also worth noting that there are older versions of DJB 2 that have encoder settings for “Live365.” Unfortunately, these settings were made for the old Live365 and do not work with the current platform. This is partially why additional steps are needed to get the text metadata flowing through to our servers correctly. 


This issue was particularly identified with the use of Digital Jukebox On-Air 2 (version 1.7.82) while also using the B.U.T.T. streaming software on another PC, but may also occur with different versions of DJB On-Air or other streaming software. 


Firstly, if you are going between 2 computers (ie. 1 PC using DJB On-Air software to another PC using the B.U.T.T. streaming software), a stable network connection is required for B.U.T.T. to be able to read the files from the computer using DJB On-Air.


Locate Your DJB Files


Once you have established that you have a stable network connection, you will need to take a look at your files to locate the issue. On the computer using DJB On-Air, take note of where all your DJB files are contained (ie. local disk C:). The folder containing your DJB files should be labeled “JBData.” This folder should contain daily music, traffic logs, as well as system files. DJB On-Air automatically creates and updates some files as each audio file plays within DJB.



After you have located your DJB files, you will need to locate the “JBData” folder from within B.U.T.T. streaming software. Navigate through your stable network connection to the computer using DJB On-Air (ie. “ONAIR1”) and access the “JBData” folder. (Once you are navigating from your B.U.T.T. streaming computer to your DJB On-Air computer, locate the “JBData” folder in the same place you previously found it while searching through the computer using DJB On-Air.)


Select the Correct .txt File


You will notice a few different .txt files in this folder, including one labeled “nowplay.” While DJB On-Air updates this file, it may not put the metadata into a format that B.U.T.T. streaming software can read. For example, the metadata from the “nowplay” file was formatted as:


 The Steve Miller Band



However, this metadata format is "unreadable" by the B.U.T.T. streaming software. The metadata needs to be formatted as:


 Steve Miller Band - Swingtown


When the metadata is filling in the text file using this format, B.U.T.T. streaming software can read the metadata, meaning it will then appear on the Live365 player. 


The .txt file that formats the metadata correctly for B.U.T.T. streaming software is labeled "titlegyor." The file formats the metadata as Steve Miller Band - Swingtown (3:23)


Although the song length is included, only the song name and artist appear, so that song length text addition does not interfere with the necessary formatting. The "titlegyor" .txt file correctly formats the metadata for B.U.T.T. streaming software to read it. 


To select the "titlegyor" .txt file, go to the B.U.T.T. settings and select the “Stream” tab across the top. Select the file icon next to the “Update song name from file” box and select “titlegyor.txt.” Ensure that “Activate” is also checked.



You should now notice in B.U.T.T. as well as in your stream, that the song information has been updated to the correct format as pictured below.



Using this .txt file, the metadata should then show on the Live365 dashboard and players. The B.U.T.T. streaming software continues to read that .txt file and the metadata changes with the song change. This .txt file correctly sends the name of everything currently playing within the DJB On-Air software, therefore, solving the metadata issue.