Pre-Render and Post-Render Tasks

Product Function Explanation: Pre-Render and Post-Render Tasks

Pre-render and post-render tasks are independent tasks executed before and after the main rendering task, respectively. Utilizing this pre- and post-task workflow achieves the following objectives and effects:

1.Pre-Render Tasks: Reduce the time required for processing related files and other cumbersome scene preparation steps during actual rendering, significantly improving rendering efficiency. Examples include generating XGen caches in Maya, creating DCC caches in UE, or modifying scene render settings. For rendering tasks heavily dependent on pre-processing, this effectively lowers the error rate.

2.Post-Render Tasks: Simplify the post-production pipeline and reduce certain post-processing workloads, such as sequence compositing or sequence denoising. This enhances team productivity and further improves delivery efficiency and flexibility.

1. Web Client Operation Guide

(1) Pre/Post Task Setup Step Becomes Visible After Normal Job Analysis

The submission form on the web client has added a third step: [Pre/Post Task Setup]. This step appears after a job is successfully analyzed.

(2) Setting Up Pre/Post Tasks

(Content related to the setup interface would go here.)

(3) Viewing Pre/Post Tasks

Each pre- or post-render task is a separate job, residing under the same parent job as the main rendering job.

● P Number: Indicates the execution order among tasks; a smaller number means earlier execution.

● Task Type: Specifies whether it's a pre-render or post-render task.

● Chargeable/Non-chargeable: Indicates if the task incurs charges. The billing method for pre/post tasks is consistent with regular rendering jobs.

(A visual representation of the task list would typically be here.)

2. Business Logic for Pre/Post Task Operations:

1. Pre- and post-render tasks do not support configuring priority frames, tile rendering, or single-machine multi-frame rendering.

2. Pre-Render Tasks only support: Start, Stop, Resubmit, and Delete operations.

3. Post-Render Tasks only support: Start, Stop, Resubmit, Delete, and Download operations.

4. When cloning a rendering job, you can choose to submit any incomplete pre-render tasks from the original job along with all post-render tasks.

5. Batch operations (Start, Stop, Resubmit, Delete) are only supported for tasks of the same type (Pre-render / Render / Post-render).