Welcome < Features < Zetta Splits

Zetta Splits®

Many radio stations broadcast over a geographically wide area on more than one frequency / transmitter, broadcasting a common program to all transmitters. However, to maximize revenues they sell localized commercials which are broadcast to specific transmitters / regions. Thus the main transmitter might be broadcasting one spot block to Region "A" while the split transmitter would be simultaneously broadcasting a different spot block to Region "B".

The splits feature lets a master station send a signal, using TCP, UDP, or Serial, to the stations to play their own local spots and links, and then it rejoins the master station after the break. Splits stations can be used for Internet Streaming stations, Network Programming or Simulcasting.

Splits in Zetta^® is a subscription based model, which means that any Split Client can subscribe and listen for Split Master control events. A subscription based system has a Master, which is an independent station that sends information out to its subscribers, the Client, which is also an independent station. The Client will receive the subscription messages from the Master when the client station is in Split Player Mode. The Split Client then decides based upon the given information what to play. What is played on the Split Client station is determined by the Split Master's Split Behavior, the Assets in a Tag or Imaging for the Split Client, and the Operation Mode of the Split Client station at the time of the Split.

A Zetta station can be setup as a Splits Master, a Splits Client or both. The Splits design allows for “cascaded splits”, where Master station A drives Split station B, which in turn can be a Master station for Split station C. A “Split” can either be a sequence of events wrapped into a Spot Block OR a standalone asset such as a link, song or spot with a split behavior. The main requirement for splits is that the Split Master and the Split Client breaks START and END simultaneously; they must be the same length, this can be achieved by a combination of time stretching/squeezing and/or filling. The target length is declared by the length of the Spot Block OR individual asset on the Master Station. The firing of Assets with a Split Behavior are also supported in the Hot Keys and Stacks modules.

The Splits feature is enabled in the Configuration | System | General tab. The Splits feature is available on stations within a single database or across multiple Zetta sites.

In this Topic: show/hide show/hide

Splits Master

A Split Master is a station that will signal a subscribed Split Client. Split messages from Master station(s) are only received when the split station is in Split Player Mode, otherwise they are ignored. Split messages to queued / play / pause / stop a split event are driven by the Split Behavior; Master Audio, Master Silence or Master Monitor, of an asset scheduled on a Master Station. The Split Client will decide, based on the split behavior, the Splits Name Matching and asset, whether to split from the master or not; if, for example, the Splits Name Matching is set to Tag and there are no assets tagged and a Fill Category is not selected for the station, the Split Client will not split from the Master. The Split Master station and Split Client station can be scheduled using GSelector Integration or through Flat File Load using the V15Native Traffic Load (Splits Only) template.

Stream to Stream Group Mapping

The mechanism used to route audio to specific streams is based on the Split Behavior property of an Asset or a Spot Block. When an Asset on a Master Station is played with a Split Behavior, the audio on the Master Station is routed in the following manner:

When a Split station is in Split Player Mode all log events are routed to the Stream Groups Split streams for that station.

Split Behavior

A Split Behavior is set on the Assets or Spot Block that are scheduled on the Split Master Station where a split is to occur. The Split Behavior is respected in the On-Air, Hot Keys and Stacks modules. The Split Behavior of an asset is set in the Station Specific tab of the assets Metadata card. The Split Behavior of a Spot Block is set when scheduling the Spot Block either using GSelector Integration or Clocks. The Split behavior of an asset or Spot Block can be configured in GSelector. When a Spot Block has a Split Behavior it will override any Split Behavior of an asset scheduled within the Spot Block and ignore any tagging on the assets within the Spot Block. The master station will however send the fill length of the Spot Block to the Split Client. If a Split Behavior is only set on the assets within the Spot Block and these assets are tagged a message is sent to the splits client to queue and play an asset with a matching tag.

A Split Behavior of tells the Master station how to play the asset and to send a signal to the subscribing Split Clients to play a Tag or Imaging asset on the client station. By default, it should try to resolve as a Tag first, then Imaging. This can be changed in the splits stations configuration using the Splits Name Matching option.

None - A Split Behavior of None will play the asset through a stream enabled as Regular (non-split) in the Stream Group. Nothing will be sent to the Split Client.

Master Audio - A Split Behavior of Master Audio tells the Master station to play the audio and send a signal to the subscribing Split Clients to play a Tag or Imaging asset on the client station. If the asset is not in a tag or imaging asset, the Split Client station will play the same asset as the Master Station, if the asset is active on the subscribing station. When an asset's Split Behavior is set to Master Audio, a Master Audio icon will be visible in the Split Behavior column of the Log.

Master Silent - A Split Behavior of Master Silent tells the master station to play silence and send a signal to the subscribing Splits Clients to play a tag or imaging asset on the client station. If the asset is not in a tag or imaging asset, the Split Client station will play the asset scheduled on the Master station, if the asset is active on the subscribing station. When an asset's Split Behavior is set to Master Silent, a Master Silent icon will be visible in the Split Behavior column of the Log.

Tip: The Silent Log Event Progress Bar option in Themes & Appearances changes the color of the progress bar for an event that is silent. This includes Spot Block headers, Master Silent Assets, Macro headers etc. This color change is shown in the Log, On-Air, Stacks, Hot Keys and Z-Player Modules.

Master Monitor - A Split Behavior of Master Monitor will route the audio for the asset to the configured Master Monitor streams of the Stream Group for the Master Station and send a signal to the subscribing Splits Clients to play a tag or imaging asset on the client station. If the asset is not in a tag or imaging asset, the client station will play the same audio asset that is scheduled on the Master Station, if the asset is active on the subscribing station. Master Monitor allows the user to hear the audio locally for the Master Station even though nothing is playing over the air for the Master Station. When an asset's Split Behavior is set to Master Monitor, a Master Monitor icon will be visible in the Split Behavior column of the Log.

Splits Client

A Station becomes a Split Client when a Split Master is selected; this can be done in the Station Configuration Splits tab, with an Execute Command Event or a Command Mapping to a Keyboard or a GPIO event using the Sequencer.SetSplitMaster command. A Split Client will receive information from the Split Master when the Split Stations On-Air module is in Split Player to: mode. The Station Mode can be changed using the Mode drop-down in the On-Air module, with an Execute Command Event or a Command Mapping to a Keyboard or GPIO event using the Sequencer.SetMode command. The Split stations log can be scheduled using GSelector Integration, Clocks, ZCast or through Flat File Load.

When the Split Client receives the splits message, that an individual asset is to play on the Master Station, it will first look for an event with the same Tag or Imaging name as the Master Station; if there is no Tag or Imaging asset and the Split Station is on the same site database, it will play the same asset as long as the asset is active and approved for the Split Station. When an Asset is inserted into the log of the Split Station it is inserted into the same hour as referenced in the Master station below any queued log events. If no queued event is found the asset is placed below the last played event; if none then it is placed below the Top of Hour marker.

When the Split Client receives the splits message, that a Spot Block with a split behavior is to play on the Master Station, it will try and locate an existing Spot Block log event which matches the Split Log Date, Hour and position, if no Spot Block is found nothing will happen on the split station.  

Tagging Assets

Tagging can be used to tell the Split Client stations what to play when a Split Master Station plays an asset with a Split Behavior.  When the Split Client receives a message from the Split Master that a Split is queued, the Split Client will first check for a Tag; if a Tag is found the Split Client will locate the asset, assigned to its station, with the same Tag and schedule it in the log. This is useful to play local imaging links on the splits stations. A Tag is created by clicking the Add new media button in the Library Module | Tags tab.

To add assets to the Tag, simply drag and drop the desired assets into the new Tag window. The assets selected for the Split Master and the Split Client should have approximately the same length. Zetta will use the Maximum stretch/squeeze value, specified in the Playback tab of the Station Configuration window, to achieve an exact length to allow the Split Client to rejoin the Split Master at the correct time. If the assets cannot be stretched or squeezed to match, a warning error will appear in the Tag window for the asset. The Station column in the Tag window is used to select the Station that will use the Asset. A warning error will appear if the asset is inactive for a selected station. For the most part a Tag will contain one asset for the Split Master and one asset for each Split Client; however more complex Tagging can be done such as one to many, many to many or many to one. When one of these more complex methods is used, Zetta will use a weighted scoring logic to select an asset to play on the Split Clients. The Metadata card can be accessed for an asset from the Tag window by simply double-clicking the Asset.  

Imaging Assets

Imaging assets are similar to Tags. However, imaging assets have a fallback order that allows assets to be added that are only used in the event the normal asset is unavailable or invalid. The Fallback order pane shows the levels and order that the asset will play. In Level 1 Zetta checks the Current Shift and then the Default Shift. If there is nothing to play in Level 1 at the station shift level, Zetta will move to Level 2 the Station Rotation level. If there is nothing to play in Level 2, Zetta will move to Level 3 the Shared Rotation (Global) level. If there is nothing to play at Level 3 Zetta will move the Level 4 Shared Rotations (Station Groups) until Zetta finds something to play. Each Station Group in the Shared Rotations (Station Groups) Level can be given a priority order using the Imaging resolution priority field in the Station Groups Configuration window. The Shared Rotations (Station Groups) level follows the Imaging resolution priority given to the station group. Each Level can have any number of assets assigned to the image. Each level shows the number of assets associated with each sub-level. Each Level can have any number of assets assigned to the Imaging asset. An Imaging asset is created by clicking the Add new media button in the Library Module | Imaging tab.

The grid to the far right of the window shows the associated assets in the Imaging asset. Select a Station, Virtual station, Station Group or the Shared Rotation (Global) from the Assignment context list. Drag and drop assets into this grid from the Library module to assign the asset to the Imaging asset. When a Station is selected and if a shift exists for the station, assets can be added at the shift level by selecting a shift in the Fallback order list. Optionally, assets can be moved from one Fallback order to another by dragging and dropping the asset on the fallback order name in the list. Additionally, assets can be dropped on the Station name in the Assignment context to add the asset to the Level 2 - Station Rotation Fallback order.

See the Imaging topic for additional details.

Zetta Splits Across Multiple Zetta Sites

There is two ways of setting up splits for Site to Site Splits configuration, External Splits and ZCast Splits.

External Splits: External Splits will use the Serial/TCP/UDP GPIO connection to communicate between the Master and the Split Forwarder.

ZCast Splits: ZCast Splits will use a ZCast Split Forwarder connection to communicate. ZCast connections use an Outbound ZCast connection at the head end site for the Master station communication and an Inbound ZCast connection at the remote site for the Split Forwarder.

The Split Forwarder is a Virtual Station that is the Master Station at the remote site for any local subscribed split clients. If using Tags or Imaging, the tags/imaging must exist at both sites and must be named the same.

Configuring Spits across multiple Zetta sites requires the configuration of Virtual Stations with External Splits or ZCast Splits. The following diagram shows Zetta Local and External Splits over a TCP-IP connection.

Tags are not used for Spot Blocks with a split behavior. When the Split Client receives the splits message, that a Spot Block with a split behavior is to play on the Master Station, it will try and locate an existing Spot Block log event which matches the Split Log Date, Hour and position. The split station will then play the spots scheduled in the Spot Block, if no Spot Block is found nothing will happen on the split station. However, if the Auto Create Spot Blocks if Missing is enabled for the Splits station, Zetta will create any Spot Blocks that are missing on the Splits Stations so the number of spot blocks match the Master Station. The selected Fill logic will then be used to fill the newly created spot block.

Zetta Splits Step-by-Step Topics

Before proceeding with the following Steps configure the Computer(s) Play Devices that will be used for the Master and Splits stations.

In this section: show/hide show/hide

Configuring Single Site Splits

The following steps will assist in the configuration of splits for a site.

In this section: show/hide show/hide

Step One: Enable the Splits Service

If the Zetta Splits service is not enabled other Splits features will not be visible.

1. Click Configuration | System
2. On the General tab enable Zetta Splits®.
3. Use the Computer drop-down field to select the Longest Split Break Negotiation Computer(s).
4. Click the Save button to save the changes.
5. Close the System window.

Step Two: Configure the Stream Groups for the Master Station

1. Click Configuration | Stream Groups
2. Click the Add New Stream Group  button to create a new Stream Group.  
3. Name the Stream Group as desired
4. In the second line enter a description of the Stream Group (optional)
5. To add play streams, click the Add Playback Stream Mapping button for the desired number of streams
6. For each stream select the Splits Event Routing for the play stream. The Splits Event Routing column is used for Splits. When an Asset or a Spot Block has a Split Behavior set, Zetta will route the audio based on the type of Split Behavior and the routing of the stream.

Regular (non-Splits) - By default the Regular option is selected for normal Play on the station.

Master Audio/Splits Player - The Master Audio/Splits Player option is used for both Master Splits and Splits Player Stations. When an asset or spot block for the master station is assigned the Split behavior, Master Audio or Master Monitor, this signals the splits player station to play an asset using an assigned Master Audio/Splits Player stream. The asset may be the same or different depending on the Asset Tagging.

Master Monitor - The Master Monitor option is used to designate what stream should be used by the Master Splits Station when an asset plays on the Mater station with a Split Behavior of Master Monitor.

Select Master Audio for the Streams that are to be used with the Master Audio Split Behavior. Splits are supported in the On-Air, Hot Keys and Stacks modules. Select Master Monitor for the Monitor streams.

7. For each stream select the Asset Types to play on the play stream.
8. For each stream, select the Player that was configured in the computers Play Devices. 
9. Select the Stream Name to use for the Player. 
   
10. Use the Verify if Player is Online  button to verify the players are functioning; the status column will display a green check mark if the player is online and is available to Zetta. If the Player is not online or not functioning a red is visible in the Status column.
11. Click Save to save the added the Player.
12. Repeat steps 2-9 for these additional recommended Stream Groups:

Step Three: Configure the Stream Groups for the Splits Client Station

1. Click Configuration | Stream Groups
2. Click the Add New Stream Group  button to create a new Player. 
3. Name the Stream Group as desired
4. In the second line enter a description of the Stream Group (optional)
5. To add play streams for the a Stream Group, click the Add Playback Stream Mapping button for the desired number of streams
6. For each stream, select the Player that was configured in the computers Play Devices. 
7. Select the Stream Name to use for the Player. 
8. By default the Regular (non-Split) option should be selected for normal Play on the station. Splits Event Routing will only need to be configured if the station is NOT a 24/7 split player station.
9. Select the Master Audio/Splits Player for each Splits Event Routing stream. Splits are supported in the On-Air, Hot Keys and Stacks modules.
   
10. Use the Verify if Player is Online  button to verify the players are functioning; the status column will display a green check mark if the player is online and is available to Zetta. If the Player is not online or not functioning a red is visible in the Status column.
11. Click Save to save the added the Player.
12. Repeat steps 2-9 for these additional recommended Stream Groups:

Step Four: Configure the Master Station

A Master Station is simply a Station that is assigned to a splits client as its master station. See the Create a Station instructions if a new station is needed for the Master station.  

1. Click Configuration | Station
2. Select the Station that is to be the Master Station
3. Select the Splits Mode tab
4. Optionally, select the Spot Block Matching Method in the Master station.
5. Optionally, select the option to use for Use Longest Spot Block Length, to allow Zetta to adjust the fill length on the Matched Spot Blocks to the Longest Length. If GSelector is integrated with Zetta, enable the Update the Spot Blocks in GSelector when the Fill Length changes option in the Logs Settings tab to send these changes to GSelector.
6. Optionally, set the Override Split Behavior on all Spot Blocks.
7. Optionally, set the Delay sending Split messages by x seconds.
8. Optionally, set the options for the Spot Blocks Dynamic Live Event Lengths.
9. Leave Splits Player settings at the default. These options are used for the Splits Client.
10. Optionally, select the Station participates in longest Spot Block negotiation option in the Spot Block Length Matching section.
11. Click the Save  button to save the station settings.

Step Five: Configure the Splits Station

A Splits Station is simply a Station that is assigned to a Splits Master station. See the Create a Station instructions if a new station is needed for the Splits station.  

1. Click Configuration | Station
2. Select the Station that is to be the Splits Client
3. Select the Splits Mode tab
4. In the Splits Player section select the Split Master Station to use for this Splits Client Station configured above.
5. Optionally, select the Merge Master Log Events into Split's Live Metadata option.
6. Optionally, select the Show Master Log Events in Split's On-Air Module option.
7. Optionally, select the Use Master Log Events for Unresolved Tags on the Split option.
8. Optionally, select the Splits Master Provides Fill content option.
9. Optionally, select the Manage Audio Routing during Splits Playback. This option also requires the selection of a Split Master Route using the Split Master / Network Route option in the Audio Routing tab of the Station Configuration window.
10. Optionally, select the Auto Create Spot Blocks if Missing option.
11. Optionally, set the On Early Completion of Splits Master Block option.
12. Select the Splits Name Matching to use. The default is Tags then Imaging.
13. Optionally, select the Station participates in longest Spot Block negotiation option in the Spot Block Length Matching section.
14. Click the Save  button to save the station settings.

Step Six: Setting the Split Behavior for an Asset

1. Click Modules | Library
2. Select the tab for the Asset to be edited
3. Double click the desired Asset
4. Click the Station Specific tab
5. Select the Master Station from the Select Station drop-down.
6. Select the Tag if one exists.  See Step Seven: Create Tags to create a new Tag.
7. Select the Split Behavior for the Master Station to use when the split occurs. 
   

8. Click Save to save the changes to the Asset.

Step Seven: Create Tags if using Tags in Splits Name Matching

1. Click Modules | Library
2. Select the Tags tab
3. Click Add new media button
4. Give the Tag a Name. When running splits across multiple Zetta sites the tag name MUST match at each site. If using Tags then Imaging or Imaging then Tags for Splits Name Matching, the Tag and the Image name MUST match.
5. Enter an External ID.
6. Select the Routing Behavior if using the Manage Audio Routing during Splits Playback option in the Splits Player Configuration.
7. Drag and Drop the desired asset that is to play on the Master Splits Station to the Tag window from the Library Module.
8. In the Station column set the station to the Master Station.
9. Drag and Drop the desired asset that is to play on the Splits Client Station to the Tag window from the Library Module.

   Important Note!

   The assets selected for the Split Master and the Split Client should have approximately the same Runtime. Zetta will use the Maximum Stretch and Maximum Squeeze values to achieve an exact length to allow the Split Client to rejoin the Split Master at the correct time.  If the assets cannot be stretched/squeezed to match an error will appear in the Tag window for the asset.

10. In the Station column set the station to the Split Client Station
    
11. Click the Save button to save the changes to the Tag.

Step Seven: Create Imaging if using imaging in Splits Name Matching

1. Configure Shifts for each of the stations to have Imaging
2. Click Modules | Library
3. Select the Imaging tab
4. Click Add new media button
5. Give the Imaging a Name. When running splits across multiple Zetta sites the Imaging name MUST match at each site. If using Tags then Imaging or Imaging then Tags for Splits Name Matching, the Tag and the Image name MUST match.
6. Insert an External ID
7. Optionally, change the Routing Behavior. The default is to Mute the Network Route.
8. Set the Target Length for the Imaging assets to be added.
9. Optionally, select a Kill Date using the Calendar Control.
10. In the Assignment context pane select a Station, Virtual station, Station Group or the Shared Rotation (Global).
11. If a Station is selected the Fallback order pane will show any defined shifts in Level 1. Select a shift to add assets to that shift.
12. Drag and Drop asset from the Library Module to assign them to the shift.
    
13. Select the Station Rotation in Level 2
14. Drag and Drop asset from the Library Module to assign them to the shift.
    
15. Select the Splits Station to drag and drop assets to each level for play during splits mode.
16. Optionally select the Shared Rotation (Global) Assignment to drag and drop assets to include in the Imaging.
17. Optionally select a Station Group Assignment to drag and drop assets to include in the imaging.
18. Click the Save button to save the changes to the Imaging.

Step Eight: Setting the Split Behavior on a Spot Block

The Split Behavior for a Spot Block can be set in the Clocks/Logs or in GSelector using GSelector Integration.  To set the Split Behavior in GSelector, see the GSelector Help Guide

1. Using the Modules menu select the Clocks or Logs module.
2. Right-click a location in the Log or Clock
3. Select Insert Control Event from the menu
4. Select Spot Block from the Control Event Consideration window
   
5. In the Properties window set the Fill Length for the Spot Block if a Block Fill Category has been selected
6. Select the Split Behavior for the Spot Block
7. Drag and drop the Spot Block Control Event or simply double click the words Spot Block. Zetta will enter the Spot Block into the previously selected location in the Log or Clock.

The Final Steps are to Schedule the Logs for the Stations, this can be done with GSelector Integration, Clocks or through Flat File Load. Then open the On-Air module for each station and set the Spilt Clients to Split Player to: mode. In Splits Player mode the title header of the On-Air module will be purple by default and will show a status for the master station. The color of the title header can be changed in the On-Air section of the Themes and Appearances window. When the Show Master Log Events in Split's On-Air Module option is checked, for the Splits Station, the events playing on the master station will be shown in the On-Air module of the splits station. This allows users to see events playing from the master station with the splits player events in the On-Air module of the splits station. When the Sequencer is in Splits Player mode the Master Log Events will be shown with a Master icon and the title header of the On-Air module will show a filter icon. This filter can be used to switch the view between showing and not showing the master log events.

The color of the stripe on the left of this icon can be changed by modifying the 'Split Master Event color' option in Themes & Appearances.

Configuring External Splits for Zetta Sites

External Splits will use the Serial/TCP/UDP GPIO connection to communicate between the Master and the Split Forwarder.

The following assumes that Splits is enabled at both sites, the Stations, Players and RS232, TCP or UDP Splits GPIO device have been created and configured.

The following steps can be used to configure Zetta sites for External Splits:

In this section: show/hide show/hide

External Splits: Configure the Master Station

See the Create a Station instructions if a new station is needed for the Master station.  

1. Click Configuration | Station
2. Select the Station that is to be the Master Station
3. Select the Splits Mode tab
4. Optionally, select the Spot Block Matching Method in the Master station.
5. Optionally, set the Override Split Behavior on all Spot Blocks.
6. In the External Splits section, select a RS232, TCP or UDP Splits GPIO device that has been configured to send splits messages for the Master Station using the Splits Master: Sends External Splits Message Over drop-down option. This is how this Master station will communicate with the Split Forwarder station at the remote site.
   1. Optionally, select the Publish Master Queue for Live Metadata option to use for sending xml data to the split stations.
   2. Optionally, select the Number of Events to Publish or select the Entire Sequencer Queue.

8. Leave Splits Player settings at the default. These options are used for the Splits Client.
9. Click the Save  button to save the station settings.

External Splits: Configure a Virtual Station at the remote site as the Split Forwarder

See the Create a Virtual Station instructions if a new virtual station is needed as a Splits Forwarder at the remote site. The Virtual Station configured here will be the Splits Forwarder for the Master Station at the head end site.

1. In the Configuration Menu, click Virtual Stations.
2. Optionally, select the Spot Block Matching Method in the Master station.
3. Optionally, set the Override Split Behavior on all Spot Blocks.
4. If using a Serial/TCP/UDP connection, select the Splits Mode tab to set the Splits Forwarder: Receive External Splits Message Over RS232 Splits, TCP Splits or UDp Splits GPIO device. The 'Splits Master: Sends External Splits Message Over' device will need to be set in the Splits tab of the Master Station at the sending site.
   
5. Leave Splits Player settings at the default. These options are used for the Splits Client.
6. Click the Save  button to save the virtual station settings.

External Splits: Configure the Split Forwarder in Splits Station as the Master Station at the remote site

The Split Client Stations should already be created at the remote site. See the Create a Station instructions if a new station is needed.

1. Click Configuration | Station
2. Select the Station to configure as the Splits Client. 
3. Select the Splits Mode tab.
4. Select the Split Forwarder station to use for this Splits Client Station configured above.
5. Optionally, set a time for the Offset incoming Split messages in minutes when using Serial connections to the Split Master. This value can be positive or negative.
   
6. Optionally, select the Merge Master Log Events into Split's Live Metadata option.
7. Optionally, select the Show Master Log Events in Split's On-Air Module option.
8. Optionally, select the Use Master Log Events for Unresolved Tags on the Split option (if Merge Master Log Events into Split's Live Metadata and/or Show Master Log Events in Split's On-Air Module is enabled).
9. Optionally, select the Automatically Create Spot Blocks if Missing option.
10. Select the Splits Name Matching to use. The default is Tags then Imaging.

11. Click the Save  button to save the station settings.

The Final Steps are to Schedule the Logs for the Stations, this can be done with GSelector Integration, Clocks or through Flat File Load. Then open the On-Air module for each splits station and set the mode to Split Player to: mode. In Splits Player mode the title header of the On-Air module will be purple by default and will show a status for the master station. The color of the title header can be changed in the On-Air section of the Themes and Appearances window. When the Show Master Log Events in Split's On-Air Module option is checked, for the Splits station, the events playing on the Master station will be shown in the On-Air module of the Splits station. The External Splits Station's On-Air Module will show the Master Log Events with a Master icon but the event progress will not be shown. However, the event that is playing on the Master Station will be shown with a blue border.  When the Sequencer is in Splits Player mode the title header of the On-Air module will show a filter icon. This filter can be used to switch the view between showing and not showing the master log events.

Configuring ZCast Splits for Zetta Sites

ZCast Splits will use a ZCast Split Forwarder connection to communicate. ZCast connections use an Outbound ZCast connection at the head end site for the Master station communication and an Inbound ZCast connection at the remote site for the Split Forwarder.

The following assumes that Splits is enabled at both sites, the Stations and Players have been created and configured.

The following steps can be used to configure Zetta sites for ZCast Splits:

In this section: show/hide show/hide

ZCAST: Configure the Master Station at the head end site

See the Create a Station instructions if a new station is needed for the Master station.  

1. Click Configuration | Station
2. Select the Station that is to be the Master Station
3. Select the Splits Mode tab
4. Optionally, select the Spot Block Matching Method in the Master station.
5. Optionally, set the Override Split Behavior on all Spot Blocks.
6. Leave Splits Player settings at the default. These options are used for the Splits Client.

8. Click the Save  button to save the station settings.

ZCAST: Configure a Virtual Station at the remote site as the Split Forwarder

See the Create a Virtual Station instructions if a new virtual station is needed as a Splits Forwarder at the remote site. The Virtual Station configured here will be the Splits Forwarder for the Master Station at the head end site.

1. In the Configuration Menu, click Virtual Stations.
2. Optionally, select the Spot Block Matching Method in the Master station.
3. Optionally, set the Override Split Behavior on all Spot Blocks.
   
4. Leave Splits Player settings at the default. These options are used for the Splits Client.
5. Click the Save  button to save the virtual station settings.

ZCAST: Configure the Split Forwarder in Splits Station as the Master Station at the remote site

The Split Client Stations should already be created at the remote site. See the Create a Station instructions if a new station is needed.

1. Click Configuration | Station
2. Select the Station to configure as the Splits Client. 
3. Select the Splits Mode tab.
4. Select the Split Forwarder station to use for this Splits Client Station configured above.
5. Optionally, set a time for the Offset incoming Split messages in minutes when using Serial connections to the Split Master. This value can be positive or negative.
   
6. Optionally, select the Manage Audio Routing During Splits Playback option. This option also requires the selection of a Split Master Route using the Split Master / Network Route option in the Audio Routing tab of the Station Configuration window.
7. Optionally, select the Auto Create Spot Blocks if Missing option.
8. Optionally, set the On Early Completion of Splits Master Block option.
9. Select the Splits Name Matching to use. The default is Tags then Imaging.
10. Click the Save  button to save the station settings.

ZCAST: Create a Master Station to Split Forwarder ZCast Connection

This option of sending/receiving Master Splits messages can be used if the External Splits is not used for communication. The On-Air module for the Splits station will not show the Master Log Events for ZCast Splits. But the Status icon will show if the Master station is Online.

1. On the Receiving site, click ZCast Connections from the Configuration menu.
2. Click the Add Connection button
3. Select Inbound for the Connection Type
4. Enter a Name to describe the connection.
5. Optionally, enter a Description of the connection.
6. Click the Create Connection Key button.
   
7. Select the Show Permissions Expand button for the Split Forwarder Station.
8. Select Splits Forwarder.
   
9. Click Save to save the ZCast Connection.
10. Click Export to export the ZCast Connection configuration to a file.
11. Transfer the file to the sending site via Email, shared folder or other means.
12. On the Head end Sending site, click ZCast Connections from the Configuration menu.
13. Click the Import button to import the ZCast Connection configuration file.
14. The Connection Type is automatically set to Outbound.
15. Edit the Name if desired.
16. Optionally Edit or enter a Description.
17. Select Test
18. Select the Local Station (Master) that has access to the Remote (Split Forwarder) Station.
19. Select Allow Splits
    
20. Click Save to save the ZCast Connection.

The Final Steps are to Schedule the Logs for the Stations, this can be done with GSelector Integration, Clocks or through Flat File Load. Then open the On-Air module for each splits station and set the mode to Split Player to: mode. In Splits Player mode the title header of the On-Air module will be purple by default and will show a status for the master station. The color of the title header can be changed in the On-Air section of the Themes and Appearances window.

Troubleshooting Splits

When the Master Station is communicating correctly with the Local Split Stations the status icon will be green and a Listening icon with a number will appear in the On-Air title bar of the Master Station. A tooltip will show what stations are listening when the mouse is hovered over the number.

Use the GPIO History at each site to verify the External Splits are communicating.

The Splits IN and OUT messages are logged with the Sequencer processes and stored on the local computer (..\ProgramData\RCS\Zetta\!Logging\Debug\xx_<ComputerName>_Zetta.SequencerLauncher.exe_ProcessID.xlog). The first two characters of the file name is the date the file was created. The date is followed by the Windows name for the computer. This file can be viewed by opening it in the xLogViewer application found in the RCS program group on the local computer. The New messages that should appear will look similar to the examples below:

4-23 09:33:01.596 | Seq    | SPLITS          | A - Split 1     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:01.665 | Seq    | SPLITS          | S - Split 2     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:06.492 | Seq    | SPLITS          | WRCS-FM     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:06.494 | Seq    | SPLITS          | S - Split 2     | SPLIT_IN [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:06.495 | Seq    | SPLITS          | A - Split 1     | SPLIT_IN [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:16.622 | Seq    | SPLITS          | A - Split 1     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:16.702 | Seq    | SPLITS          | S - Split 2     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:21.658 | Seq    | SPLITS          | WRCS-FM     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:21.660 | Seq    | SPLITS          | S - Split 2     | SPLIT_IN [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:21.660 | Seq    | SPLITS          | A - Split 1     | SPLIT_IN [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

4-23 09:33:31.652 | Seq    | SPLITS          | A - Split 1     | SPLIT_OUT [ZETTA_SPLITSMASTER]:  SEQUENCER_DATA - INVALID, Split Id: 0,

Welcome < Features < Zetta Splits