Adding TAMS Outputs

the tams output allows you to send streams to a cloud repository for more information about tams and why you might want to use it, see tams and zixi docid\ xb6n9zunccgoddabrvsba the input for a tams output must be an adaptive group that generates hls you can produce zixi and/or cmaf as well, but only hls will be sent to tams to create a tams output in the zixi broadcaster outputs page, click + new output the new output window is displayed new tams output select the tams option (radio button) type in the unique identifier for this output in the output name select an adaptive group to be made available on this output from the drop down list note that the adaptive group must include uuids for the video and audio flows see creating new adaptive groups docid\ i8deswrqtzabwg4zowckw select the log this stream checkbox if you would like to generate event logs for this output currently, only oauth is supported for authentication enter the following required information for your tams instance token url (for oauth) client id (for oauth) secret key (for oauth) url (base api url of the tams deployment) if your oauth credentials are scoped for delete permissions, select require 'tams api/delete' (read/write permissions are always requested) select ignore tls certificate errors to prevent the connection from failing because the tls certificate is found to be faulty select a billing code if needed, and provide the password click ok output stream parameters table parameter description output name a unique name for the output input adaptive group the input for a tams output must be an adaptive group that outputs hls, and the uuids for the tams video and audio flows must be entered in the adaptive group configuration latency offset see the latency offset subsection below this table tams authentication token url the server address broadcaster calls to obtain and refresh access tokens required client id the oauth client id used to get access tokens for your tams system required secret key the oauth secret key (sometimes called client secret) used to get access tokens for your tams system required url url for your tams system required require 'tams api/delete' select this checkbox if your oauth credentials are scoped for delete permissions (read/write permissions are always requested) ignore tls certificate errors select this option when streaming to a trusted server that may not have a valid certificate when this option is selected, zixi broadcaster will ignore the tls certificate errors and transmit the stream to its destination billing codes billing codes are used to identify and differentiate traffic on a zixi broadcaster for billing purposes when a billing code is added to a source or target, zixi can track the traffic on that broadcaster input or output separately from other inputs and outputs on the same broadcaster billing codes are created by zixi personnel on the zixi customer portal for a particular organization billing code enter the billing code that corresponds to this stream the relevant billing can be obtained from the organization that received the billing code from zixi billing password enter the password that corresponds to this billing code advanced settings the fields discussed below are optional and available only in advanced mode to enter advanced mode add the url parameter ?advanced=1 to the zixi broadcaster url in your browser and press enter/return to reload the page note the advanced mode settings are generally intended for advanced users and special cases if you do not understand the settings, you should probably accept the default values advanced settings in advanced mode, you have some additional options set latency offset (see below) add custom http headers to the api requests that send the segments to tams (if your tams implementation requires that) enable ifp/talkback enables a return audio channel from the broadcaster to the source, allowing operators, producers, or remote staff to communicate with the contributor during a live transmission latency offset latency offset is a configuration parameter that delays the processing of a transport stream by a defined amount of time (in milliseconds) this delay is not arbitrary—it serves specific operational goals scte 35 cue injection and pre roll support in broadcast workflows, scte 35 markers signal ad breaks or content insertion points by applying a latency offset, the system can inject scte 35 packets ahead of playback , ensuring accurate timing for ad insertion or blackout triggers this is critical for compliance and monetization workflows example zixi broadcaster introduced latency offset to enable scte 35 insertion after the offset for pre roll scenarios stream normalization and timeline alignment hls inputs often arrive with irregular timestamps (pcr, pts, dts) or discontinuities adding a latency offset gives the system time to buffer and normalize segments , repair timeline irregularities, and remultiplex into a stable mpeg ts output this prevents audio drift and switching errors downstream smooth buffering for burst handling when upstream encoders send data in bursts, latency offset combined with buffering helps maintain a steady flow into the broadcaster this avoids jitter and packet timing issues that could disrupt adaptive bitrate workflows