-
Notifications
You must be signed in to change notification settings - Fork 253
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
-continue_with option #8
Comments
Exactly, with the option There is also a |
I must have done something wrong. I had rendered frames 1 to 35. Should I have set -continue_with to 35 or 36? (in order to render frame 36 as the next frame upon resumption) More importantly, would I have needed to set the -seed on the first run to some particular number for this to work? In other words, in order for -continue_with to work correctly, must -seed be set during the initial run as well? (I didn't set it on frames 1 to 35, so suspect that it is now 'lost' if I want to continue) ?? Thanks for the quick response. |
You have to set -continue_with to 36 in that case. No, it is not required to use a custom seed value in order to use the -continue_with parameter. The seed value is only needed to initialize the first frame. After that, frames are initialized with information from the previous frames, therefore it doesn't matter what seed value you have chosen or if you have set a custom seed value at all. But a seed value may be help to evaluate the effect of different parameter settings, because if you always use the same seed, the algorithm will always start from the same random initialization in the beginning. |
Great! Thanks for the info. |
@manuelruder How does the Wouldn't it make sense for |
If a render session get interrupted, does this option allow us to restart at the 'next' frame and maintain the previous style continuity? I didn't see it referenced in the documentation other that what is in the artisitic_video.lua file
I've noticed that different runs of the same video and style frame result in different initial frames. (probably due to random initialization).
I'm trying to figure out if it's possible to safely interrupt a long render without creating a glitch between frames and what settings would need to be set either during the initial run so as to preserve the start state and/or later during a resumption.
Thank you for your help.
The text was updated successfully, but these errors were encountered: