ZEC Outputs

zec supports the following output types udp – target is a udp or rtp stream, over unicast or multicast rtmp – real time messaging protocol streams can be played on systems that accept this protocol as input originally designed to enable adobe® flash® streams to be sent between a server and a client, rtmp has become a popular protocol for streaming into content delivery networks (cdns) rtmps rtmp over a tls/ssl connection push stream – push streams are zixi protocol streams destined for other zec instances and zec in “accept mode” tcp – tcp protocol provides reliable transmission guarantee for no loss of frame its bandwidth probing and congestion control will attempt to use all of the available bandwidth between the server and client, fetching content as quickly as possible while being friendly to other (tcp) traffic on the same links the tcp output can push the stream directly to a tcp socket or to an http server http push – the http push output stream can be encapsulated in hls or dash the source of the output stream is a predefined adaptive group that has been configured in the zec adaptive groups https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887948807/zec+adaptive+groups screen the configuration of the stream includes the option to delete outdated stream fragments on the server output streams can be pushed to one zecs or zec aws – the aws output stream can be encapsulated in hls or dash and be pushed to an aws s3 bucket or elemental mediastore srt – the srt output can be pulled to/from an srt enabled device and is configured via zen master or zec api only srt stands for ‘secure reliable transport’ and is an open source video transport protocol and technology stack srt uses secure streams and easy firewall traversal to optimize streaming performance and deliver high quality video over even the most unreliable networks srt listener/pull – the srt client output can be pushed to an srt enabled device and is configured via zen master or zixi api only srt stands for ‘secure reliable transport’ and is an open source video transport protocol and technology stack srt uses secure streams and easy firewall traversal to optimize streaming performance and deliver high quality video over even the most unreliable networks rist – the rist output can be push streams or have them pulled to/from a rist enabled device rist seeks to provide reliable, high performance media transport by using udp at the transport layer to avoid the inefficiencies of tcp, then layering on top forward error correction and retransmits to add the reliability inherently absent from udp 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 zec using output templates docid\ xktjovywiwozj0b3d5uqg zec adding outputs docid 60guo4kae0kdmuzfbneqv zec viewing existing outputs docid 8jky7jhajizjam nx4bf5 zec searching for output streams docid aouypihlfaqtxehgsol3 zec performing actions on output streams docid\ txfzlbru6r8pusyy31ioc zec performing actions on multiple outputs docid\ ljjn3c2cfbkvq9ewuwcsx decrypting an output stream in zec docid 9ngu36geigg56k4toivug zec using output templates docid\ xktjovywiwozj0b3d5uqg zec network bonding docid\ q wae7q3d1gzmtjgckjgn