Zixi Broadcaster/ZEC v18 Docum...
Zixi Edge Compute (ZEC)
ZEC Outputs
1 min
zec supports the following output types udp – delivers the output stream as a udp or rtp stream over unicast or multicast this output type is commonly used in managed networks where low latency is required and packet loss can be tolerated or handled downstream rtmp – outputs the stream using the real time messaging protocol (rtmp) rtmp streams can be ingested by systems and platforms that accept rtmp as an input format and are commonly used for delivery into content delivery networks (cdns) and live streaming platforms rtmps provides rtmp output over a tls/ssl–secured connection rtmps is functionally identical to rtmp while adding transport level encryption for secure stream delivery push stream – outputs the stream using the zixi protocol and pushes it to a zixi broadcaster instance operating in accept mode this output type enables reliable, low latency transport with zixi’s advanced error correction and congestion control tcp – outputs the stream over tcp, providing reliable, lossless delivery tcp dynamically adapts to available bandwidth and congestion conditions, ensuring complete frame delivery while remaining fair to other tcp traffic on the network the stream can be pushed directly to a tcp socket or to an http server http push – outputs the stream over http, encapsulated as hls or dash the output is based on a predefined adaptive group configured in the https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887948807/zec+adaptive+groups screen configuration options include managing segment lifecycle, such as automatically deleting outdated fragments on the destination server streams can be pushed to one or more zec instances aws – outputs the stream as hls or dash and pushes it to aws based storage and delivery services, including amazon s3 buckets or aws elemental mediastore this output type is commonly used for cloud based distribution and downstream processing workflows srt (listener / pull) – configures zec as an srt listener, allowing an srt enabled device to pull the stream from zec this output type is configured through zen master or the zec api srt (secure reliable transport) is an open source video transport protocol designed to deliver high quality streams over unpredictable networks using encryption, retransmission, and efficient firewall traversal srt (caller / push) – pushes the output stream from zec to an srt enabled destination device this output type is configured through zen master or the zec api and uses the same secure reliable transport (srt) protocol to ensure reliable, low latency delivery over challenging network conditions rist – outputs the stream using the reliable internet stream transport (rist) protocol, supporting both push and pull workflows with rist enabled devices rist builds reliability on top of udp by combining retransmissions and forward error correction (fec), delivering high performance, low latency transport without the inefficiencies of tcp when zec pulls a stream, a pull stream definition is generated automatically in zec, the stream is identified in the name and destination columns of zec with the id and ip address of the zec that pulls the stream automated output configuration with output templates instead of manually creating an output and then connecting the output to an input, you can define output templates with rules for automatic creation of outputs with predefined settings the template includes an input pattern when an input pattern matches the pattern of an incoming input stream, the output is created automatically for more information about output templates, see docid 68z vgwe fajsjim8p4d docid\ jzyzus3pzryf6uy8nrtjx docid 6ne770qkpgnbcdpaniwaa docid 4ips55m jbkjdesffaqf7 docid\ qonxy6r6fi1ejdo1npqyn docid\ akr5rykcetjlimzm9wiiz docid\ zzwfcdcntf960viadh2j docid 68z vgwe fajsjim8p4d docid\ zsdxvbnwyydhsh9gr8tbe

