-
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
Add #OFRAME# (outframe) to DispatchSupportService to support chunks #597
Conversation
|
@@ -389,6 +389,7 @@ public RunFrame prepareRqdRunFrame(VirtualProc proc, DispatchFrame frame) { | |||
frame.command | |||
.replaceAll("#ZFRAME#", zFrameNumber) | |||
.replaceAll("#IFRAME#", String.valueOf(frameNumber)) | |||
.replaceAll("#OFRAME#", String.valueOf(frameNumber+frame.chunkSize-1)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. The only thing I'm unsure of is the name -- was OFRAME
used elsewhere in the codebase or is this some kind of standard I'm unaware of?
I think it would be much more clear if we used START_FRAME
and END_FRAME
as our tokens. But of course we need to maintain IFRAME
as it's what everyone is using already (and it makes sense for single-frame jobs). So I guess my suggestion is:
.replaceAll("#IFRAME#", String.valueOf(frameNumber))
.replaceAll("#START_FRAME#", String.valueOf(frameNumber))
.replaceAll("#END_FRAME#", String.valueOf(frameNumber+frame.chunkSize-1))
Any thoughts from anyone else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds much better, wasn't happy about the OFRAME
anyway. :)
We could also add CHUNK_FRAME
and STEP_FRAME
. Or perhaps reverse them :
FRAME_CHUNK
, FRAME_STEP
, FRAME_START
, FRAME_END
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer reversing them to all be prefixed with FRAME_
, and agree with adding FRAME_CHUNK
and FRAME_STEP
.
That was supposed to be "Changed to FRAME_END and added FRAME_START and FRAME_CHUNK" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks!
Hello all, sorry to reopen this subject two year later, but we found an issue related to this subject. For exemple, if we have 72 frames with a chunk size of 10, unfortunatly, i don't have knowledge in java to offer you a ready to use "pull request", and only suggest you some idea like Many thanks |
Link the Issue(s) this Pull Request is related to.
#83
#104
Summarize your change.
This is to better support frame chunks in the layers.
Frame chunks are really valuable for software packages like Nuke and Houdini