This guide will provide step-by-step instructions for setting up Vantage and integrating it with Mediabeacon. Vantage will then process video transcoding requests from MediaBeacon. These instructions assume that Vantage and MediaBeacon are on separate servers. The integration requires the following:
- Windows with NTFS-based file system.
- An installation and working knowledge of Vantage 5.0 or higher.
- A Vantage license with the following options (at minimum):
- (1) Vantage Transcode
- (1) Vantage Analysis
- (1) Metadata Conversion
- An installation of MediaBeacon 6.0 or higher, or MediaBeacon 5.2.5 with Vantage functionality.
- MediaBeacon's Vantage style sheet (mediabeacon.xsl).
- MediaBeacon's Vantage metadata labels (MediaBeacon Metadata Labels.xml).
- MediaBeacon's Vantage workflows (keyframes.xml, metadata.xml, and texttracks.xml).
- MediaBeacon's sample transcoding workflows.
In general, these are the steps for activating the MediaBeacon/Vantage integration:
- Grant remote access to the MediaBeacon server from the Vantage Management Console.
- Ensure there's only one active local Vantage Store for the Vantage text tracks workflow.
- Add the MediaBeacon metadata stylesheet to Vantage.
- Add the MediaBeacon metadata labels to Vantage.
- Import the MediaBeacon keyframes, metadata, and text tracks workflows into Vantage.
- Add the required system properties on the MediaBeacon server to activate Vantage functionality.
- Connect to the Vantage server from the MediaBeacon server application.
Vantage Configuration: Granting Remote Access to MediaBeacon
Vantage requires remote access to the MediaBeacon asset repository to transcode video. This allows Vantage to work on video assets in place.
- On the MediaBeacon server, share out the asset directory and give the user running MediaBeacon read/write/execute privileges.
- On the Vantage server, open the Vantage Management Console.
- Go to "Settings & Options" and click the "Authorization" tab.
- Add a new entry with the static IP or hostname of the MediaBeacon server, along with credentials for the user running MediaBeacon.
- Restart the Vantage server for the new authorization to take effect.
Vantage Configuration: Default Local Store
Check to make sure that there is only one active local store (Default managed store) configured within Vantage Management Console. This is configured automatically when Vantage is installed and will be used for temp files in the text tracks workflow. The location of this store is typically:
<Vantage installation path>\Vantage\Store\
If there is more than one local store, set all of them to "Offline" except the default store.
Vantage Configuration: Adding the MediaBeacon Style Sheet
MediaBeacon requires a default style sheet to interface with Vantage, which assists with metadata stamping.
- Open the Vantage Management Console.
- Under "Workflow Design Items," choose "Style Sheets" and click "Add a new style sheet".
- Locate mediabeacon.xsl, open it, and give it a name and description. Save your changes.
Vantage Configuration: Adding the MediaBeacon Metadata Labels
MediaBeacon requires metadata labels to interface with Vantage, which assists with metadata stamping.
- Open the Vantage Management Console.
- Under "Workflow Design Items," choose "Metadata Labels" and click "Import".
- Locate MediaBeacon Metadata Labels.xml and import the file. The imported Vantage parameters will now be correctly stamped into the XMP of transcoded videos.
Vantage Configuration: Importing Default Workflows
MediaBeacon requires three default workflows to interface with Vantage. These workflows (keyframes, metadata, and texttracks) generate thumbnails for video assets, stamp metadata into transcoded proxies, and extract text from supported text tracks. The workflows can be imported or else created manually (see "Appendix: Manually Configuring Default MediaBeacon Workflows" at the end of this document).
- Open the Vantage Workflow Designer.
- Choose "File > Import Workflow…" and import the default MediaBeacon workflows (keyframes.xml, metadata.xml, and texttracks.xml).
- After the workflows have been imported, choose the metadata workflow, select its "Transform" action in the workflow design tab and click "Configure".
- Click "Next".
- Under the style sheet dropdown, choose the MediaBeacon style sheet added in Step 3.
- Click "Next" and then "Finish".
- Once the workflows have been imported and configured, they must be activated before they will process requests from MediaBeacon. Select each workflow and choose "Activate" from the contextual menu.
- The workflows will now process requests from MediaBeacon.
Vantage Configuration: Creating Additional Workflows
Workflow and transcoding requirements vary widely between organizations—building a complete set of workflows takes time and energy. This example covers the simplest case: receiving a file and creating a single transcoding.
- In the Vantage Workflow Designer, go to "File > Create New Workflow…"
- Enter a name for the workflow. For the description, enter the file extension of the desired output file. This is the extension Vantage will append to the transcoded file. Note: Workflows with names that include "texttracks", "keyframes", or "metadata" will not show up on the MediaBeacon server, as those names are reserved for MediaBeacon's default workflows.
- Workflows must begin with a "Receive" action to receive jobs from MediaBeacon. Create a "Receive" action in the "Workflow Design" tab.
- Right-click the "Receive" action to bring up its contextual menu and choose "Configure". Set the expected nickname to "Original".
- To transcode the received file, add a "Flip" action and attach it to the "Receive" action.
- Right-click the "Flip" action to bring up its contextual menu and choose "Configure".
- Enter the desired settings for the transcoding.
Some things to note:
- Input media file nickname should be "Original".
- Output media file nickname should be "Web".
- Output Location should be "Path." Click the green "..." and bind it to the "Output_File_Path" variable.
- Add a "Media Trim" action to allow MediaBeacon to adjust the in/out points for transcodings.
- Select the "Media Trim" action and check "Media to Keep".
- Click "Add New Item".
- Click the green "..." for "Media start time" and bind it to the "Clipping Start Time" variable.
- Click the green "..." for "Media end time" and bind it to the "Clipping End Time" variable.
- Click "Save".
- Right-click the workflow in the workflow list and choose "Activate". The workflow can now begin receiving jobs from MediaBeacon. If this workflow was created as part of the initial integration setup, proceed to the next section "MediaBeacon Configuration: System Properties." If the workflow was created after initial setup, proceed to step 10.
- On the MediaBeacon server, go to the "Admin" tab and click "Movie Profiles."
- Click "Fetch/Verify Workflows". This will connect to the Vantage server and fetch an updated list of active workflows available for use in MediaBeacon.
- The new workflow will now appear in the list. Configure its options, then click "Save."
- Restart the MediaBeacon server to make the workflow available in the MediaBeacon web interface.
MediaBeacon Configuration: System Properties
MediaBeacon's integration with Vantage requires two system properties on the MediaBeacon side. Set these in the following way:
- If MediaBeacon is running, stop the MediaBeacon service and shut down the server application.
- Open the MediaBeacon system properties file, located here:
# Windows Server 2008 C:\Users\<account running MB>\AppData\Local\MediaBeacon\mediabeacon.properties
# Windows Server 2003 C:\Documents and Settings\<account running MB>\Local Settings\Application Data\MediaBeacon\mediabeacon.properties
- Add the following lines to the system properties file:
mb.vantageEnabled=true #Not required for 7.x and on, as this is now enabled via your license. mb.vantageOutDir=<path to MediaBeacon assets>\\m-vantageOutputs mb.vantage.storage.server.locale=<UNC path to MBAssets> #Example: \\\\10.10.4.81\\Users\\Administrator\\MBAssets mb.vantage.preview.share.path=<Drive path to MBAssets, only in Pr3view app> #Example: Z:\\MBAssets\\
Note: The mb.vantageOutDir property specifies Vantage's temp directory and should be set appropriately for your system. Be sure to use two "\" characters as file path separators on Windows deployments.
- Save the properties file. MediaBeacon will now be able to connect to the Vantage server.
MediaBeacon Configuration: Connecting to the Vantage Server
Once the system properties have been entered, MediaBeacon is ready to connect to the Vantage server.
- Open the MediaBeacon server application without starting the server.
- From the "Admin" tab, click "Movie Profiles".
- Enter the IP and port for the Vantage server. Vantage's default port is 8676.
- Click "Fetch/Verify Workflows". This will connect to the Vantage server and fetch a list of active workflows available for use in MediaBeacon. Note: The keyframes, metadata, and texttracks workflows will not appear in the list, as they are run by default for every new video asset.
- Check "Pre-Transcode" for any workflows that should be run on ingest. Workflows that aren't pre-transcoded will still be available in the web interface as on-the-fly conversions.
- Check "Use for HTML 5 video" for any transcodings that should be used for in-browser playback.
- Click "Save".
- Start the MediaBeacon server. These transcodings will now be available in the web interface.
MediaBeacon: Monitoring Jobs
When jobs have been submitted to Vantage, administrators can monitor progress from two places. The Preview Queue is available in the web interface and functions the same way it normally does.
Additionally, administrators with console access can monitor jobs on the Vantage Workflow Designer under "Domain Job Status".