Engine with Orchestrator 

 

 

Based on using it in Orchestrator 2.7.1 but it should work in later versions as well. Make sure that you are using the UUIDs for the workflow, input and output locations. For input and output it’s {uuid => location}

This action plug-in is used to interact with Emotion Engine API for audio processing.

Description

Saved Parameters Description

• Name: The name used to identify a saved EmotionOperation configured instance.
• Comments: Some comments about this saved EmotionOperation configured instance.
• Service URI: The URL of the server where the Emotion service is hosted.(Example: http://localhost:44544/jobs)
• API Operation: Operation to be performed. Currently supports Triggering a Job (Aynch), Submitting a Job through Payload (Asynch), Listing Workflows(Synch), Polling Job Status (Asynch).
• Source File: The file(only 1) on which the operation is to be performed. It uses a hash format. Example : {"sourceUUID" => "/tmp/source/first.wav"}. Please note that the source UUID must already be present in the Emotion system.
• Destination File: The file into which the output has to be stored. This uses a hash format.Example : {"destinationUUID" => "/tmp/source/first.wav"}. Please note that the destinationUUID UUID must already be present in the Emotion system.
• Workflow ID : The UUID of the workflow that describes the operation on the source file must be entered here.
• Job UUID : Optional field. If not assigned, the server would assign a unique id to every job.
• Inputs : Some workflows require extra inputs for its execution. That could be entered here. It again follows a hash format(Example given below)
• Outputs : Some workflows require extra outputs after its execution. That could be entered here. It again follows a hash format(Example given below)
• Polling Frequency: The frequency of polling for the asynchronous operations.

Inputs Description

The Mandatory inputs are service uri, source, workflow id. Some workflows doesnt require destination. So please set it up according to the workflow that you are triggering. For all the Asynchronous job submissions, after the job is submitted the process keeps polling for a status till it gets a valid stable status ("Success", "Error"). The polling continues for the "Queued" and "InProgress" return status.

Outputs Description

The output fields obtained are the Job UUID, Job Raw Response, State Description and the message received. In case of an exception, we have a error msg field which displays the error associated with it.

Operating Instructions

Note:

• The path for triggering job is http://host:port/jobs. We have added code to handle /jobs. So please enter just the IP(or host) and the port.
• Source, Destination , Inputs, Outputs are all entered as a hash. Please follow the same.
• *IMPORTANT* - The file path entered should follow different naming to not fail on Windows Machines.(Follow one of the below methods)
• 1. Change the Windows path to Unix Path.
  • "C:\\Users\Administrator\Documents\wav-files\audio-file.wav" Should be changed to
  • "C://Users/Administrator/Documents/wav-files/audio-file.wav"
• 2. Add extra "\" for every "\" present to escape it right.
  • "\\127.0.0.1\tfs\effengine\inputs\abc.mov" Should be changed to
  • "\\\\1.2.3.4\\tfs\\effengine\\inputs\\abc.mov"

 

Example:

service URI : http://localhost:44544/ workflow Id : {be8ce50d-62f9-4e9a-8a8f-9966d63804d1}

Source : {'{7621eb1b-bc75-45c5-9bf4-a90aabae1afb'=>'C:/Users/Administrator/Documents/wav-files/audio-sample.wav'}

Destination: {"{a09751ae-3ec1-4cef-80d7-0a06f89c84a4}" => "C:/Users/Administrator/Desktop/orchestraddtor.wav"}

Inputs : {"{a09751ae-3ec1-4cef-80d7-0a06f89c84a4}" => "C:/Users/Administrator/Desktop/i1.wav","{a09751ae-3ec1-4cef-80d7-0a06f89c84a4}" => "C:/Users/Administrator/Desktop/i2.wav"}