This chapter contains various matrices indicating what formats have been tested successfully with the Oracle DIVArchive Partial File Restore operation. Testing with samples provided by the customer is recommended to confirm interoperability. Oracle makes no commitment if variations in the encoding profiles cause issues with the Partial File Restore feature. All formats support AUTO_DETECT.
Contact Oracle Support for more details about each implementation.
This chapter includes the following information:
GXF Partial File Restore is supported on Windows in the following formats:
Aurora Edit
MPEG2 D10 MPEG2 I-frame
MPEG2 D10 MPEG2 LGOP
BitScream
DV25
DIVArchive TMCommunicator
DV25
DV50
MPEG2 D10
K2 Media System
MPEG2 D10 MPEG2 I-frame
MPEG2 D10 MPEG2 LGOP
K2 Media System / Summit
AVC-I
DVCPRO
XDCAM HD
Mseries
MPEG2 D10 MPEG2 I-frame
MPEG2 LGOP
NewsEdit
DV25
DV50
MPEG2 D10 MPEG2 I-frame
PDR
MJPEG
Profile XP
DV25
DV50
MPEG2 D10 MPEG2 I-frame
MXF standard specification (SMPTE377M) defines multiple operational patterns. Only OP1a is supported. MXF Partial File Restore is supported on Windows in the following formats:
Manufacturer | Product | Release | Qualified Video Essence |
---|---|---|---|
AmberFin, Ltd. | iCR | 4.0.3, 4.5.1 | MPEG2 LGOP HD |
Avid | TRMG | 2.97
1.00, 3.00 3.00 |
MPEG D10
DV25 XDCAM HD |
Canopus Company, Ltd. | EDIUS | 5.00 | XDCAM HD |
EVS - OpenCube | MXFTk Advanced | 2.1.10.0
2.2.4.0 |
DV50, DV100
DNxHD |
Harris Corporation | Nexio | 1.0.0.0 | DV50 |
Leitch | VR475 | 1.00 | DVCPRO HD, DV50 |
Ligos Corporation | MediaRig | Ligos MXF 1.0 | MPEG2 D10 |
Matrox Electronics | DSX | 50.46.48.0 | XDCVAM HD |
MOG | MXFspeedrail | Toolkit 4.2.1.326 | MPEG2 D10 |
OCFoot 1 | OCTk | 2.1 | MPEG2 D10 |
Omneon Video Networks | Omneon Media Subsystems | 4.6.0.0
4.7.0.0 |
MPEG2 D10
DV25 |
Oracle | Bitscream
TMCommunicator TMCommunicator |
3.1.0.90
3.1.0.74 4.1.1.245 |
DV25
MPEG2 D10, DV25, DV 50 DVCPRO HD, DNxHD |
Quantel | GenerationQ | C3.0 rev 13.18
C2.1 rev 22.43 V2.1 22 T4.0 R&D, C3.6 11.003 |
MPEG D10
MPEG D10 MPEG D10 AVC-i |
SAMMA Systems | MXF for Oracle SAMMA MJPEG2K | 0.2.0.41 | MJPEG2K |
SeaChangeFoot 2 Foot 3 | MediaClient | 2.3.0.12 | MPEG2 D10 |
Snell & Wilcox, Ltd. | iCR | 3.0.0 | MPEG2 LGOP HD |
Sony | Opt
Opt eVTR HA XDCAM Transfer |
1.00
1.21, 1.22 1.00 1.00 Sony MXF SDK 2.1.0.0 |
MPEG2 D10
XDCAM HD MPEG2 D10 MPEG2 D10 XDCAM HD |
Telestream | Flip FactoryFoot 4 | 3.00 | MPEG2 D10, XDCAM HD |
Thomson Broadcast and Media Solutions, Inc. | Universal Interface Module | 2.0.6.3, 2.0.14.2 | MPEG2 D10 |
Thomson Grass Valley, Inc. | K2 Media Systems | Engineering Release
Toolkit 9.8.7.0 |
MPEG2 D10
XDCAM HD |
Footnote 1 MXF files created by OCTk are the files created by Oracle SAMMAsolo.
Footnote 2 MXF generated by Seachange are supported as standalone MXF files (no .pd
or .vix
file).
Footnote 3 Starting with DIVArchive 7.2.2, the Vstream protocol is no longer supported for Seachange sources and destinations. This applies to the source types SEACHANGE_BMC and SEACHANGE_BML when no -ftp option is specified (indicating Vstream protocol is in use, not FTP).
Footnote 4 DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.
The applicable wrapper format is a single AVI file per object, and may contain audio tracks. This Partial File Restore is supported by AUTO_DETECT only.
Supports DVSD and PCM video and audio essences.
Supports DVSD and PCM video and audio essences.
The applicable file format is a single AVI file with separate WAV files. The AVI file contains a single video track, and the WAV files contain a PCM sample format. This Partial File Restore is supported by VIDEO_FORMAT_AVI and AUTO_DETECT.
Manufacturer | Product | Release | Supported Video and Audio Essence |
---|---|---|---|
Insipiens | AVI Writer | 1.0.0.0 | MPEG2 LGOP |
Matrox | MQSink Filter Format 4
MQSink Filter Format 6 MQSink Filter for MPEG Format 4 DSX AVI File Format 6 |
2.0.0.271
2.0.0.271 2.0.0.270, 2.0.0.271 1.0.0.362, 1.0.0.401 |
DV25, DV50
Dv25, DV50, DVSD MPEG2 LGOP, MPEG2 I-FrameFoot 1 MPEG2 LGOPFoot 2 , M701 HD |
Telestream | Flip FactoryFoot 3 | Unknown
6.0, 6.1 |
DVSD, MPEG2 LGOP
M701 HD |
Footnote 1 MPEG2 I-Frame supported on 2.0.0.271 only.
Footnote 2 MPEG2 LGOP supported on 1.0.0.362 only.
Footnote 3 DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.
QuickTime is a file wrapper and may contain multiple tracks of various types (audio, video, and so on). QuickTime self-contained clips are supported using OMNEON and AUTO_DETECT.
QuickTime Partial File Restore is supported by Windows Actors only.
Partial File Restore support for QuickTime with MPEG2 LGOP (XDCAM HD 422 with sixteen tracks of audio) is supported as follows, regardless of the type of video or audio content:
The number of tracks per clip is currently limited to thirty.
Tracks must have the same duration and start time.
QuickTime standards support advanced edit list features that are not supported by Partial File Restore.
Each track must be composed of a single valid edit list entry that may or may not start from zero.
Some content types are not supported, including some video and audio combinations. The following table identifies supported types:
Supported Track Types | Cardinality |
---|---|
Video | One video track per clip |
Video | Two video tracks per clipFoot 1 |
Audio | Zero or multiple tracks per clip |
Closed CaptionFoot 2 | One track per clip |
Timecode with a single entry | One track per clip |
Timecode with multiple entries | One track per clip |
Footnote 1 When a Quicktime clip contains two video tracks, the tracks must be synchronized and have the same duration and start from 00:00:00:00.
Footnote 2 Empty Closed Caption tracks are supported.
The format of the video essence is not a criterion in QuickTime Self-Contained clips. In theory, the Partial File Restore for QuickTime should be able to support any type of video essence. Partial file restore is not recommended for the following variations in the video essence format:
Where the video quality supports 420 or 422
Where the number of pixels is not a factor
Where the clip is bit rate independent
The following table describes what has already been tested and does not guarantee that Partial File Restore will support it. The only supported audio formats are AIFF and WAV (LPCM).
Manufacturer | Product | Release | Supported Video Essence |
---|---|---|---|
Dalet | DVCPRO100 | ||
Omneon | Spectrum | 5.x | DV25, DVCPRO, DVCPRO50, DVCPRO HD, MPEG2 D10, MPEG2 I-Frame, MPEG2 LGOP, MPEG2 LGOP HD |
Oracle | SAMMAsolo | Unknown | DV25 |
Telestream | Flip FactoryFoot 1 | MPEG2 LGOP |
Footnote 1 DIVArchive 7.5 ends Oracle support for Telestream Flip Factory. Oracle will provide best efforts to assist customers to transition to other transcoding solutions.
Leitch Exchange Format (LXF) is well defined and Partial File Restore supports specific releases of the file format regardless of the source of the clip (Nexio, Flip Factory, and so on). The supported request format is either AUTO_DETECT or VIDEO_FORMAT_LEITCH.
The LXF Release 0 supported video and audio essences are:
MPEG2 I-frame Standard Definition (SD)
MPEG2 LGOP SD
DV
DVCPRO
DVCPRO50
The LXF Release 1 supported video and audio essences are:
MPEG2 4:2:2 (1080i and SD only)
DV SD
DVCPRO SD
DVCPRO50 SD
DVCPRO HD
The applicable file format is a single DIF or DV file with separate WAV files. WAV files contain the PCM sample format. This Partial File Restore supports Avid Liquid and Omneon Spectrum with DV25 and WAV PCM using either AUTO_DETECT or VIDEO_FORMAT_OMNEON.
Broadcast WAV (BWAV) is a regular WAV file that includes additional information - Bext
and iXML
(optional). Bext
is a broadcast extension containing metadata, including TimeReference
(timecode reference in milliseconds). DIVArchive uses Bext
as a timecode reference for Partial File Restore.
BWAV may also contain and optional metadata called iXML
. The metadata iXML
contains an additional TimeReference
and a frame rate. When iXML
and Bext
are both present, DIVArchive uses iXML
because it contains an accurate frame rate (useful to convert milliseconds to and from a timecode). Without iXML
, the millisecond to timecode conversion is only an approximation.