Cerify integration

The Cerify plugin allows Vidispine to integrate with Cerify from Tektronix. The plugin allows video files to be analyzed by Cerify during their import. RAW_IMPORT (New in 4.0.), PLACEHOLDER_IMPORT (New in 4.0.3.), ESSENCE_VERSION (New in 4.0.3.) and AUTO_IMPORT (New in 4.2.8.) are supported.


  1. Configure Cerify. The minimum configuration required is the creation of a MediaLocation with a path that is shared between Cerify and Vidispine storage, and the creation of a Profile. The profile may be empty.

  2. Configure the plugin by creating a Cerify resource containing the Cerify settings, by making a POST request to API/resource/cerify containing:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <ResourceDocument xmlns="http://xml.vidispine.com/schema/vidispine">
          <name>Name of Media Location</name>

    The elements are:


    The URL of the Cerify web service.


    One or many media locations. If many media locations are configured, the storage method where the file is stored will determine which one to use.


    The name of the media location. A media location with this name must be configured in Cerify.


    The storage method that contains the files that should be analyzed by Cerify. Must be on a file system accessible by Cerify through the path configured in the corresponding media location.


    If set to true, jobs and media sets will be removed from Cerify after completion.

  3. Update the task definition document by inserting a Cerify step at the appropriate position by making a POST request to API/task-definition containing something similar to:

    <TaskDefinitionListDocument xmlns="http://xml.vidispine.com/schema/vidispine">
        <description>Executing Cerify job</description>

    Note: for ESSENCE_VERSION, the Cerify job step should run after step 400; for AUTO_IMPORT, the Cerify step should run after step 200.


The Cerify profile to use when analyzing a file is specified using the jobmetadata query parameter.

Import a file and let Cerify analyze it using the Cerify profile named mpeg2 PAL :

curl -X POST -u admin:admin --data-binary @test_file.mpg ''

(New in 4.2.8.) For AUTO_IMPORT job, the job metadata can be set in the AutoImportRuleDocument. For example:

<AutoImportRuleDocument xmlns="http://xml.vidispine.com/schema/vidispine">
      <value>Vidispine test profile</value>

When the file is being analyzed by Cerify there will be progress information available in the job. The metadata key is cerifyProgress and the value will be an integer between 0 and 100.

New in version 4.2.8.

Use the cerifyPriority job metadata field to set the Cerify job priority (LOW, MEDIUM, HIGH). For example:

curl -X POST -u admin:admin --data-binary @test_file.mpg ''


Upon completion the results from Cerify is added to the shape as bulky metadata. The following fields are available. Note that cerify_alerts might not always be present and its absence means that Cerify did not detect any problem with the file.

<URIListDocument xmlns="http://xml.vidispine.com/schema/vidispine">

The element cerify_alerts contains all alerts produced by Cerify. Example:

<field start="466@3082500:128557" end="466@3082500:128557">
      <entry key="alertFrame"></entry>
      <entry key="alertId">22015</entry>
      <entry key="details">In Main profile / Main level, the maximum permitted value of f_code[0][1] in a frame picture is 5. In the current picture it has been set to 7. Stream position: 0x7cf812 (dec. 8189970), bit 7 Bitstream context: [VSQ|PCX]</entry>
      <entry key="level">error</entry>
      <entry key="location">00:00:15;16 frame 467</entry>
      <entry key="title">Invalid f_code</entry>
      <entry key="trackId">-1</entry>
      <entry key="type">video</entry>
      <entry key="url"></entry>

cerify_streaminfo contains general information about the analyzed file, such as peak volume level, frame rate, etc.

See the following documents for for more complete examples of metadata documents produced by this plugin: