 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Deckker wrote:
klausesser, If what you say is true, would contacting Kolor Tech support be the best way to resolve this? Because its a problem in the code already.
Don´t know - that´s just a feeling. Single images of about 300MB each seem to be not the usual task for a stitcher in my eyes . .
I didn´t compare the H3D files directly to 5DmkII or 1DSmkII/III files. But the latter ones even in their very best mode are by far smaller.
Maybe the H3D 16bit mode is a too heavy challenge for the whole system - even for an 8core MacPro.
If that is a basic problem in APP - i really don´t know. I guess 1.4.2 might be overstressed - maybe it´s a task for an upcoming server-version of APG . . Alexandre will tell us i´m sure.
best, Klaus
Offline
klausesser wrote:
Deckker wrote:
klausesser, If what you say is true, would contacting Kolor Tech support be the best way to resolve this? Because its a problem in the code already.
Don´t know - that´s just a feeling. Single images of about 300MB each seem to be not the usual task for a stitcher in my eyes . .
I didn´t compare the H3D files directly to 5DmkII or 1DSmkII/III files. But the latter ones even in their very best mode are by far smaller.
Maybe the H3D 16bit mode is a too heavy challenge for the whole system - even for an 8core MacPro.
If that is a basic problem in APP - i really don´t know. I guess 1.4.2 might be overstressed - maybe it´s a task for an upcoming server-version of APG . . Alexandre will tell us i´m sure.
best, Klaus
Well I will work on it still, trying to use DNG now, since the H3D raw will not work in anything but their own software.
Offline
OK I finally give up...its not happening.
Offline
Deckker wrote:
Well I will work on it still, trying to use DNG now, since the H3D raw will not work in anything but their own software.
This is a very special case you´re discussing here.
I strongly advise to work the RAW over in Phocus, save as TIFF or even JPG and give them to APP or the APG Alpha.
As i see it we´re at a transition-point where the "usual" APP - which fits the needs of surely 75% of all users - is transformed into a version to handle very large amounts of pictures for very big resolutions.
I remember the "Harlem 13Gigapixel" example - Alex told to have split the big amount of shots into groups of 300 shots to get it done. I´m sure that was about the time he started to think about a "stronger" version of APP - which led to APG, i think.
Btw.: did you try othe stitchers?
best, Klaus
Offline
The mac version needs the 64bits version to handle big panorama. It has been compiled last week and it works great. We'll need some more time to check that everything is okay.
Offline
Deckker wrote:
Hello All,
I am trying to attempt at a Gigapixel HDR shot. My Autopan Pro has being crashing when I try to detect the pano. It is about 200+ Photos from my H3DII-50, where each file size is about 300mb each(8176 * 6132 Tiff 16bit, PhotoRGB), so its about 60+ gig of actual data.
Now I have read the FAQ on handling such panos. I am Wondering if anyone else is having trouble with this?
I run a 8 core Mac with 16 gig of Ram, should be enough Hardware.
...what makes you think that's enough HW to do what you are trying to do with APP on it?
Have you tried tracking the APP memory use...and the free memory in your system?
What's the crash error? Does it just lock up, go away or spit an error message like GPL "can't get memory"
Why don't you try working from the center outwards, get it to stitch & render the center first, adding images from the periphery to make the overall pano bigger?
Or try reducing the total MP requirement, run the pics through a batch tool to downsample them to say 12MP or even 3MP tiffs from the current 48MP tiffs, and then try that set. Each step there will only cost you half the linear resolution. You can adjust DPI to get the desired output resolution and then use the higher-resolution sources if you really want the IQ.
I'd start with the 3MP set at 300dpi and work up from there. And track APP memory usage during the process. It will help to close the group after it has detected the pano and let the prerenderer run on its own.
Last edited by touristguy87 (2009-02-24 00:43:00)
Offline
there's no point in doing this in jpeg if he wants to use tiff sources.
that will oversimplify the process.
just start with less image-data and get it to work then increase the resolution of the sources.
if the DPI doesn't actually affect the output resolution then reduce the output % and see if that helps anything. In fact you might as well start with that at 20% or so and use 3MP sources then see if you can get it to render at all...track the APP memory use during the process and work up from there.
the basic effect that I see using the output % slider is that smartdrive will use so much free space depending on that 10-20MB per MP of final image data. So the first question is how big is the pano going to be, in pixels, rendering to 100%, using the desired source images. You can't really know that for sure until the render completes at least once. If say 200 3MP images are giving you output that's 100MP at 100% and APP requires say 2GB peak ram and 2GB peak disk space to do that, then scaling up the MP will linearly scale up the output, as well as the peak ram and disk-space required. Then as long as APP doesn't run into any internal limits then you should be able to scale up output resolution to the limit of your hardware.
If it does run into internal limits then you have to reconfigure APP itself.
The only problem with this is of course all the time that it will take to downsample the sources and render the low-resolution panos. But you have to start somewhere.
Last edited by touristguy87 (2009-02-24 00:53:06)
Offline
I was having real trouble getting APP to render large images with SmartBlend on Vista 32bit. The only way round was to use a simpler blend than SmartBlend. Moving to Win7 64bit and the latest AutoPano Giga beta seems to have sorted this. I haven't managed to crash out on a SmartBlend since I upgraded.
Andy.
Offline
andybryant wrote:
I was having real trouble getting APP to render large images with SmartBlend on Vista 32bit. The only way round was to use a simpler blend than SmartBlend. Moving to Win7 64bit and the latest AutoPano Giga beta seems to have sorted this. I haven't managed to crash out on a SmartBlend since I upgraded.
Andy.
I switched to the Linux version on Ubuntu and that seems to work nicely.
The batch renderer is much easier to control.
but even with the win32 version smartblend never actually "crashed out" on me. Maybe it would be a good idea to monitor it in task manager once?
Last edited by touristguy87 (2009-03-01 02:18:42)
Offline