Supported fields, Input file fields – Grass Valley K2 Edge Protocol Manual v1.0 User Manual
Page 40
K2 Edge Protocol Manual – document version 1.0 – Page 40
6.3. Supported fields
A complex source string is limited to a set of well-defined field/value pairs, some of them mandatory, the
others optional.
6.3.1. Input file fields
These fields specify the media file(s) to be played. It is possible to compose a clip out of several essence
files, for example a video file and number of audio files. Normally, the
file0 field will be sufficient to
define an input file that holds all the needed streams.
field
name
field type value
description
since
file0 mandatory file name
or path
The name of the first (and possibly only) input media file, including
extension. Relative or absolute paths are allowed.
Examples: a000123.avf, or clips/a000123.mpg, or
../clips/a00012.mov, or /some/absolute/path/a000123.mxf.
1.56
file
Identical to
file0 field described above.
Deprecated since nexos-v1.56. Please use the
file0 field from
now on.
file1
...
fileN
optional
file name
or path
The name of extra input media files, use for clips that use separate
physical files for the different elementary streams.
The first additional input file must be defined with field
file1,
followed by
file2, file3, etc. No gaps are allowed in the field
name numbering. Input media files are processed in order of
numbering. See field
file0 for supported formats.