search

JakeClark1129 / Wolfkrow

GNU General Public License v3.0
4 stars 0 forks source link

Bug with frame ranges #5

Open aloyisus opened 1 year ago

aloyisus commented 1 year ago

Hey,

I've noticed that if I submit a task with replacements e.g. {'start_frame': 0001, 'end_frame': 0010}, then the resulting render has range 0001-0008, i.e. 0010 has been resolved to 0008 somehow.

Note that it doesn't matter whether the numbers are strings or ints, I still get the same result.

Cheers,

John.

JakeClark1129 commented 1 month ago

Hey, Sorry for the delay! I have not been monitoring the issues! (Perhaps I should start...). I imagine that you've probably figured this out already or have moved on... But just in case:

This sounds like a chunking issue with SequenceTask's. By default the chunk size is set to 8, which explains why the range is updated to 0008.

What should happen is that a 10 frame task will get split into 2 separate tasks - frames 1-8, and then frames 9-10. How are you submitting the task? "execute_local", or "execute_deadline"?

If you are running "execute_local" I suspect that this is a bug in the code because chunking probably shouldn't happen at all when executing locally because it's all run on the same host anyway.