Skip to content
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

Closed
gregdenton opened this issue Jan 15, 2019 · 5 comments
Closed

Allow for frame chunking at the application level #104

gregdenton opened this issue Jan 15, 2019 · 5 comments
Labels
enhancement Improvement to an existing feature

Comments

@gregdenton
Copy link
Collaborator

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.

@gregdenton gregdenton added the enhancement Improvement to an existing feature label Jan 15, 2019
@gregdenton gregdenton added this to the OSS Launch CBBs milestone Jan 15, 2019
@gregdenton gregdenton added this to To do in OpenCue OSS Launch via automation Jan 15, 2019
@bcipriano bcipriano removed this from To do in OpenCue OSS Launch Jan 17, 2019
@bcipriano bcipriano removed this from the OSS Launch CBBs milestone Feb 8, 2019
@donalm
Copy link
Contributor

donalm commented Jun 27, 2019

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:

  • generate a movie from rendered frames or
  • publish frames or
  • cat and bzip the frames for transfer

I guess I can:

  • set the 'frame spec' to 1
  • assign the 'postprocess' service to the layer
  • hardcode the real frame range into the command before I hand it off to OpenCue

Is that the best approach for now?

Thanks

@gregdenton
Copy link
Collaborator Author

Hi @donalm.
Yes, the approach you describe is the current best practice. Are you using outlines for the job submission? It is a little more manageable baking the command with frame range in the outline file, but as you point out still not ideal.

@donalm
Copy link
Contributor

donalm commented Jun 27, 2019

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.

@donalm
Copy link
Contributor

donalm commented Jul 3, 2019

Might be some overlap here with #83

@bcipriano
Copy link
Collaborator

These tokens exist now, added in #597

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants