Important Note!
The entire Zetta system will need to be rebooted following any changes made on this tab.
Welcome < Configuration < System Configuration < Transport Layer
To communicate between different processes and computers, Zetta relies on messaging based on networking protocols used via local area network (LAN) or wide area network (WAN). While the vast majority of users have their Zetta system set up to use User Datagram Protocol (UDP), Transmission Control Protocol (TCP) may be a better fit for specific environments and configurations. UDP is the default setting. Consult RCS before making any adjustments on this tab; making changes without prior approval of RCS may introduce performance issues or affect reliability of the system. The entire Zetta system will need to be rebooted following any changes made on this tab.
In this Topic: show/hideshow/hide
Compress large packets over (x) bytes
Compress packets using Protobuf
Use the Protocol type drop-down to select the protocol Zetta will use to communicate with other computers and servers. Consult RCS before changing to TCP as a Transport protocol.
|
Important Note! |
The entire Zetta system will need to be rebooted following any changes made on this tab. |
User Datagram Protocol (UDP) is the default Transport protocol used in Zetta. Consult RCS before making any adjustments to the UDP settings.
The Transmission Control Protocol (TCP) is not typically used, but may be a better fit for specific environments and configurations. Consult RCS before changing to TCP as a Transport protocol.
The "Compress large packets over" field is used to set the maximum size in bytes a packet can be before it is compressed.
The "Compress packets using Protobuf" option is enabled by default. This option allows the data to be compressed upon send and de-compressed upon recieve. The concept is similar to zipping and unzipping a file. This reduces strain on the network, particularly in large setups with many computers.
Select the "Log .NET TCP tracing" option to enable advanced logging of the TCP communications. This may help when troubleshooting certain networking issues. The logging is saved to the XX_Zetta.exe.xlog file in the “C:\ProgramData\RCS\Zetta\!Logging\Debug” folder.
These "TCP Specific Settings" are shown when TCP is selected as the Protocol type. Consult RCS before changing the TCP specific settings.
Zetta uses three tiers to send important realtime messages. The first tier is used to send highly important messages for example messages from/to Sequencer, Player and GPIO. Tier two and three are used for less important messages from other Zetta processes that are not critical to on-air performance. This ensures that on-air critical communications do not get delayed when being sent through the network. This section allows the configuration of the connection state, Keepalive packets and Bad endpoint lockouts.
The "Establish Connection Timeout values" feature affects the amount of time before Zetta will timeout when a TCP client connects to a TCP server.
The "Send Packets Asynchronous" feature is used when the TCP transport sends packets between processes and computers.
Welcome < Configuration < System Configuration < Transport Layer
© 2007-2024 RCS All Rights Reserved.