EVS OpenCube MXFTK User Manual
USER MANUAL OpenCube MXFTk® Front-End 2.6
Copyright
EVS Broadcast Equipment SA – Copyright © 2005-2013. All rights reserved.
This publication, including all photographs, illustrations and software, is protected under
international copyright laws, with all rights reserved. Neither this user manual, nor any of
the material contained herein, may be reproduced without written consent of the author.
Disclaimer
The information provided in this user manual is "as is" and without warranty of any kind,
expressed or implied, including those of merchantability and fitness for a particular
purpose, or arising from a course of dealing, usage or trade practice.
This user manual is for informational use only and subject to change without notice.
While every effort has been made to ensure that the information contained in this user
manual is accurate, up-to-date and reliable, EVS Broadcast Equipment SA makes no
warranties or representations regarding the accuracy or completeness of the information.
In no event shall EVS Broadcast Equipment SA or any of its affiliates be liable for any
damage, including incidental or consequential damages, lost profits, or lost data, or any
indirect damages even if EVS Broadcast Equipment SA or any of its affiliates have been
informed of the possibility thereof.
Trademark Recognition
All product names used in this manual are the properties of their respective owners and
are acknowledged.
This product includes software developed by the OpenSSL project for use in the
OpenSSL toolkit (www.openssl.org).
This product includes software developed by the Apache Software Foundation
(www.apache.org).
Improvement Requests
Your comments will help us improve the quality of the user documentation. Do not
hesitate to send improvement requests, or report any error or inaccuracy in this user
manual by e-mail to doc@evs.com.
Regional Contacts
The address and phone number of the EVS headquarters are usually mentioned in the
Help > About menu in the user interface.
You will find the full list of addresses and phone numbers of local offices either at the end
of this user manual (for manuals on hardware products) or on the EVS website on the
following page: http://www.evs.com/contacts
User Manuals on EVS Website
The latest version of the user manual, if any, and other user manuals on EVS products
can be found on the EVS download center, on the following webpage:
http://www.evs.com/downloadcenter
I
EVS Broadcast Equipment S.A.
Issue 2.6.A October 2013
The present document shall be governed by Belgian law. In case of a dispute, all parties
shall submit to the exclusive jurisdiction of the court of Liège.
II
USER MANUAL OpenCube MXFTk® Front-End 2.6
Table of Contents
TABLE OF CONTENTS ............................................................................ III
REVISION HISTORY ................................................................................. V
1. PRELIMINARIES ................................................................................. 1
1.1 MXF File Format .......................................................................................................... 1
1.2 OpenCube MXFTk® Front-End Installation ................................................................. 1
1.2.1 Windows Platform............................................................................................ 1
1.2.2 Linux Platform .................................................................................................. 1
1.2.3 Apple Platform ................................................................................................. 2
1.2.4 OpenCube MXFTk® Front-End Activation ...................................................... 2
1.3 OpenCube MXFTk® Front-End Overview ................................................................... 2
2. OPENCUBE MXFTK® FRONT-END IN PRACTICE ........................... 4
2.1 MXF File Creation ........................................................................................................ 4
2.1.1 Operational Pattern and Input Files Selection ................................................. 4
2.1.2 Single and Multi-file Selection ......................................................................... 7
2.1.3 Output File Selection – Standard Operational Patterns .................................. 9
2.1.4 Output File Selection – Atomic Operational Patterns ....................................10
2.1.5 Source and Output Package Edition .............................................................11
2.2 MXF File Browsing .....................................................................................................12
2.2.1 File History .....................................................................................................12
2.2.2 File Packages ................................................................................................13
2.2.3 Data Tracks ...................................................................................................14
2.2.4 Metadata Tracks ............................................................................................15
2.2.5 Framework Sets ............................................................................................16
2.2.6 Set Properties ................................................................................................16
2.3 Package Timecode and Metadata Edition .................................................................17
2.3.1 New Metadata Track .....................................................................................18
2.3.2 Remove Metadata Track ...............................................................................18
2.3.3 Add Metadata Segment .................................................................................18
2.3.4 Remove Metadata Segment ..........................................................................19
2.3.5 Replace Framework ......................................................................................19
2.3.6 Add Metadata ................................................................................................19
2.3.7 Edit Metadata ................................................................................................20
2.3.8 Remove Metadata .........................................................................................20
2.4 Partial Restore ...........................................................................................................21
2.5 DCP Creation .............................................................................................................22
2.6 IMP Creation ..............................................................................................................28
III
USER MANUAL OpenCube MXFTk® Front-End 2.6
Document
Version
Revision Date
Author
Change Description
2.6. A
10-Oct-2013
VPO
Update user manual to OpenCube
MXFTk® Front-End 2.6
Revision History
Preliminaries V
USER MANUAL OpenCube MXFTk® Front-End 2.6
1. Preliminaries
1.1 MXF File Format
MXF (standing for Material eXchange Format) is a file format aiming to improve data and
metadata exchange. The targeted objective is the interoperability between content
creation mainframes, work stations and peripherals.
This wrapper file format was designed to make use of current and forthcoming data
formats. Hence, it not only allows exchange of contents in MPEG, DV or else but also
improves interoperability between editing systems. In the meantime, it also permits
conveyance of metadata following standardized schemes.
1.2 OpenCube MXFTk® Front-End
Installation
1.2.1 Windows Platform
If you received OpenCube MXFTk® Front-End on a CD, insert it in your CD drive. The
installation should start automatically. If not, open an explorer window and look for the
executable “Setup.exe” and launch it. During the installation procedure, your antivirus
software may warn you about the execution of Windows scripts. You may safely ignore
these warnings.
1.2.2 Linux Platform
Unzip the file and create the destination directory '~/MXFTkFrontEnd'.
> unzip MXFTkFrontEnd-2.5.0.zip
> mkdir ~/MXFTkFrontEnd
Launch the script to install the « License Key Manager » software into the
'~/MXFTkFrontEnd' directory.
> OCPackage/Linux/KeyManager-2.5.0.sh --prefix=$HOME/MXFTkFrontEnd -exclude-subdir
Launch the script to install the « MXFTk® Front-End » software into the
'~/MXFTkFrontEnd' directory.
> OCPackage/Linux/MXFTkFrontEnd-2.5.0.sh --prefix=$HOME/MXFTkFrontEnd --
exclude-subdir
Set the MXF_HOME_FRONTEND variable and launch the « License Key Manager »
software.
> MXF_HOME_FRONTEND=~/MXFTkFrontEnd
~/MXFTkFrontEnd/bin/licensekeysmanager
Click on the « Load license file » button.
Select the file which is in the 'OCPackage/Licenses' directory.
Preliminaries 1
EVS Broadcast Equipment S.A.
Issue 2.6.A October 2013
Quit the « License Key Manager » software.
You can know execute the 'MXFTkFrontEnd' software.
> ~/MXFTkFrontEnd/bin/mxftkfrontend
1.2.3 Apple Platform
OpenCube MXFTk® Front-End comes as a self-extractible archive.
Double-click on OpenCube MXFTk® Front-End package to launch the installation.
The default installation path is in the “Applications” directory however you may
choose to install it elsewhere.
If you have not installed OpenCube MXFTk® Front-End in the default installation
path, you have to set an environment variable:
o MXF_HOME_FRONTEND which should contain the path to the root directory of
your OpenCube MXFTk® Front-End installation directory.
o (installation_directory/MxfTkFrontEnd.app/Contents/SharedSupport/MxfTk).
1.2.4 OpenCube MXFTk® Front-End Activation
OpenCube MXFTk® Front-End requires a valid license key to work. Temporary license
keys for evaluation purpose are available from EVS OpenCube’s website (http://www.evs-
opencube.com). After creating an account there, you will get access to a download area
where you will be able to retrieve a one-month license key file. If you purchased
OpenCube MXFTk® Front-End you should have received a permanent license key file.
To enable your software, you will need to install the OpenCube Key Manager also freely
available for download and load your license file in this application. After agreeing to the
license you will be ready to start working with OpenCube MXFTk® Front-End.
1.3 OpenCube MXFTk® Front-End
Overview
OpenCube MXFTk® Front-End is an application built on top of OpenCube MXFTk® C++
OEM SDK library for Linux, Mac OS X and Windows operating systems. It enables
wrapping of MXF files embedding your audiovisual material, MXF file unwrapping, partial
restore of MXF files and metadata update. OpenCube MXFTk® Front-End can read and
partial restore all normative files ranging from Op1a to Op3c as well as OpAtom
operational patterns. It can create MXF files following operational patterns Op1a to Op2b
and OpAtom. It also includes support of SONY eVTR, XDCam, Panasonic P2, Panasonic
AVC-LongG and Avid files. OpenCube MXFTk® Front-End was built to demonstrate the
main features of MXF and all of them can be automated using OpenCube MXFTk® C++
OEM SDK library.
2 Preliminaries
USER MANUAL OpenCube MXFTk® Front-End 2.6
Part
Description
1
Menu and dockable toolbar.
2
File History Overview. Displays the time of edition, the product used
to edit the file and also mentions the operational pattern.
3
Packages Overview. Displays the packages of the file.
4
Data tracks Overview. Displays the tracks of the selected package.
5
Metadata tracks Overview. Displays the metadata tracks of the
selected package.
6
Framework Sets Overview. Displays the metadata tree of the
selected metadata track.
7
Set Properties Overview. Displays the properties of the selected
metadata set.
1
2
3
6 4 5
7
Preliminaries 3
EVS Broadcast Equipment S.A.
Issue 2.6.A October 2013
1
2
3
5 4 6
7
8
9
10
11
12
13
2. OpenCube MXFTk® Front-End in
Practice
2.1 MXF File Creation
To create a new MXF file you simply need to click on New. This will open a new wizard
that will guide you through the different steps required to build a file.
2.1.1 Operational Pattern and Input Files Selection
4 OpenCube MXFTk® Front-End in Practice
USER MANUAL OpenCube MXFTk® Front-End 2.6
This page lets you select the operational pattern (Op) of the file and the media files you
want to embed. The drop-down box (1) is a list of operational patterns available for
creation. You will also find here some predefined manufacturers patterns that are heavily
used (SONY eVTR, XDCam IMX, XDCam DV, XDCam proxy and Panasonic P2/AVCLongG files). The choice of the operational pattern depends on what you want to do with
the MXF file:
Op1a: the most common operational pattern. It is used to embed media files in an
MXF file and play them all together simultaneously and in their entirety. These files
contain a single source package where the media files are stored and a single
material package representing the output of the file. Consequently, the number of
parallel and play-list packages is forced to 1 and cannot be changed.
OpZero: this is an Op1a file with a single meda track and structure constraints to
ensure play while record capability.
Op1b: these files contain at least two source packages and a single material package
referencing all the source packages. All the source packages are played
simultaneously. Consequently, the number of parallel packages cannot be lower than
2 and the number of play-list packages is forced to 1.
Op2a: these files contain at least two source packages and a single material package
referencing all the source packages. The source packages are played one after the
other. Consequently, the number of parallel packages is forced to 1 and the number
of play-list packages cannot be lower than 2.
Op2b: these files contain at least four source packages and a single material
package referencing all the source packages. This is a combination of Op1b and
Op2a where a set of source packages is played simultaneously and is then followed
by another set of source packages played simultaneously. Consequently, the number
of parallel and play-list packages cannot be lower than 2.
OpAtom: OpAtom files are MXF files embedding a single source and a single
material package. On top of this, the source package should only contain a single
media file. However, the material package is representing a combination of several
OpAtom files in order to build a complete editing. When you create OpAtom files you
should keep in mind that one MXF file will be created for each media file you provide
and the files should remain altogether to be played later on. Similarly to standard
operational patterns, it is possible to create OpAtom1a, OpAtom1b, OpAtom2a and
OpAtom2b files.
DCP (SMPTE): DCP files are OpAtom files compliant with the SMPTE429 standards
relative to DCI distribution package MXF files.
DCP (Interop): DCP files modified to be compliant with some manufacturer’s D-
Cinema servers.
eVTR: this will create an Op1a file following the exact properties of a SONY eVTR
file. You will need to provide one IMX sequence (30, 40 or 50 Mb/s) and one 8channel AES audio file.
XDCam IMX: this will create an Op1a file following the exact properties of a SONY
XDCam Optical IMX file. You will need to provide one IMX sequence (30, 40 or 50
Mb/s) and one 8-channel AES audio file.
XDCam DV: this will create an Op1a file following the exact properties of a SONY
XDCam Optical DV file. You will need to provide one DV IEC sequence and four 1channel AES file or four 1-channel WAV files.
XDCam Proxy: this will create an Op_pd_proxy (Professional Disc Proxy) file
following the exact properties of a SONY XDCAM MPEG4 proxy file. You will need to
provide one MPEG4 file and four A-law (embedded in WAV) files.
OpenCube MXFTk® Front-End in Practice 5
Loading...