EVS IPDirector Version 5.6 - May 2009 Part 3 User's Manual - Manual (Page 34)

IPDirector Version 5.6 – User Manual – Part 3: Browsing
EVS Broadcast Equipment – May 2009
Issue 5.6.D
23
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 and Proxy (lo-res) files.
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
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).
Bad data in one or more metadata
tag Bad metadata file: bad/incoherent data
(e.g. IN < OUT, bad value).
Unsupported A/V format. You need to
transcode your file before importing
it to IPDirector nearline. Unsupported A/V format (recognised
by TimeCode Extractor but not
supported natively).
Could not read A/V file. This file
might be corrupted or in the wrong
format. Corrupted A/V file. TimeCode
Extractor or EVS MXF.dll cannot read
the file.