This version was really dedicated to get rid of some annoying bugs ( those which are really hard to get and hard to catch ).Mac users, you should have a more stable version now.Big panorama creators, you can use smartblend on standard computer and still create gigapixels. We did that on a mono cpu 1 giga memory NEW : You will found a new button near the smartblend drop button => you can play with those values, there are internal smartblend value which can be interesting to play with.

We have now branched this 1.* series and we'll work 100% on v2.0. You want to know what's inside v2 ? ... You are curious ! We have planned many stuff as we always want the best in our tool.For the last big release, it wasn't really clear with the version naming. We came up with this idea :v1.9.0 => pre2.0 with first feature integratedv1.9.1 => pre2.0 with second feature integrated ....When we have finished integration, we'll do RC until stability is good enough to create first release.

Nice done! BUT: whatÂ´s the deeper sense of that for practical work? What after all is the exact meaning/definition of "pyramidal"?Where does it come fom? I mean: itÂ´s very interesting what the wiki says . . but . . does this "pyramidal"- thing only influence/equalize colors?What means: "It's not coded as a pyramid level but as a stop condition." Is a "pyramid-level" something like an exposure-level or numbers of f-stops?In fact, this description doesntÂ´tell me anything at all . . .

2) why no attempt at using 2, 1 or 0 values ? (= are value smaller than the default useless ?)

__________________

On the same web page the interpolator section is a clear example of why documentation is difficult: it's obvious for any experienced user that the example is shown at 200% or more but inexperienced users will not figure that and will probably conclude using Spline64 is preferable !

That specifying example image sizes is mandatory is not obvious for everybody : I run the risk to look like a very boring person!

2) why no attempt at using 2, 1 or 0 values ? (= are value smaller than the default useless ?)

__________________

On the same web page the interpolator section is a clear example of why documentation is difficult: it's obvious for any experienced user that the example is shown at 200% or more but inexperienced users will not figure that and will probably conclude using Spline64 is preferable !

That specifying example image sizes is mandatory is not obvious for everybody : I run the risk to look like a very boring person!

Hi GURL!

Yes - some simple descrition to start from in a way like:"if you want a result like THIS you have to do THAT" . . or something like that would be fine. When iÂ´d have time enough iÂ´d tend to test everything and gather experiences - but iÂ´m in two productions at the moment to make three real big pictures printed @150dpi at app. 1,50x7m iÂ´d welcome some hard facts to ease my work and get optimal results. Without spending days and nights of stitching/rendering again and again to explore new options in a software.

So in some bare words: what smartblend setting would show the best results in this task for an optimum resolution and sharpness?