I am afraid you've hit a design issue with the GIMP -
when adjusting colors via tools, i t simply operates on the whole
image for each preview step.
The options let to you right now are workarounds:
Either select a small part of the image, preview on that part, hit
cancel, select all the imagem, anbd adjust to the optimal previewd
values later. Or - if yoou need to see the effect in the wholke
image, make a copy of the image, scale it so it gets smaller (like
800x600), and select your adjustment values on the scaled down
version. Them apply these values to the larger image.
Sorry, but currently the GIMP does not automate that, and it, in this
case, has not to do with RAM, it is raw CPU power that counts.
On Friday 28 January 2005 08:33, Dana Sibera wrote:
> I'm having what seem to be performance issues with editing some
> images about 4000x2200 pixels (they're panoramas of multiple
> photos), and would like some advice on the best settings in GIMP
> for RAM use, or whether what I'm seeing is normal.
> I have 640MB in this machine, and GIMP is set to use a tile cache
> size of 400MB. By the look of GIMP's info in the window of the
> photo I'm editing, it's only taking 161MB once flattened, so I
> don't think RAM use is the problem, but could be wrong - I'm not
> familiar with exactly how GIMP best uses memory :).
> In any case, the specific problem I'm getting is while colour
> balancing of the final image, and each shift of the slider requires
> a bit over 20 seconds to complete the colour change over the image,
> which seems slower than it should be. It's just a little difficult
> to really get an idea how the before/after compare when it doesn't
> flick from one adjustment to another in time to see it 'real time'.
> thanks in advance,
> Gimp-user mailing list
Gimp-user mailing list