Integration
Accurate.Video allows for simple integration into your media workflows. This can be done in multiple different ways and this article will showcase a generic solution.
Generic overview
This solution implements an integration service which can serve launch templates on demand. The service will, when a launch template is requested, fetch data and generate a launch template which is then read by Accurate.Video.
1. Open Accurate.Video Validate
An action to open Accurate.Video Validate is initiated.
The launchTemplate query parameter describes the endpoint to the integration
with information about some item to open in Accurate.Video Validate.
2. GET launch template
When Accurate.Video Validate is launched, the url specified in the launchTemplate query parameter will be called from the browser.
A JSON response is expected.
3. Build launch template
The integration service uses the information from the launchTemplate url to build a launch templateslaunch template.
In its essence the launch template is very simple, containing the data to work on, configuration of the Accurate.Video Validate app and information about where to export the result.
With this, it is also possible to create specialized workflows that suits any particular needs. We'll discuss this further in Adaptable workflows section.
4. Return launch template
The finalized launch template is returned to Accurate.Video Validate, which in turn creates a session locally in the browser, ready to view and enrich.
5. Work in Validate
Work is done in Validate, e.g. performing QC, adjusting file metadata or placing ad breaks. What this work entails depends on the workflow and how the launch template has been defined.
6. POST data
The work in Accurate.Video Validate is finished and the data is exported to an endpoint configured in the launch template. This data could for example be fed back to the integration service or be passed on to a different service.
Adaptable workflows
A powerful feature of launch templates is that they allow highly adaptable workflows. With launch templates, it is possible to control what data is passed in, configures how Accurate.Video Validate should work with that data and what happens with the result once the work in Validate is finished.
For a subtitle workflow, the input can be limited to contain only data necessary for subtitle localization and QC. Accurate.Video Validate can be configured to use custom forms to validate, modify or add file metadata and use the general workspace to QC the subtitles. The output should point to an endpoint that expects this subtitle data.
For an audio workflow, the input can be video and audio files together with e.g. AI generated loudness detection markers. Accurate.Video Validate can be configured to use the audio workspace which has tools to help verify possible audio issues. The output could point to a pass/fail endpoint allowing an operator to approve or reject the asset based on what is found in Accurate.Video Validate.