Describe the problem
Currently, if a scene has more than 10,000 frames in a take then job submissions will fail because Deadline Cloud does not allow for a job with more than 10,000 frames.
Proposed Solution
This would require more thought and design because its not supported by Deadline Cloud right now.
A workaround could be that the submitter automatically submits multiple jobs divided with max 10,000 tasks per job.
Example Use Cases
Any scene with more than 10,000 frames.
Current Workaround
To unblock, customers would have to manually change the frame range and re-submit the same job multiple times to render all the frames. For example, say a scene file has 25,000 frames.
Then, customers would have to do the following:
- First job, same scene with Override frame range: 0-10000
- Second job, same scene with Override frame range: 10001-20000.
- Third job, same scene with Override frame range: 20001-25000
The second and third jobs can be submitted within the monitor as well
Environment (optional)
This affects all environments.
Describe the problem
Currently, if a scene has more than 10,000 frames in a take then job submissions will fail because Deadline Cloud does not allow for a job with more than 10,000 frames.
Proposed Solution
This would require more thought and design because its not supported by Deadline Cloud right now.
A workaround could be that the submitter automatically submits multiple jobs divided with max 10,000 tasks per job.
Example Use Cases
Any scene with more than 10,000 frames.
Current Workaround
To unblock, customers would have to manually change the frame range and re-submit the same job multiple times to render all the frames. For example, say a scene file has 25,000 frames.
Then, customers would have to do the following:
The second and third jobs can be submitted within the monitor as well
Environment (optional)
This affects all environments.