You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was doing a long video render (6 minutes) and found my runs were arbitrarily stopping at around 2000 frames. After digging through the code it looks like they stopped because the steps_per_scene value was arbitrarily set to 60000 or so and I was doing 30 steps per frame.
This steps_per_scene value seems kind of non obvious to me. Consider dropping this limit at least for Video Source?
The text was updated successfully, but these errors were encountered:
oh okay lol just realized that even with video source an arbitrarily high number of steps_per_scene will result in near endless rendering. so what we really need is a way to calculate the steps_per_scene number based on the length of the video input.
I like your thinking here. I don't think it should be too hard to add a setting for something like "process all frames in video source". conversely, could probably add a warning or something along those lines to alert the user if the steps per scene is too low to run the length of the video.
I was doing a long video render (6 minutes) and found my runs were arbitrarily stopping at around 2000 frames. After digging through the code it looks like they stopped because the steps_per_scene value was arbitrarily set to 60000 or so and I was doing 30 steps per frame.
This steps_per_scene value seems kind of non obvious to me. Consider dropping this limit at least for Video Source?
The text was updated successfully, but these errors were encountered: