| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Engines are API connecting the OOONA Manager to providers of automatic speed recognition (ASR) and machine translation (MT) to apply those processes to files or Toolkit projects.
These are available in the system as resources that are assigned to tasks, like any other resource.
| Info |
|---|
Using engines requires an established agreement with the provider, so they are not available by default. Please reach out to our team to sign the required documentation. |
Configuration
Setting up languages
In order for the correct language combination to be sent to the engine, first it’s necessary to connect the languages within the Manager with the list of languages within the Toolkit.
This can be done from Administrator > Tables > Language tables.
Using “Reconnect to Toolkit languages” (1), the system will try to populate the “Connected Toolkit language” column based on that language’s Toolkit settings.
If no settings are present, the system will try to map the languages in the system to languages in the Toolkit with the same name.
If no language is found, or the language found isn’t the one needed, it can be manually set from the Toolkit settings (2). The language used in the “Language” field will be applied to the “Connected Toolkit language” column (3) once saved.
Setting up the engines
Engines are available in the system as resources and can be created from Manager > Rolodex tables > Resources.
Click on the Engines tab
Click on “Add new engine”
Populate the name, which will be displayed when assigning this resource to a task.
Select the engine type. This list will include all available engines, and the type (ASR or MT) in brackets next to the name.
Optional: select if the engine should start running immediately once its task is ready to start.
Select which file types should be used by the engine.
| Info |
|---|
ASR engines require media files and currently do not support MPD files, only MP4. MT engines do not use files. Instead, they will use the project of the previous task in the flow. |
Save to add the engine to the list of resources.
After the resource has been created, click on “Load Toolkit languages” to connect it to the languages available in the system, as configured in the Setting up languages step.
| Tip |
|---|
If the language configurations at the system level are changed after performing this step, please make sure to repeat it to ensure the engine’s language pairs are up-to-date. |
Assign the resource to the relevant languages, tasks and order types, like any other resource.
| Note |
|---|
When assigning languages to an engine, please be sure to use Language pairs. This will ensure the shown language combinations are supported by the engine. |
| Info |
|---|
The list of languages available to an engine is generated when checking the connected Toolkit languages in the system. Only languages with a supported connected Toolkit language will be available in the selection and unsupported language pairs will not be added. |
Using engines in orders
Engines behave like normal resources and can be assigned to tasks based on their skill set (languages, tasks and order types).
Once assigned, the “Completed” icon will change to indicate the current status of the process:
Once the task is done processing, it will automatically be marked as done and the task will be completed:
| Info |
|---|
Please note that the processing time varies by engine. |
Checking engine costs
After an engine has processed a task, the cost information is added to the Task info page (1) of the task the engine was assigned to, in the “Task cost information” section (2):
A more detailed breakdown can be seen from the magnifying glass (
) next to “Total amount due”:
| Info |
|---|
The cost of engines is always logged in dollars, which are then converted into your system’s currency, if different. |
The same information is also available from the same pages as other order costs, such as the Cost tab of the Order info page.
