Add Profile
Last updated
Last updated
The "Add Profile" Button opens the “Add new profile” dialog to define the following parameters:
Selection box for defining the stream type to be used in the profile. Selecting a type filters the available streams by the type.
PRESTREAM is a separate trigger that is only available within IO. If a stream is linked to this trigger, it can be defined within a profile. For example, if a prestream is defined in addition to an autoimport trigger within a profile, the corresponding prestream is executed each time an autoimport trigger is triggered. The prestream defines whether the actual stream is executed or not. If the prestream is successful, the actual stream is executed and a job appears in the dashboard. If the prestream fails, the actual stream is not executed. In this case it is possible to delete the failed prestream job (Job delete action node) or to display it (Job status update action).
If several jobs are started whose profile contains a prestream, all prestreams are executed one by one. The number of possible prestreams is not infinite and prestreams should be used with care. They are designed to take on easy tasks. Example: If you only want to process video files in auto import, it is possible to filter all video files via a prestream and only create a job for these files. A prestream should not contain asynchronous tasks and is designed to be processed within 60 seconds.
Drop-down menu to select the desired stream. All previously created streams under the menu item "Streams" are displayed here and can be selected.
Dropdown menu to select the desired priority for the profile. By default, the priority is set to 5 (middle) and can be set in the range of 1 to 10, with 1 being the highest and 10 being the lowest priority. The priority defines the rank of the job in relation to the render nodes stored in the profile. Example: If there are two profiles and all existing render nodes are entered in both profiles, all jobs that were created with a profile that has a higher priority are processed preferentially.
Dropdown menu to select the desired metadata set. All previously created sets under the menu item "Metadata" are displayed here and can be selected.
Drop-down menu to select the desired group (s). All previously created groups under the menu item "User" are displayed here and can be selected. If one or more groups are selected, the profile is available only to this group.
Due to the fact that a profile is visible in all groups if it is not assigned to any group, it is possible to hide a profile from the user. This allows profiles that are assigned to a job as job profiles via the Job Create Job Action to be hidden.
Free text field for defining the name of the render node (s) which should process the jobs created with this profile. There are different ways to define this render nodes:
Processed by the local workstation: To automatically assign every job to the user that has created that job, it is possible to use the {user.name}. This wildcard is always automatically replaced by the username and thus transferred from the server to the workstation via the client connector.
Processed by a dedicated user/render node: To assign a job to a specific user or a dedicated render node, regardless of whether or not he has created the job, the name of the user can be entered here. Example: “User1” or “rendernode 1”
Processed by one user of a group: To assign a job to multiple users or render nodes, regardless of whether or not he has created the job, the names of all users can be entered here. The next available user will automatically start to process the job. The Usernames need to be added separated by a comma without any blank space (Example1). Alternatively it is is possible to assign the jobs to a group of users that start with dedicated letters (Example2) Example1: User1,User2,User3,rendernode1,rendernode2 Example2: User* or render*
Processed by any available user: Leave this filed blank
Works in the same way as the render node assignment, but for pre Streams.