Hi Dana!

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.

Regards, JS
->

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, Dana

Dana Silbera wrote:

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'.

I think you're right, actually. (You must have a pretty slow machine, though -- it only takes about 3 seconds for an image that size on mine.)

I have noticed before that the previews for the image map tools (of which color balance is one) seem slower than they ought to be. The operation they are doing is extrememly simple, so they ought to be as fast as other simple tools like bucket-fill, but they are not.

Best, -- Bill

______________ ______________ ______________ ______________ Sent via the CNPRC Email system at primate.ucdavis.edu

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and  /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins BUT... if I a ask to acquire an image  neither xsane nor xscanimage are displayed in the file->acquire menu (sorry I'm translating the menu item from Italian into English!)

What should I check and do in the end? (A step by step explanation please)

Ciao Vittorio

--
gentoo-user@gentoo.org mailing list

Hi,

Dana Sibera writes:

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'.

Color correcting the image affects all pixels, so such an operation needs quite a bit of memory on the undo stack. So you might be filling up the tile cache with undo steps here. Lowering the number of minimum undo steps could help to improve this.

But then, the color correction tools in GIMP are definitely slower than they would have to be and most probably the time it takes is just the time that it takes.

Sven

Alle 11:11, sabato 29 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins BUT... if I a ask to acquire an image neither xsane nor xscanimage are displayed in the file->acquire menu (sorry I'm translating the menu item from Italian into English!)

What should I check and do in the end? (A step by step explanation please)

Ciao Vittorio

Hello

I don't know about the xscanimage, but for xsane do as described in the readme:
To run xsane under the gimp(1), simply set a symbolic link from the xsane-binary to one of
the gimp(1) plug-ins directories.

I did it, as I said in my message. Ciao
Vittorio

Hi,

"Joao S. O. Bueno Calligaris" writes:

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.

I don't think this counts as a design issue. A design problem would be something that could not be solved without a major redesign. The speed of the color adjustment preview can certainly be improved based on the current design.

Sven

On Sat, Jan 29, 2005 at 08:05:15AM +0000, Vittorio wrote:

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and ?/usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins BUT... if I a ask to acquire an image ?neither xsane nor xscanimage are displayed in the file->acquire menu (sorry I'm translating the menu item from Italian into English!)

-->Acquire and it should be in this list.

carol

Vittorio wrote:

Alle 11:11, sabato 29 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins BUT... if I a ask to acquire an image neither xsane nor xscanimage are displayed in the file->acquire menu (sorry I'm translating the menu item

from Italian into English!)

What should I check and do in the end? (A step by step explanation please)

Ciao Vittorio

Hello

I don't know about the xscanimage, but for xsane do as described in the readme:
To run xsane under the gimp(1), simply set a symbolic link from the xsane-binary to one of
the gimp(1) plug-ins directories.

I did it, as I said in my message.

No - in your message you said it was in:

The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/

but it has to be as an symbolic link in your user plug-ins directories, like:
~/.gimp-2.0/plug-ins/

Alle 02:30, domenica 30 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Alle 11:11, sabato 29 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins

.................................................

I don't know about the xscanimage, but for xsane do as described in the readme:
To run xsane under the gimp(1), simply set a symbolic link from the xsane-binary to one of
the gimp(1) plug-ins directories.

I did it, as I said in my message.

No - in your message you said it was in:

The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/

but it has to be as an symbolic link in your user plug-ins directories, like:
~/.gimp-2.0/plug-ins/

You're right, sorry!
I put this new link as you said but still doesn't work,i.e. xsane (which works standalone, I repeat) is seen by the Gimp as a plug-in BUT doesn't appear in the menu.
Ciao
Vittorio

Hi,

"William Skaggs" writes:

I have noticed before that the previews for the image map tools (of which color balance is one) seem slower than they ought to be. The operation they are doing is extrememly simple, so they ought to be as fast as other simple tools like bucket-fill, but they are not.

It doesn't surprise me that filling with a solid color is faster than applying a color-correction. I don't think the image map tools are implemented particularily slow (but of course I would like to see a faster implementation). The problem rather seems to be that the effect is applied on the whole image instead of doing some kind of preview that takes the viewed area and display scale into account.

Sven

Hi,

Vittorio writes:

I put this new link as you said but still doesn't work,i.e. xsane (which works standalone, I repeat) is seen by the Gimp as a plug-in BUT doesn't appear in the menu. Ciao Vittorio

How do you know that it is seen by GIMP as a plug-in? Did you locate it in the Plug-In Browser (as found in Toolbox->Xtns)?

Sven

Vittorio wrote:

Alle 02:30, domenica 30 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Alle 11:11, sabato 29 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins

.................................................

I don't know about the xscanimage, but for xsane do as described in the readme:
To run xsane under the gimp(1), simply set a symbolic link from the xsane-binary to one of
the gimp(1) plug-ins directories.

I did it, as I said in my message.

No - in your message you said it was in:

The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/

but it has to be as an symbolic link in your user plug-ins directories, like:
~/.gimp-2.0/plug-ins/

You're right, sorry!
I put this new link as you said but still doesn't work,i.e. xsane (which works standalone, I repeat) is seen by the Gimp as a plug-in BUT doesn't appear in the menu.
Ciao
Vittorio

How, as a standalone? if I call xsane without the Gimp open, it by default scans to viewer, file or others, but under Gimp, it scans to the Gimp.

My xsane under Gimp is located under 'file/acquire' from top-menu.

Alle 15:17, domenica 30 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Alle 02:30, domenica 30 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Alle 11:11, sabato 29 gennaio 2005, Mogens Jaeger ha scritto:

Vittorio wrote:

Context:
pentium 4, kde 3.3.2, the very last build of linux gentoo compiled from scratch; gimp 2.0.4, xsane 0.96, xscanimage 1.0.13; epson usb scanner

Both xsane and xscanimage alone work smoothly with the usb scanner. The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/ contain @xsane and @xscanimage.
When I launch the gimp 2.0 I see during the booting phase of the program that xsane and xscanimage are detected as plugins

.................................................

I don't know about the xscanimage, but for xsane do as described in the readme:
To run xsane under the gimp(1), simply set a symbolic link from the xsane-binary to one of
the gimp(1) plug-ins directories.

I did it, as I said in my message.

No - in your message you said it was in:

The directories /ushr/lib/gimp/2.0/plug-ins/ and /usr/local/lib/gimp-2.0/plug-ins/

but it has to be as an symbolic link in your user plug-ins directories, like:
~/.gimp-2.0/plug-ins/

You're right, sorry!
I put this new link as you said but still doesn't work,i.e. xsane (which works standalone, I repeat) is seen by the Gimp as a plug-in BUT doesn't appear in the menu.
Ciao
Vittorio

How, as a standalone? if I call xsane without the Gimp open, it by default scans to viewer, file or others, but under Gimp, it scans to the Gimp.

My xsane under Gimp is located under 'file/acquire' from top-menu.

Right, I mean that I tried to verify if xsane worked, was in order. So, launching it on its own, outside the gimp I could work with it to acquire an image, a fax, etc. So xsane exists & works, isn't "out of order". Its the combination of xsane & the gimp that doesn't seem to work properly.

Ciao Vittorio

Alle 14:23, domenica 30 gennaio 2005, Sven Neumann ha scritto:

Hi,

Vittorio writes:

I put this new link as you said but still doesn't work,i.e. xsane (which works standalone, I repeat) is seen by the Gimp as a plug-in BUT doesn't appear in the menu. Ciao Vittorio

How do you know that it is seen by GIMP as a plug-in? Did you locate it in the Plug-In Browser (as found in Toolbox->Xtns)?

Sven, when you launch the gimp, at the very beginning during the booting a rectangular box with the word Gimp 2.0 and many running words occupies the display. One of those running words is "plug-ins" and another is "xsane". This intutevely makes me think that xsane has been detected.

Ciao Vittorio
I

Hi,

Vittorio writes:

Sven, when you launch the gimp, at the very beginning during the booting a rectangular box with the word Gimp 2.0 and many running words occupies the display. One of those running words is "plug-ins" and another is "xsane". This intutevely makes me think that xsane has been detected.

Sure, that tells you that GIMP sees the plug-in executable and queries it. It doesn't tell you anything about the results of this query. Looking at the Plug-In Browser, as I told you, would probably give you some useful information.

Sven