nisus Posted December 8, 2006 Share Posted December 8, 2006 Hi all, I'm using m9/MR but i cannot render longer than 600minutes. I've tried to override the settings on a per job basiS (64000minutes) but it just doesn't work. Anyone got a clue on how to solve this? rgds, nisus Link to comment Share on other sites More sharing options...
ITryMyBest Posted December 9, 2006 Share Posted December 9, 2006 i will start by saying i am still using max 8. what i have may not be a solution, but when sending a job you can click the advanced button to the right of submit when the job description dialog box comes up. this will allow you to change the timeout setting without having to do it in the monitor. and of course you can change it in the monitor by right-clicking on the job and edit settings. the real problem i think is the 64000 minutes. that's actually 44days 10hrs 40mins. if you have a rendering that takes that long, you need to optimize something. if this is an animation, try breaking the job into several smaller ones. just so you know, i typically use 2400 minutes since i do have single large resolution images that can take over 600 minutes. and just to confirm the timeout deals with the rendering time for a single frame, not the entire job (unless the job is only a single frame). this post was entirely too long, so i hope it helps. Link to comment Share on other sites More sharing options...
nisus Posted December 10, 2006 Author Share Posted December 10, 2006 Hi, Tnx for your reply. when sending a job you can click the advanced button to the right of submit when the job description dialog box comes up. this will allow you to change the timeout setting without having to do it in the monitor. and of course you can change it in the monitor by right-clicking on the job and edit settings. this is the manual override I was talking about, so this is what I do... the real problem i think is the 64000 minutes. that's actually 44days 10hrs 40mins. if you have a rendering that takes that long, you need to optimize something. This is a just-in-case value to be safe at any time. Renders don't take so long, but some exceed 10hours (600minutes)... So the 10hours iS the problem... so why 6400? better safe than sorry ,-) rgds, nisus Link to comment Share on other sites More sharing options...
Chad Warner Posted December 10, 2006 Share Posted December 10, 2006 I don't know if this helps, but back with max 6 or 7, I had installed backburner on a local machine and then copied over the installation to the manager machine, and had the exact same problem you are having now. Only when I did the install on the manager machine did the timeout function work like it was supposed to. So maybe the answer is to reinstall the manager? Link to comment Share on other sites More sharing options...
nisus Posted December 10, 2006 Author Share Posted December 10, 2006 Hi Chad, Do I lose the jobs in the queue when I re-install the manager? rgds, nisus Link to comment Share on other sites More sharing options...
jucaro Posted December 10, 2006 Share Posted December 10, 2006 Do I lose the jobs in the queue when I re-install the manager? You won't so long as the contents of ..\Backburner\Network dont get deleted Best regards Link to comment Share on other sites More sharing options...
nisus Posted December 13, 2006 Author Share Posted December 13, 2006 Tnx All, We idd forgot to update the manager. Stupid, we have updated all machines except the server... just didn't think about it, because it doesn't need a max... ow ow ow... We also could keep the whole queue ,-) **OUFF** rgds, nisus Link to comment Share on other sites More sharing options...
Chad Warner Posted December 13, 2006 Share Posted December 13, 2006 Glad you got it worked out. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now