ZEC Adding File Streams

this input creates a file input for the zec from a local or mounted disk and subsequently streams it to the end user if the stream is an mpts stream, you can either upload it as an mpts file or you can demux it into separate spts input streams to demux the mpts stream, create the input stream by following the instructions below, and then follow the instructions in the demuxing an mpts stream docid\ fil363whm6ibixibmn2fz section to add a file stream in the zec navigation menu, click the inputs tab in the menu bar, click +new input the add a new input stream window is displayed enter the unique stream id note this must be identical (case sensitive) to the stream name configured in the sending zixi broadcaster or mediaconnect select the maximum concurrent connections to this stream from the max outputs drop down list default unlimited select the show in matrix check box to display this stream in the matrix (see zec using the matrix docid\ ofxethpsuo9eimqpwfzea ) default selected select file for the input stream specify the stream parameters (see the input stream parameters table docid\ uvytrjlt w6ur81jkdfti below) if you want to enable encryption , select this checkbox ( see input stream parameters table docid\ uvytrjlt w6ur81jkdfti ) for more information, see zec encrypting an input stream docid\ qern0zffbaztl vrw4rn if you want to configure the recording parameters , specify them in the respective fields ( see input stream parameters table docid\ uvytrjlt w6ur81jkdfti ) click ok the “input added” message appears at the top of the screen the stream is added to zec and now appears in the list of streams available in the zec inputs ui input stream parameters table parameter description stream parameters path see notes on the file path docid\ uvytrjlt w6ur81jkdfti below enable encryption select this checkbox to encrypt the input stream the stream encryption prevents any further processing, such as analysis, transcoding, etc the encryption works in the following way if the stream has been encrypted at the source the stream will remain encrypted regardless of the output type zec can only encrypt the stream after it has been decrypted if the stream is being encrypted by the zec it will be encrypted only if the output is a zixi pull or zixi push output all other outputs will send out an unencrypted stream for more information, see zec encrypting an input stream docid\ qern0zffbaztl vrw4rn encryption type (for encryption enabled) specify the type of encryption (aes 128/192/256) encryption key (for encryption enabled) click generate to generate an encryption key the generated encryption key must be sent to the end user to decipher the received encoded stream notes on the file path the paths the broadcaster understands here are not operating system paths full system paths such as /home/user/videos/file ts or c \home\videos\file ts will not work instead, the file you wish to use must be in the root folder for the broadcaster the location of the root folder is shown in the general settings of the settings tab note that to change the root folder location, you must edit the broadcaster info xml file, which is located in the broadcaster installation folder on the files tab, you can upload files to the broadcaster for use as file streams and also create subfolders to organize files for files in subfolders, the path is relative to the root folder for example, if you create a videos subfolder and within the videos folder create another subfolder called nature, and you want to use a file called forest ts for the file stream, the path would be /videos/nature/forest ts advanced mode 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 file input advanced mode general latency offset \[ms] support injection scte 35 pid inject metadata remove old scte 35 packets keep stream stream parameters synchronize playback checkbox compression checkbox fast connect checkbox synchronize playback synchronize playback ties a looping file's position to wall clock time instead of to when the input was started when it's off (default) the file simply starts from the beginning when the input starts, and loops from there if you restart the input, or start the same file on a second broadcaster, each one begins at the start of the file at the moment it was started — so they will not be at the same point in the file as each other when it's on the broadcaster calculates where in the file it would be if the file had been playing continuously since a fixed reference time and jumps straight to that position this means the playout position is deterministic from the clock — restarting the input resumes at the "correct" point for the current time rather than jumping back to the beginning two or more broadcasters playing the same looping file will stay aligned with each other because they all compute their position from the same clock reference rather than from their individual start moments this is what makes it possible to have multiple servers (or a restarted input) present the same looping file content in lock step, as a continuous "always on" channel, rather than each copy starting from frame one whenever it happens to be launched pcr, pts and dts are all derived from the ntp time