Media Service User Guide
Version 2.3 | Published February 19, 2018 ©
Reprocessing Asset Proxy Media
New versions of Media Service may introduce new types of proxy media that clients can use for previewing. All newly ingested media will automatically include the new proxy types. But in order to provide this content for preexisting assets, they need to be reprocessed.
Reprocessing can also be used if processing previously failed for an asset due to a problem that has since been fixed (such as disk space or service downtime).
Note: The API provided in version 2.3 is using temporary link relations, and may change in future versions.
Reprocessing individual assets
Some clients may provide means to trigger asset reprocessing in their search or browse interfaces, which should be documented in their respective user guides. This is the recommended way to perform this operation.
It is possible to trigger reprocessing using any HTTP client. Each asset entry contains a link with relation http://schema.vizrt.com/2017/MediaService/Temporary/Reprocess as well as a short exlanation of how to use it.
Reprocessing all assets
The Media Service status monitor can be used to trigger reprocessing of all assets as a bulk operation. See Media Service status check for details.
It is possible to trigger reprocessing using any HTTP client. The service document contains a link inside the Asset collection with relation http://schema.vizrt.com/2017/MediaService/Temporary/ReprocessAll as well as a short exlanation of how to use it..
WARNING! Reprocessing all assets will take a considerable amount of time and resources, and should preferably be performed during scheduled maintenance.
Limitations
It is not possible to trigger reprocessing of an asset that is currently being ingested using Channel Recorder. After recording stops, it may be reprocessed as normal.