After successfully launching and connecting the Bitmovin service to your Vidispine instance as a Vidinet Resource, you must now find the Vidinet resource ID for your Bitmovin Transcoder in order to start using it from the Vidispine API:

 GET {my_vidispine_endpoint/API/resources/vidinet

Make a note of the resource ID for your Bitmovin Transcoding service, you will need it later in this guide. (You can also find resource ID displayed under Connected Vidinet Resources on your running Vidispine instance in the Vidinet Dashboard.)


Running a job with three encoding passes 

Vidispine is automatically configured with a set of transcode presets. In order to run 3 pass encodings using Bitmovin you need to create a custom transcode preset document encoding in Vidispine. 

Read more about transcode presets here.

Adding three pass encoding transcode preset document 

An example document using h264 codec and the setting of three encoding passes.

Usage: PUT {my_vidispine_endpoint}/API/shape-tag/mp4-3pass 


<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<TranscodePresetDocument xmlns="">

Execute import and transcode job 

POST {my_vidispine_endpoint}/API/import?uri={uri_to_s3_store_file}&resourceId={bitmovin resource ID}&tag=mp4-3pass&storageId={your-s3-storage}&createThumbnails=false

Execute encoding job on existing item 

Use the transcode endpoint on an already existing item by 

POST {my_vidispine_endpoint}/item/{item-id}/transcode?tag=mp4-3pass&resourceId={bitmovin resource ID}&storageId={s3 storage id}&createThumbnails=false 

For transcoding jobs body must contain a metadata document  


View job execution progress using job endpoint 

Job status and progress can be viewed using 

GET {my_vidispine_endpoint}/job/{job-id} 


Execute jobs using Vidinet Content Viewer 

Every Vidispine instance is shipped with Vidispine Content Viewer, it supports usage of all our media services including Bitmovin encoding, cost estimation and job execution.