Generative Productions allow more dynamic processing of assets– especially for use cases involving Generative AI, where assets require flexible inputs and outputs. When combined with Cloud Automation in your Workflows, Generative Workflows allow you to fine-tune and perfect how assets flow to and from your AI tool of choice.
➕ Cloud Automation: Generative Workflows are designed to complement Cloud Automation, which requires the Workflow & Style Guide V2 Engine. If you are interested in using them in your studio, reach out to your CSM to chat.
Getting Started
Generative Productions work through Cloud Automation to execute powerful Generative AI functions. The first step in applying flexible AI Automation to your studio's assets is to create a Generative Workflow.
Generative Workflows
To get started, head to Studio Settings → Workflows, then select Add Workflow → then, select Generative as the Workflow Type.
Within the Workflow Builder, you will be able to add steps in the same way as Workflows of the standard photo and video types.
⚠️ Important: Digital Processing and Derived Workflows are not supported in Generative Workflows at this time.
Assets of different types will be grouped together for the steps that support grouping assets, and will be handled separately for post-production.
Groups Assets
Workflow Step | Notes |
Capture | Photo and video files are mapped to positions based on the photography position's Media Type setting. |
Final Selection | Supports photo and video assets. Warning shown if the user drags a video into a photo position. |
Photo Review | Supports both media types. Warning shown if user drags a video into a photo position. |
Cloud Automation | Available sub-functions are enabled/disabled based on the media type. |
Asset Delivery | Delivers both photo and video assets. If seperate delivery locations are required for the different media types, this can be configured in the Style Guide's Delivery Matrix. |
Post-Production
Workflow Step | Notes |
Internal Post | Supports Photo (via Hue) and Video (via Luma) in separate steps. Requires Video add-on for Luma. Each step is configured for one media type only. |
Internal Post QC | Validates output from the preceding Internal Post step. Can view assets from the other media type as a reference. |
External Post | Supports photo and video in separate steps. Each step is configured for one media type only. |
External Post QC | Validates output from the preceding External Post step. Can view assets from the other media type as reference. |
Post Review | Review outputs and support rejections from the most recent Post Production step. Display option allows the user to show all assets (from both media types). Assets from a bypassed post step will auto-approve if rejected and resubmitted. |
When adding a Post-Production step to the Workflow, an additional configuration option will appear in the right-hand menu called 'Media Type.' For each step, the Media Type must be explicitly defined.
As an example, in a standard Generative Workflow where both image and video assets are moving through production, if both internal and external post-production are necessary, there would need to be 4 total post-processing steps.
Workflow Step | Media Type |
Internal Post L1 | Photo |
Internal Post L2 | Video |
External Post L1 | Photo |
External Post L2 | Video |
📝 Note: When a Post step is configured for one media type (e.g., Photo), assets in positions of the other type automatically bypass that step. No manual configuration is needed per asset.
Post-Production QC
When a QC step is added to the Workflow, it corresponds to the last Workflow Step preceding it.
This means if both internal and external post-production are necessary, and QC is needed for each, there would need to be 8 total post-processing steps.
Workflow Step | Media Type |
Internal Post L1 | Photo |
Internal Post QC L1 | ↑ |
Internal Post L2 | Video |
Internal Post QC L2 | ↑ |
External Post L1 | Photo |
External Post QC L1 | ↑ |
External Post L2 | Video |
External Post QC L2 | ↑ |
⚠️ Important: Photo and Video post-production steps run sequentially in order (one at a time).
Internal Post Handling
When an Internal Post-Production step is specified with the Media Type Photo, all related assets will be sent to Hue for post-processing work.
When an Internal Post-Production step is specified with the Media Type Video, all related assets will be sent to Luma for post-processing work.
➕ Add-On: Using the Luma App requires the Cloud Video add-on package to be enabled. If this has not been enabled for your studio, Internal Post-Processing will not be possible for the video Media Type.
Next Steps
Once your Generative Workflow has been created, you can move on to creating a new Generative Production Type and assigning it to a Style Guide to set Generative properties only available when connected to a Generative Workflow. Learn more at the link below.