-
Notifications
You must be signed in to change notification settings - Fork 4
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
Tiled rendering #473
Tiled rendering #473
Conversation
@guidow, you ready for a review of this? |
Yes, this is ready for review now. |
task.priority = job.priority | ||
db.session.add(task) | ||
if num_tiles: | ||
for tile in range(0, num_tiles - 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.
Use the appropriate range so we get a generator:
try:
range_ = xrange
except NameError:
range_ = range
Also, you don't need to include the starting 0.
Seems generally ok and much simpler than I guess I was expecting. I thought it might be beneficial to offer two modes of tiling, one where the jobtype on the agent determines how to tile the image and another where the user can. But...this setup will probably work fine and it's not like we couldn't include something more customizable later. |
e8bb5a8
to
7dba203
Compare
instead of x / y values. After some deliberation, it seems more useful to leave the exact splitting of frames into regions to the jobtype. The resulting regions may even be non-uniform, which could allow users to render the parts the deem most important first.
I've rebase this branch to master to make it mergable again. |
Any more objections to merging this? |
Nope none, sorry for the delay got caught up on another project. Merge when ready. |
No description provided.