- Wed Jan 22, 2014 4:34 pm
#377019
While doing an animation job, there was an electric issue, and all machines stopped working.
It was a 300 frames animation to be rendered at SL intervals of 3,7,10,12.
When the problem presented 233 frames were already rendered at SL3.
So I restarted everything and choose the option RESUME.
To my surprise the Maxwell Manager opened the 233 already rendered files, opening one by one, just to realize that they reached SL3 already, a process that took forever, to start rendering frame 234 after hours of delay.
I would be happy to have a faster way to tell maxwell manager that those files were already rendered at SL3 and it do not need to waste time opening them one by one.
In a second attempt, I thought that if I change the SL intervals from 3, 7, 10, 12, to 7, 10, 12, the manager would avoid opening the mxi files just to check the SL, and it would render to the next SL interval, in this case SL7.
But I found another obstacle: It seems that the Manager refuses to render the frames 234 to 300, and it only work withy the already rendered frames from 1 to 233.
So finnally I had to create a batch job, by hand, to render frames from 234 to 300, and then run a normal animation job using resume option, once all the frames were rendered at the same SL.
As you may see this is too comnplex, and time consuming. I hope you can make a more inteligent manager that could handle all these options in an automatic way.
Ernesto
It was a 300 frames animation to be rendered at SL intervals of 3,7,10,12.
When the problem presented 233 frames were already rendered at SL3.
So I restarted everything and choose the option RESUME.
To my surprise the Maxwell Manager opened the 233 already rendered files, opening one by one, just to realize that they reached SL3 already, a process that took forever, to start rendering frame 234 after hours of delay.
I would be happy to have a faster way to tell maxwell manager that those files were already rendered at SL3 and it do not need to waste time opening them one by one.
In a second attempt, I thought that if I change the SL intervals from 3, 7, 10, 12, to 7, 10, 12, the manager would avoid opening the mxi files just to check the SL, and it would render to the next SL interval, in this case SL7.
But I found another obstacle: It seems that the Manager refuses to render the frames 234 to 300, and it only work withy the already rendered frames from 1 to 233.
So finnally I had to create a batch job, by hand, to render frames from 234 to 300, and then run a normal animation job using resume option, once all the frames were rendered at the same SL.
As you may see this is too comnplex, and time consuming. I hope you can make a more inteligent manager that could handle all these options in an automatic way.
Ernesto


- By Mark Bell