Process

Starts ingesting and processing the specified media.

Type: asynchronous

Parameter Description Required
AdditionalData Additional files to upload. If your session configuration requires a file, such as a Lua script or XSL transform, that is not available on the Media Server file system, you can upload it with the process action. Files must be uploaded as multipart/form-data. For more information about sending data to Media Server, refer to the Media Server Administration Guide. No
AdditionalDataLabels A comma-separated list of labels to identify the files uploaded using the AdditionalData parameter. Specify a label for each file that you upload. You can use these labels in your session configuration instead of file paths. No
Config A configuration to use (base64 encoded, unless you upload it as multipart form data). Set one of Config, ConfigName, and ConfigPath
ConfigName The name of a configuration file to use.
ConfigPath The path of a configuration file to use.
Persist Specifies whether the action restarts in the event that processing stops for any reason. No
Source The media source to process. Set either Source or SourceData
SourceData The media file to process. Set either Source or SourceData
Synchronous Specifies whether to run the action synchronously. No

Example

The following example starts processing a file using a configuration named myconfig that exists in the ConfigDirectory on the Media Server machine.

/action=Process
             &ConfigName=myconfig
             &Source=/videoarchive/broadcast.mpeg

The following example demonstrates how to upload a configuration, source file, and an additional XSL file using the command-line tool cURL.

curl http://localhost:14000/action=Process
                            -F Config=@ocr.cfg
                            -F SourceData=@document.pdf
                            -F AdditionalData=@transform.xsl
                            -F AdditionalDataLabels=file1

Response

This action is asynchronous, so Media Server always returns success accompanied by a token. You can use this token with the QueueInfo action to retrieve the status of your request.


_FT_HTML5_bannerTitle.htm