Post processing
Last updated
Last updated
Post processing settings can be accessed from the Settings > Library > Automations > Post processing (tab) menu.
When a post process automation task is activated, it will run automatically on each upload. If not activated, the task can be manually triggered for certain uploads via the Upload API using the postprocess parameter (e.g., postprocess=remove-background).
Once a post process is selected, the user is requested to set the following parameters:
Mode
Sets if the post processing is SYNC (synchronous, -during the upload- preventing the asset to actually be stored while it's analysed) or ASYNC (asynchronous, meaning that the analysis job will be queued, allowing for the asset to immediately be available in the library)
Run on every upload
When enabled, the post process will apply to every upload, if activated and triggers don't prevent it. When disabled, it allows you to prepare, test parameters, and temporarily put on hold the post-process while not losing the configuration.
Trigger rules
Defines conditions under which the post processing will be triggered. If "no trigger rules" is selected, the post processing will trigger with every upload, if activated and enabled.
Validation rules (optional)
Some post-process running in sync mode allow to determine attributes for a file that can be used to decide whether or not to take a predetermined validation action at upload (eg. Notice or Refuse the upload)
When setting up a post-process, trigger rules can be specified. These rules specify conditions that must be met to activate the related task. If left empty, the task will be run on each upload.
The following variables may be used to construct rules:
Image/Video width (px)
images / videos
Horizontal image dimensions / frame size (in pixels).
Image width (px) is smaller than 500
Image/Video height (px)
images / videos
Vertical image dimensions / frame size (in pixels).
Video height (px) is larger or equal than 200
Image format
images
The file type of the image.
Image format contains PNG, JPEG
File size (B)
images / videos
The size of the asset in bytes.
File size (B) is larger than 5000000
Video bitrate (bps)
videos
The video bitrate in bits per second.
Video bitrate (bps) is smaller than 1500000
Video duration (s)
videos
The video duration in seconds.
Video duration (s) is larger than 60
Upload folder path
images / videos
The location in which the asset is getting uploaded.
Upload folder path starts with '/users'
As mentioned, the synchronous tasks provide a mechanism to validate uploads using validation rules. Possible actions when conditions have been met are:
Refuse - The upload is rejected.
Notice - A notice is issued, added to the file information and returned in the API response.
Setting up many synchronous tasks might significantly slow down the upload process.
Count faces
Number of faces
Number of faces is smaller than 1 => Refuse
Not Safe For Work
NSFW
Drawing
Hentai
Neutral
Porn
NSFW is larger than 0.70 => Refuse
Recognize number plate
Number of characters in number plate
Number plate content
Number plate content does not start with 'C' => Notice
Recognize text (OCR)
Text contains
Text contains 'Copyright' => Refuse
Validate image properties
Image/Video width (px)
Image/Video height (px)
Image format
File size (B)
Upload folder path
Image width (px) is smaller than 500 => Notice
Validate video properties
Image/Video width (px)
Image/Video height (px)
File size (B)
Video bitrate (bps)
Video duration (s)
Upload folder path
Video bitrate (bps) is smaller than 800000 => Refuse
When the activation is provided and your account has enough Visual AI credits to run it, the post-process will be applied to all uploads, if the "Run on every upload" option is set to "Enabled".
Please note that when marked "Unavailable", a post-process will not run and first it needs to be activated. That happens with a request to our , and in the meantime, triggering will be prevented regardless of the configuration of the post-process.
Refer to the Upload post-processes on the for a list of available post-processes.
