EVS IPDirector Version 5.8 - July 2010 Part 3 User's Manual - Manual (Page 35)

Issue 5.8.B IPDirector Version 5.8 – User Manual – Part 3 – Browsing
EVS Broadcast Equipment – July 2010
24
3.3.1 F
ILES
T
YPES
All the files appearing on the nearline storage are filtered according to a list of
supported extensions. Depending on the extension, they will or will not be visible
in IPDirector.
Files can be classified among three types:
1. files with a non-supported extension and which are not video files: they
will be ignored and will not be visible in IPDirector.
This could be an EVS XML file without an associated A/V file or this could be a
file with a non-supported extension like a dll, or a text file.
2. A/V files with an extension not supported on the nearline: they will be
visible in the Media Files branch of the tree, but no clip will be created, so
they will not be visible in the Clips branch of the tree for most users.
The import status of this kind of files will be ‘unsuccessful’ in the Import
Status column of the Media Files node with the error message stating
‘unsupported format’.
In a future version of IPDirector, it will be possible to import these files by
initiating a transcoding process.
3. A/V files with an extension supported on the nearline: they will be visible in
the Media Files and in the Clips branches of the tree.
This is the case for EVS MXF, QT, OP1A, Proxy (lo-res) and DV DIFF files.
In addition, some multi-files formats, having separate files for audio, video,
and sometimes a reference file, are now supported by IPDirector. With such
files, IPDirector links the different components and only one file appears in the
media files list.
This is the case for QT Ref, OPAtom and MPEG 1 Elementary System.
Metadata of this third kind of files can be obtained from three different sources
which will be reflected in the metadata source column of the Media Files node:
Metadata Source Metadata Source Column
XML metadata file XML
Header of an EVS MXF file EVS MXF
no metadata None
The Metadata files are automatically updated when clip metadata are changed.
E
RROR
M
ESSAGES
The following error messages could appear in the Error Message column of the
Database Explorer grid:
Error Message Source of the Error
Could not read metadata file Bad metadata file: corrupted file or
bad syntax.
Some compulsory tags are missing
from the XML metadata file Bad metadata file: missing tag or
incoherent data (e.g. IN < OUT).