backburner - resubmitting frames from a previous job rendered by a specific server?

[mattclinch]

is there any way to rerender frames from a network render that were rendered on a specific server? one of the servers had a badly mapped network drive and dropped all the proxies, but i'm sure as hell not going to sit here and write down the 1000 or so frame numbers that it processes. any clues?

[Thablanch]

In BB monitor, you can pause the job, select an other server and assign to selected job. The job will now start on the selected machine. ( think it is in the right-click menu )

[amer abidi]

is there any way to rerender frames from a network render that were rendered on a specific server? one of the servers had a badly mapped network drive and dropped all the proxies, but i'm sure as hell not going to sit here and write down the 1000 or so frame numbers that it processes. any clues?

 

Not that i know of! Happened to me last year, 2 servers went colour blind on an animated dreamscape sky. Wasted 3 hours of my life sat down scrutinizing and interrogating thumbnails one by one, jotting down their numbers, and re-rendering them on different servers... only to find out that i missed about 10 frames... so spent another 4 hours finding them because the changes were too small to notice in thumbnail view!

[mattclinch]

what a simply ridiculous feature oversight. pah.. right, just going to re-render the whole thing. sod it...

[acjwalker]

Also had a similar problem, though it was not on many frames. I do not think there is a way I'm afraid, usually end up deleteing corrupt frames and re rendering while skipping existing frames.

 

We have similar issues with Irradiance maps as well.

[Chad Warner]

The backburner log file on the specific server will log what frames that server rendered. It might not be perfect, but at least you'll have a list that you can reference instead of trying to write them all down.

[Justin Hunt]

I think there is a way in explorer to identify the owner of the files, this way you should be able to sort them by owner and deleter the ones done by the bad machine.

 

jhv

[milfora]

I also get this happening from time to time, so what I do is:

 

1. Determine the offending PC(s) and jot down the machine ID

2. Export the log file to a .txt file

3. In a text editor (or even excel), sort the log text file by PC or asset number.

4. delete all but the corrupting PC's references. This should leave only the corrupt frame numbers.

5. Write a small batch (*.bat) to delete these frames (i.e del "I:\render\xxxx.tga" - where xxxx is the corrupt frame number)

6. Once the corrupt files are removed, re-render the scene through the Backburner Monitor (Edit Job Settings - Restart Job), making sure that the 'Skip Existing Frames' is set to 'True'. It is important to skip existing frames otherwise max will start re-rendering every frame again regardless if it already exists.

 

Backburner will then re-render only the deleted frames

 

Good luck

 

AM