Backburner hanging on very high res image.

[Crazy Homeless Guy]

So, who here has rendered extreme resolution images?

 

I am rendering a 25,000 pixel wide image. It renders and saves fine locally, but when I try and render it though BackBurner it does not save. Instead, Backburner seems to hang, and never actually completes the image.

 

This could potentially be a Mental Ray / Backburner problem instead of just a Backburner problem. It seems to call the output shaders for MR, and I can't remember if it makes it past that point, but again, it calls and saves fine if I am only rendering locally.

[Spacelord]

Hi Travis,

Thats extremely high res image, whats it for ?

If your output shaders are for glow I'd recommend trying to add it in photoshop.

I've never had glow work properly rendering to strips. (if thats what your doing)

You might be better satelite rendering it.

Not sure if you have seen this article on dpi, ppi, etc.. Really interesting

You might not have to render that large.

http://www.cgpipeline.com/?p=30

[Crazy Homeless Guy]

Hi Travis,

Thats extremely high res image, whats it for ?

If your output shaders are for glow I'd recommend trying to add it in photoshop.

I've never had glow work properly rendering to strips. (if thats what your doing)

You might be better satelite rendering it.

Not sure if you have seen this article on dpi, ppi, etc.. Really interesting

You might not have to render that large.

http://www.cgpipeline.com/?p=30

 

Not using glare, or any other post output shader, but MR is still making a call to the shader. I am guessing it processes rendering outputs through a shader for the info on how to write to a the file type you specified. But again, that is just a guess based on MR does other things.

 

I tired using strips, and I tried using region render to divide up the image. Both had the same result... Backburner/MR starts to write a file to the hard disk. It creates a 1k file then hangs. If I open a copy of Max locally on each renderfarm machine, draw a box, and hit render, the file renders and has no problems saving the file to the hard disk.

 

As for resolution... This is for a 2.25m meter by 7.5 meter print that is viewable from 4 feet away. In reality I should be rendering somewhere around 45,000 pixels wide to get the clarity I want from the viewable distance, but given it will be printed on fabric with a large format printer, I am guessing I will loose a little clarity anyway.

 

Overall the image can render on a dual quad core with 8gb ram in about 16-18 hours or so the overall total time for the render really isn't that bad.

 

....all that said, I haven't tried to reassemble this in Photoshop yet, so I could be in for another headache.

 

As a funny side note, this image is the equivalent to taking a photo with a 182 mega-pixel camera. Sweet.

Edited March 9, 2009 by Crazy Homeless Guy

[Spacelord]

In the the camera shaders rollout, is the output glare shader there but not checked ?

I wonder if it would make a difference if it was totally removed.

 

That res sounds a bit overkill to me, but good luck.

It would be sweet to have the cash to do some test prints at different resolutions to see the difference.

[Crazy Homeless Guy]

Just double checked. All of the slots are completely clean in the camera shader rollout. Before I start blaming this on MR to much, I want to double check to make sure I have the exact point it is hanging at. It might be the step immediately after it calls the output shader.

 

I think this is my first image over 8000 pixels.

[Crazy Homeless Guy]

Still need to go back and comp the people, but it rendered through. It is funny the details you miss when doing low res checks before going full res. Like floating cars....

 

The first image is the entire image reduced of course. The second is a crop before the image was reduced.

[SandmanNinja]

huge renders are definitely eye poppers!

[demo38]

I wish I could see that larger on the iPhone, looks great though. Colors, composition... Nice work Travis.

[Spacelord]

Wow thats one huge render, nice job.

[SandmanNinja]

I wonder if that Split-a-Huge-Render-into-smaller-jobs script would have helped?

 

I've made some really huge renders.

[Crazy Homeless Guy]

I wonder if that Split-a-Huge-Render-into-smaller-jobs script would have helped?

 

I've made some really huge renders.

 

?? ...is this different from Zap's script?

 

I started off using Zap's script. The first run through, I didn't specify the file location, and I could never find where they went. So then I que'd it again with a pathed file location, but for some reason it crashed on the 7th segment out of 16. After that point I used region rendering to fill in the rest.

 

The weird thing about Zap's scripts compared to the region renders was that the registration wasn't perfect. I still haven't exactly figured out how the registration was off, just that it wasn't perfect.

Edited March 10, 2009 by Crazy Homeless Guy

[ihabkal]

great render, very nice project indeed.