Please enable JavaScript to view this site.

XStudio PostMajik

Navigation: » No topics above this level «

How XStudio PostMajik Works

Scroll Prev Top Next More

XStudio PostMajik consists of two main programs and a number of ancillary programs, support files and databases. The main program is the XStudio PostMajik server, which runs as a Windows service and thus is invisible to the user. Configuration, maintenance and monitoring tasks are carried out using a client application, PostMajik Client, which communicates with the server.

Overview

The XStudio PostMajik server is designed to run 7x24, whether or not a user is logged on to the host Windows operating system. When it starts up, information about each station that has been configured is retrieved and evaluated. If a station is enabled (marked as active), the server starts a subprogram specifically for that station. Each station subprogram communicates with the server about its activity and errors, if any. The server, in turn, forwards individual station information and general system information to any PostMajik Client applications that are connected.

During operation, most system configuration and station configuration changes are detected and updated automatically by the server, generally within a minute or so. If system configuration changes are fundamental to the core system and require a server restart, all client applications are notified of the need for the server restart and the changes won't take effect until the server is restarted.

Each defined station has its own database and one or more associated post items, which are acted upon when the station subprogram receives play start information from its host audio system. Post items can be either text or RDS types and each station can have as many post items as needed to forward messages to all the places they are needed. Each station subprogram has its own FTP module (for uploading text items) and may have one or more RDS modules to handle communications with RDS encoders. Event logs are created and maintained for each station, its FTP module and any RDS modules to provide information on activity related to each station and its posting activities.

You may create as many stations as you wish. The XStudio PostMajik server controls the number of stations that may be active at any one time based on your license. As a default, XStudio PostMajik is licensed to support one station but more station licenses can be purchased as needed.

Station Processing Overview

Each active station subprogram monitors its host audio system for play start activity. On detection of the start of play, the cart number (audio ID) is used to determine the user-defined audio category the item belongs to. The station's database is used to create the core message content (song title, artist, alternate message, etc.). Once the core content is determined, each active station post item is used to construct a complete message for that item. The completed message is the result of merging the variable content (song title, artist, alternate message, etc.) with the post item's message template. The completed message is then processed according to the post item's properties, which may include writing a text file, uploading a text file via FTP, or sending a message to an RDS encoder. All active post item's for the station are processed, each with is own customized message and handling properties.

Station Posting Decision Tree

Depending on the host audio system and features enabled or disabled in XStudio PostMajik, different paths will be used by the station subprogram to determine which, if any, content for given audio start of play will be posted.

The cart number supplied by the host unit is used to try to find a cart category for the cart, using the cart masks you've defined for each cart category.

Custom_Info02_40x40_Circle_ClarendonExtended

XStudio PostMajik searches for a matching category (the cart number matches one of the cart masks in the category) in alphabetical order of the category names that have been defined for the station.

If a category is found, the category is "Music", and you've elected to use the station's music database, the song Title, Artist, Album and Release Year are looked up in the music database. If found, the information is posted. If not found and you have alternate messages for the music category, then a valid alternate message is used. Otherwise, no information is posted.

If a category is found, the category is "Music", you have not elected to use the music database, and you have alternate messaging enabled, a valid alternate message for the music category is used. If no message is found, then an attempt is made to use a valid message from the "* Unknown *" category. If no valid messages are found, nothing is posted.

If a category is found, the cart is non-music and alternate messaging is enabled, then the cart category is used to look up available alternate messages and the least recently used message valid for the day is used. If the category cannot be found, then an attempt to use a valid message from the "* Unknown *" category is made. If no valid messages from this category are found, nothing is posted.

If a category is found, the cart is non-music, and alternate messaging is not enabled, no message is posted.

If all tests listed above fail, no message is posted.

Special Maestro Handling

If the host audio system is Maestro and you have enabled the "SendAllInfoToRemote" option within Maestro, handling of the play start message is a bit different. If not enabled, handling of Maestro play start information is the same as other host audio systems, as described above. With the "SendAllInfoToRemote" option enabled, play start information for Maestro is handled in the following way:

If the cart is music and you have the station's "Use Music Database" option enabled, a lookup of the song is attempted in the music database. If found, the Title and Artist information in the database is used. Otherwise, the song Title and Artist information provided by Maestro is used.

If you do not have the station's music database enabled and the cart is music, the song Title and Artist information provided by Maestro is used.

If the cart is non-music and alternate messaging is enabled, then the cart category provided by Maestro is used to look up available alternate messages and the least recently used message valid for the day is used. If the category cannot be found, then an attempt to use a valid message from the "* Unknown *" category is made. If no valid messages from this category are found, nothing is posted.

If the cart is non-music and alternate messaging is not enabled, nothing is posted.

The primary difference in this special Maestro processing is the use of the Song Title and Artist information received from Maestro if the station does not have the music database enabled.

Alternate Message Handling

Alternate messages, if enabled for a station, are used for non-music cart categories and in the case a song has no available information. Cart categories can have multiple category alternate messages, each with its own valid start and end date. When XStudio PostMajik determines an alternate message is to be used, the last-used alternate message in the category is located as a starting point. From there, XStudio PostMajik steps to the next message to see if it is valid for the day. If so, it is used and marked as last-used. If not, XStudio PostMajik steps through the rest of the available messages until if finds one that is valid for the day and marks it as last-used. When the last category message is reached, XStudio PostMajik loops around to the beginning of the list.

See the topic Using Alternate Messages for additional information on using alternate messages.

Scheduled Event Handling

Scheduled events differ from music and alternate message handling in that they are not driven by start-of-play messages from the host audio system. Rather, scheduled events are time, day and date driven. A scheduled event provides a means to post a specific text or RDS message at a particular time of the day. Long-form programming, like sporting events, news programs, public affairs programming and remote broadcasts may be candidates for using a scheduled event. Scheduled events can be exclusive to the time period they are active (meaning no other posts are allowed), or they can be configured to allow other start-of-play posting activity, then re-posting the the event message when the other post expires at the end of its play.

See the topic Scheduled Events for information on setting up scheduled events.

Remote Monitoring and Maintenance

Since the XStudio PostMajik server, which provides all the processing and posting functionality, is separate from the PostMajik Client application, you can install PostMajik Client on machines other than the one hosting the XStudio PostMajik server.

This allows for remote access to the system to monitor activity and perform maintenance tasks. A separate installation program for PostMajik Client is available for this purpose. Once installed, you can connect to the XStudio PostMajik server from anywhere you can access the machine hosting the XStudio PostMajik server via TCP/IP.

Using PostMajik Client remotely, you can manage system posting templates and station databases. You can also monitor a station's activity, including information on the most-recently posted items.

Custom_Info02_40x40_Circle_ClarendonExtended

As a default, Server Configuration & Station Configuration access is disabled when PostMajik Client is installed on a remote PC.