strip rendering & unnecessary overlap

[dynaman]

hey guys - i'm new to rendering using backburner and have encountered an annoying glitch that i can't figure out...

so far i've had no trouble setting up my network and i've been working on net rendering single frames using strips. everything is running fine and i am able to complete my renders and they look fine. but the problem is that my servers are all computing strips that are much larger than they need to be. i have the overlap set to zero, so i can't understand why they are still calculating a larger strip than required.

for example, i have been running tests on a 800x600 frame. i have it set to render in 20 strips, and hence the strip size should be 30 pixels. but each strip is coming out at 54 pixels. what this amounts to is almost twice what it needs to be, and much longer rendering times than required.

i can't figure out what i could be doing wrong. i have tried using both pixel and percentage options for the strips, but it's still exactly the same result. i have also tried different number of strips, but no matter what the servers generate significant overlap.

can anyone suggest what i may be doing wrong? thanks in advance for any advice.

[Tim Nelson]

I don't think you're doing anything wrong. Unfortunately I think that the strips always overlap even when you tell it not too. So, you lose some efficiency there, but if you have enough computers it is still worth it.

[dynaman]

thanks tim. i was hoping that's not the case...seems like an awful lot of redundancy, especially in a small network. do you think it would be more efficient to use larger strips? i will run some tests myself to check on this.

[dynaman]

just to follow up, i ran some tests using larger strips, and it appears that there is a 24 pixel overlap rendered, regardless of the other settings. this is fairly insignificant when rendering larger frames.