To start processing, send the process
action to HPE Media Server.
HPE Media Server adds your request to the process
action queue. When the request reaches the top of the queue and a thread is available, HPE Media Server starts to ingest the media and perform the configured tasks.
To start processing
Send the process
action to HPE Media Server. Set the following parameters:
Source
|
(Set either The media source to process.
|
SourceData
|
(Set either The media file to process (as binary data). For information about sending data to Media Server, see Send Actions to HPE Media Server. |
Persist
|
Specifies whether the action restarts in the event that processing stops for any reason. For example, if you are processing video from an RTSP camera which becomes unreachable and persist=true , HPE Media Server will wait for the stream to become available again. Persistent actions only stop when you stop them using the QueueInfo action with QueueAction=stop , or when HPE Media Server finishes processing the media. |
Config
|
(Optional) A base-64 encoded configuration that defines the tasks to run. This overrides the HPE Media Server configuration file. |
ConfigName
|
(Optional) The name of a configuration file that defines the tasks to run. This overrides the HPE Media Server configuration file. The file must be stored in the directory specified by the ConfigDirectory parameter in the [Paths] section of the configuration file. |
ConfigPath
|
(Optional) The path of a configuration file that defines the tasks to run. This overrides the HPE Media Server configuration file. Specify an absolute path or a path relative to the HPE Media Server executable file. |
For example,
http://localhost:14000/action=Process&Source=.\video\broadcast.mpeg &ConfigName=broadcast
This action is asynchronous, so HPE Media Server returns a token for the request. You can use the QueueInfo
action, with QueueName=Process
to retrieve more information about the request.
|