No problems with small pics (< 20 Mpix) but CS4/Neutralhazer crashes on bigger ones (I suspect RAM crash).
What does it mean: "on bigger pics"? HOW big? I guess NH should be used *before* stitiching. On the
camera-size images - not on the rendered panorama.
NH analyzes the overall / final image to create a artificial depth map to make it's calculations so applying the filter to single images and then stitching the panorama later would not be using the filter correctly.
Indeed i experienced it as more effective using the filter on the input images inside APG. ThatÂ´s my personal experience and so it is my personal opinion.
Another point is the size of the image to get filtered when itÂ´s a very big one - as you experienced yourself recently . .
- Photoshop needs VERY much RAM anyway for working fluently.
I sugst at least 16 GB RAM for handling gigapixels without having cake-and-tea-time after each command and also when saving a, letÂ´s say, 9GB file . .
The worst case i had was selecting a sky using a soft lasso of 200px and running a Gauss blur . . took about 25 min. to show only the preview . . . and another 20 min to fine-render it.
In CS6 itÂ´s a bit easier: you can keep on working while CS6 saves in the background - big step ahead in terms of workflow.
(i use a MacPro, 2x3GHz Xeons, 8 cores, 16GB RAM and 8TB of fast HDs inside).
So when it comes to gigapixel panos: yes, i definitely prefer to de-haze the images before stitching.