- Tue Jul 01, 2014 2:28 pm
#381660
Hello,
We are currently testing Maxwell for the first time on a job and are running into a strange issue.
Basically the Maxwell Render Manager seems to be switching frame numbers around.
Here is a more detailed explanation:
We have exported an .mxs sequence from Softimage, which we then load into the Render Manager and assign to a bunch of workstations. Everything is fine, until you remove a machine from the render pool.
What seems to happen is that when that machine later gets reassigned to the same job, it picks up a new frame but doesn't start rendering, and the frame just stays greyed out in the Render Manager for a short lapse of time. Then the Render Manager assigns the machine to the next available frame, but in fact it actually starts rendering the previous frame (which remains greyed out) but saves it out as the newly assigned frame. What is also very serious is that in some cases it will be picking up a frame that is partly rendered (the job is in resume mode) and thus will overwrite it with the other frame.
So for example
1. the machine picks up frame 37 of the sequence
2. it fails to start rendering (or to resume if it is a partly rendered frame)
3. the Render Manager moves the assignment of that machine to frame 38 (while keeping frame 37 greyed out)
4. the machine actually renders frame 37, but writes it out as frame 38
5. If frame 38 had already been partly rendered by another machine previously, bad luck you've lost that frame.
Note that this only happens when the Render Manager is performing automatic assignment, not when we manually assign machines. We could of course just manually assign, but it's not very practical!
Any help on this matter would be highly appreciated.
Kind regards,
Jean-Louis
Digital Golem
We are currently testing Maxwell for the first time on a job and are running into a strange issue.
Basically the Maxwell Render Manager seems to be switching frame numbers around.
Here is a more detailed explanation:
We have exported an .mxs sequence from Softimage, which we then load into the Render Manager and assign to a bunch of workstations. Everything is fine, until you remove a machine from the render pool.
What seems to happen is that when that machine later gets reassigned to the same job, it picks up a new frame but doesn't start rendering, and the frame just stays greyed out in the Render Manager for a short lapse of time. Then the Render Manager assigns the machine to the next available frame, but in fact it actually starts rendering the previous frame (which remains greyed out) but saves it out as the newly assigned frame. What is also very serious is that in some cases it will be picking up a frame that is partly rendered (the job is in resume mode) and thus will overwrite it with the other frame.
So for example
1. the machine picks up frame 37 of the sequence
2. it fails to start rendering (or to resume if it is a partly rendered frame)
3. the Render Manager moves the assignment of that machine to frame 38 (while keeping frame 37 greyed out)
4. the machine actually renders frame 37, but writes it out as frame 38
5. If frame 38 had already been partly rendered by another machine previously, bad luck you've lost that frame.
Note that this only happens when the Render Manager is performing automatic assignment, not when we manually assign machines. We could of course just manually assign, but it's not very practical!
Any help on this matter would be highly appreciated.
Kind regards,
Jean-Louis
Digital Golem
- By hwolfejr
- By choo-chee