The MXFserver plugin allows Vidispine to integrate with MXFserver. The plugin allows collections to be created in Vidispine, representing business units, sections, modules, episodes and projects (here called entities.) Items added to a project collection will automatically be added to the MXFserver project.
The plugin can also extend LDAP so that business units and sections are created for imported users.
A JDBC resource should be configured in your application
server for connecting to the MXFserver MySQL database. The
element can be used to specify the JNDI name of the JDBC resource (default=
jdbc/mxfserver). Typical connection pool settings are:
Configure the plugin by creating a MXFserver resource containing the MXFserver settings, by making a
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <ResourceDocument xmlns="http://xml.vidispine.com/schema/vidispine"> <mxfserver> <url>http://192.168.38.200:11000/mxfserver/</url> <workspaceUrl>file:///mnt/mxfserver/</workspaceUrl> <mxfServerWorkspacePath>C:\storage\Workspaces\</mxfServerWorkspacePath> <mxfServerUserId>1</mxfServerUserId> <mxfServerPathToStorage>C:\storage\Vidispine\</mxfServerPathToStorage> <storageId>VX-1</storageId> <db-host>192.168.38.200</db-host> <db-port>3307</db-port> <db-username>root</db-username> <db-password>Mastermeta</db-password> <atomShapes>atom</atomShapes> <importShapes>hd,original</importShapes> </mxfserver> </ResourceDocument>
In the example above the (first) shape with the
hdtag should be imported, if one exists, and the
originalshape should be used otherwise.
The elements are:
The path to the workspaces directory used by MXFserver.
The Vidispine MXFserver user id.
The path to the Vidispine storage
storageIdas seen by MXFserver.
The storage that contains the files that should be imported into MXFserver. Must be on the same file system as the MXFserver workspaces directory.
Should contain the tags of the shapes that contain OP-Atoms, and for which QuickTime reference files will be created.
Contains the shapes that should be considered for import into a MXFserver project, ordered by priority.
Enable the plugin by setting the following configuration properties:
Property Value Note
- If enabled then MXFserver functions will be created with the same names as the groups found in the directory.
To enable automatic import of new media added to projects, the MXFserver configuration file
Mxfserver.inineeds to be updated with:
[API_OPTIONS] notifyNewFilesHTTPLocation=http://[Vidispine server address]/MxfServerAPI/import
MXFserver entities are in Vidispine simply created as collections. A number of additional parameters are required, depending on the type of entity to create, as shown below. See Collections for more on how to manage collections.
Note that a collection will automatically be added as a child to the parent collection.
The query parameters are:
- The name of the collection and MXFserver entity.
- The type of MXFserver entity. Either
- The id of the parent collection/entity.
- The type of MXFserver project.
- The project template to extend.
Creating the MXFserver project hierarchy.
With a FCP (
projectType=2) project based on the FCP7 template (
Note that projects can be created at any level in the hierarchy. However, the MXFserver client only allows projects to be created if an episode has been selected. An episode must also be selected before the details of a project can be edited and saved, which if done would cause Vidispine to be out of sync with MXFserver (it’s one way sync from VS to MXFserver only.)