I did try to do a search on this Kevin, but it didn't find it; must have not done it right. Oh well. Now I'll get reemed again. lol

better consider kindly duplicate bug record to avoid the risk of unreported bug

I mean better do the best to avoid duplicate but may happen what should not happen is people giving up:
no more reporting real and maybe critical bugs because burned by stingy comments on previous report, similar comment are
no smart (..to use a euphemism.. ).

I got a very nice email back this time saying, yes, it's been already reported, but also to encourage me to report more bugs as I see them. Much better then the reem I got last time. lol

Like the new atmosphere by the developers. Give them all a raise I say.

I started getting too many memory allocation errors with the RC1 version.
Plus i was getting a libgimp error for the PDB calls?
I completely uninstalled it and re installed Gimp-2.6.12.



All better now.

2.8 rc1 64-bit hasn't crashed on me yet Rod and my last session's been open for several hours now; beginning to believe it's a keeper. Now I do have 6 Gigs of RAM, but I also have Virtualbox, PostworkShop, and FotoSketcher open concurently until just a few seconds ago (now just Virtualbox XP and GIMP). I do hope the issues that have been found get patched soon. I would give it a week or two so that more issues can be ferreted out.

GIMP Version: 2.8.0-RC1 (32Bit)
Operating System: Windows
OS Version: win 7-x64
GIMP develop Experience: bloody beginner

Hi all.

I have activated the color management thing in gimp, and I could also see the slow-down,
when activating the color management filter.
I tried to optimize the code, but I didn't find anything to optimize...
Many programs, that make use of lcms show a significant slow-down, when using color management.
So maybe it is not a problem of gimp, but a problem of lcms.
But the lcms version, gimp uses, is >= 1.6 and this is the old version.
The current version is 2.3, but this differs from 1.9 sigificantly.
So I changed some files in gimp source to use lcms 2.3, so when there is a speedup in lcms2,
gimp can make use of it. I think, with the changed files, gimp 2.8.0 RC1 reacts somewhat faster, but that is maybe
just a wish... So I don't know, if it really works. So maybe here is anyone who can test it?
I zipped the changed files. lcms-1.dll can be deleted, but now, lcms2-2.dll is required.
In my Gimp-2.8.0-RC1, the libjpeg-8.dll is required, because of a problem with marker length.

Hatti

Hi Onkel Hatti - you are very good -Groß Hatti

1. First This is the solution to the problem jpg (1.3 GB) -thanks HATTI !
2. You can temporarily solve the problem tiff:
change the files:
file-tiff-load.exe
file-tiff-save.exe
from version Partha 2.7.6 to 2.8 RC1
and add (to bin) libtiff-3.dll
3.Uuserfilter (gufF) -edit file gimprc - paste the path:
(userfilter-path "C:\\~~\\~~\\guf")
Now it all works...

to 2.:

I got the same problem. Libtiff seems only to be used for tiff loading/saving.
Maybe there is a problem with libtiff-5, I don't know.
I renamed libtiff-3.dll to libtiff-5.dll and VOILÀ :-)

Hatti

oh, I forgot:

Don't forget to post the JPG solution in Bugzilla...

Hatti

Thanks a heap for the User Filter solution MareroQ; it worked. Going to share this solution at GIMPUsers giving you full credit by linking it to your entry. Fantasic stuff.

Well shoot; another issue now arises. If userfilter works, it prevents PSPI to work and vise versa. Going trump PSPI over userfilter since those filters are more important to my workflow. Oh well.

i didn't try but from the screenshoot i have doubts that the jpg problems was really fixed:
sure the file size preview seems more reasonable but looking better i believe is still very incorrect.

If the same file is of 66.3 kb saved a 60 can't be of only 76 at 100...but at least 3 x bigger

The curve is not linear as example a file saved at 96 is about half of the size of the same saved at 100,not sure how much less would be at 60 i never used a so high compression but should be much less then the the half...

A simple way to test would be confront that with the result of the RIOT save for the web plugin that give more reliable info

PS obviously if the screenshoot doesn't refer to the same file...never mind
But if is the same i believe that the file size reported can't be trusted in any way

Maybe, maybe not.
But it's somewhat academic.
When gimp tells me, the size will be ~200Kb, then the result is ~200Kb
And when it tells me, the size will be ~80Kb, then it is 80Kb.
So, the resulting preview size is correct 'per definitionem'

Hatti

Are we looking for problems - or their serviceable solutions?
Onkel Hatti - works for me (Bugzilli - I do not know) - You are great.
Every system (computer) is different - for some work - not for others.
Solution - experiment - and I know the answer - share your way ....

Solution for LqR plugin and 64-bit GIMP

Download Partha's 64-bit build of Liquid Rescale, extract gimp-lqr-plugin.exe plugin and then download the attached dll and place it in the same plugins directory as gimp-lqr-plugin.exe (had a completely different program that had this dll file which LqR was looking for which is cool). It works; trust me.

Partha's 64-bit plugins: http://www.partha.com/downloads/Gimp-2. ... s-64bit.7z

I went ahead and created a bugzilla with this strange gimprc file behavior w.r.t. the user filter path and PSPI filter path. Below's the entry.

https://bugzilla.gnome.org/show_bug.cgi?id=674096

you got a reply with a relevant question

I think i will just wait until Gimp-2.8 is nice and stable

The only issue that makes it not what I had with GIMP 2.6.12 Rod is PSPI/User Filter. I did submit a bugzilla since I believe it's a bug with how gimprc file is handled by GIMP rather then the plugins themselves. I can live with having to poing to the guf files each time since I rarely use the user filter; I need PSPI. Other then that, I'm quite happy with 2.8 64-bit stability. Hasn't locked up on me yet after near 3 days of use. I can't say that about GIMP 2.6.12.

This solution fixed the Tif issue Onkel Hatti. Even fixed mm-filters Sigmoidal Contrast python plugin, but did not fixe mm-filters Lab Curves unfortunately. Guess you can't win them all. lol

I used Partha's Delaboratory's (already had Delaboratory so why not) libtif-3.dll file which I renamed to libtif-5.dll per your post; didn't want to re-download GIMP 2.7 again. lol