Audio Processing Priority

SPE has a simple built-in system of task prioritization, allowing for flexible management of the processing queue, which is especially useful in mass audio processing.

For example, if there is a long queue of files waiting to be processed, and one needs to urgently process another batch of files, these files can be sent for processing using a higher priority. They will be processed as soon as possible, without waiting in the queue.
Similarly, if there is a batch of "not so important" files for processing, these can be sent for processing using a lower priority. They will be processed later, after the higher-priority tasks in the queue have been completed.

To use task prioritization, you need to have:

• Task priorities enabled in the SPE configuration file (enabled by default, see the server.task_priorities_enable option) and a default priority value set.
• The prioritize role enabled for the SPE user creating the processing task.

If prioritization is enabled and a processing task is started by a user without the "prioritize" role, the task is started with the default priority.

Task priority is defined by a number from 0 (highest priority) to 99 (lowest priority) and can be set using the X-Priority HTTP header when starting the asynchronous task. The PendingInfoResult response contains information about task priority.
Priority can be set only when starting the task; it is not possible to modify it afterward.

For additional information and examples, see the Task prioritization section in the REST API documentation.