Error messages – EVS IPDirector Version 6.2 - June 2013 DATABASE EXPLORER User Manual User Manual
Page 34
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.
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.
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 grid.
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.
3.3.3.
Error Messages
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).
Bad data in one or more metadata tag
Bad metadata file: bad/incoherent
data (e.g. IN < OUT, bad value).
22
3. Clips, Clip Elements and Nearline Files
EVS Broadcast Equipment S.A. - June 2013
Issue 6.2.A