-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for frame chunking at the application level #104
Comments
How should I create a single layer to run only one task for an entire frame range - say for example I want the last layer of my job to run one process that consumes all the frames rendered in the previous layer to:
I guess I can:
Is that the best approach for now? Thanks |
Hi @donalm. |
I just started testing again with CueSubmit - my wee module for submitting via Outlines has suffered from bit rot but sure I'll get that running again in the next day or two. Thanks @gregdenton - we're still at a fairly early/loose stage of testing so I'm not too stressed about a few rough edges at this stage. |
Might be some overlap here with #83 |
These tokens exist now, added in #597 |
By default we only have the #IFRAME# replacement token, which limits our ability to do frame chunking in the application (executing a single command with a frame range, so we only incur the application startup cost once).
It would be nice to have a start and end frame token exposed by default in pyoutline making this functionality at least work for Maya and Nuke.
The text was updated successfully, but these errors were encountered: