Viewpoint Correction Render time improvement???

[gavinfarrell]

Hey Joost,

I'm working on a job with hundreds of panoramas. being rendered for an
extremely special situation, that render perfectly with Viewpoint
correction turned however the small 7Gig renders take 5 1/2 days to
render and the the large ones 16-25 Gigs 2 1/2 weeks.
My hardware configuration is fairly robust and is not the issue here.
I know I've brought up this discussion exactly a year ago but I
thought I should ask as perhaps there's been some new developments in
your continued amazing development of this software. Without some sort
of solutions I'm looking at several years of continued non-stop
rendering which is serious waste of electricity. For example with
viewpoint correction turned off I get a wall that is supposed to have
straight lines slightly curved and it only take 6 hrs to render
opposed to 5 days. Is there anyway, or any feature/code addition you
can make to the speed of renders with Viewpoint turned on, I beg you!!

[PTGui Support]

Hi Gavin,

I can only say that I'm aware of this and it's still on my radar..

Joost

[Joergen Geerds]

On Apr 14, 6:52 am, PTGui Support <supp...@ptgui.com> wrote:
> I can only say that I'm aware of this and it's still on my radar..

I am with Gavin here on this point.
I know the original use for the VP feature is the nadir fix, and it
literally doesn't matter computational, if a "small" project (anything
smaller than 20x10k) needs a couple of seconds longer...
but, it does matter in large projects, as I have experienced it, and
Gavin, and now Greg (and probably a handful of people who did not
speak up yet).
The VP feature helps to reign in stitching errors for large works,
either a true panorama, or for flat 2D reproductions (as Gavin and
Greg are doing now), where the lens wasn't at the perfect NPP (for
whatever reason). VP would need to be turned on for all but one in the
center to work.
I am not sure why ptgui needs to do "unoptimized" warping for those
tiles, but since VP is a killer feature, using it brings huge
computational penalties: rendering goes from a couple of hours to days
and weeks, and that is usually the part where the fun in rendering
large works with "problems" stops.

I do not know how you would fix it in your rendering engine, but if
it's not too much work, please do it (soon).
(think of Gavin, he is forced to spend quality time with his family
while the rendering is happening, instead of spending days and nights
sitting behind the computer doing productive work :-))

joergen
360nyc.com

[perspixe]

+1