Automated VFX pulls anyone? Ci Workflow is an app that brings EDL-triggered workflow automation to your browser. In this article you will learn how to configure workflows by defining input and output file specs and designating output recipients. Then use an EDL to kick off the workflow and tell Ci exactly which clips to pull. Here's how you can do that:
Configuring Workflows
To get started, open a workspace and select the Workflows icon in the navigation menu:
Figure 1: Opening Workflow
Your Workflow Dashboard will open in a new tab showing a list of configured Workflows. To search for Workflows, type the name in the Jump to Workflow search box. To create a new workflow, select + New Workflow:
Figure 2: Workflow Dashboard
First, create a Workflow name and from the drop-down menu select the target workspace where your source files are located. Please note that only .MXF files are supported in Workflow.
Please note that if the .MXF file is archived than we auto standard restore it but we do not archive it again. We assume there are storage management policies in place. For more information on storage policies, please visit our help desk article Storage Management Policies.
Once name is created and workspace are selected click Next:
Figure 3: Configure Workflow (General)
In the EDL Event Markers section, open the drop-down menu and select Red. This controls which marker color will contain the event name. Once this is selected, click Next to set the Output Profile:
Figure 4: Configure Workflow (Input Profile)
Select the Output Root Folder location by clicking the drop-down menu and select the icon to open the workspace folder tree:
Figure 5: Selecting Output Root Folder
Now set the Default Handle Length. After clicking the drop-down menu, the available options are 0 frames, 8 frames, or 16 frames:
Figure 6: Setting default Handle Length
Figure 7: Handle length options
For start frame, we set the default to 1001. To change the start frame, select the frame number field and type in the new start frame (see figure 6). Click Next for the final configuration step.
The EDL Uploaders section gives you the option to invite workspace members to submit EDL jobs to this workflow. Invited members will not have access to the configuration settings. To define EDL uploaders, enter their email address and select Add. Invited members will receive an email notification.
The Recipients option allows you to notify specific workspace members that an EDL job is completed. Alternatively, added recipients can also receive a MediaBox containing the completed EDL job + additional files such as references and a line-up sheet. Click the drop-down menu next to Add to specify if the recipient will receive a MediaBox or notification. Click Activate to complete configuration:
Figure 8: Adding Uploaders and Recipients
Create a New Job
The user will be brought back to the Workflow Dashboard with the newly created workflow displaying at the top of the list. To start a new job, select the new workflow or click the icon on the right and select View:
Figure 9: Creating a new job
After opening the Workflow, click + New Job in the upper-right corner to create a new EDL Job:
Figure 10: EDL Job page
Drag-and-drop and EDL file or click the plus icon to select a file. Please note that EDL files must be uploaded with Aspera. If you do not have Aspera, please click the following link to have it installed: https://downloads.asperasoft.com/connect2/. For more information on uploading with Aspera, please visit our help desk article Aspera Upload.
Once the file is selected, confirm the handle length (see figure 12). By default, the configured handle length settings of the workflow will be displayed. After this step is completed click Next:
Figure 11: New job EDL Selection
Figure 12: New job handle length
For the final step in creating a new job, the user can upload additional files such as references or a line-up sheet. Once your files are uploaded, select Submit and the job will begin to process (see figure 14). Processing times vary but are faster than the industry standard of ~12 hours:
Figure 13: Uploading additional files
Here is a list of statuses that may appear as the new job is in progress:
— In Progress: EDL pulls are processing and will appear in output root folder when complete;
— Complete: EDL pulls are successful;
— Partially Successful: Only part of the EDL pulls were completed. We'll send you a MediaBox containing these;
— Failed: Processing failed. We will notify the job creator and Ci customer success will be in contact with you.
Figure 14: New job in progress
Once the job has completed processing the status will display Complete. The files will appear in a folder within the specified output folder with the creation date as the title (see figure 15). As you drill down into the folder structure you will reach the DPX files along with the reference file and EDL (see figure 16). The DPX folder will contain the EDL pulls (see figure 17):
Figure 15: Completed Pull Request
Figure 16: DPX, Reference, and EDL folders
Figure 17: EDL Pulls
When job has completed defined workspace members will be notified. Recipients will receive a notification or a MediaBox containing these files.
For any additional questions, please reach out to the Ci Customer Success Team by submitting a request here in the Help Center.