GIMP sucks...

james b norman

Senior Member
Messages
2,154
Reaction score
50
Location
Salem, US
i have GIMP installed at my office and PS at home. i had been having a hard time getting decent prints at the office, and kept thinking it was my printer, or driver issues, or just my eyes were crossed or seomthing. well, today i took a shot and processed in GIMP, brought it home and processed the same file in PS to compare them. well, jeebus, they werent even close - the PS version just blew away the GIMP version. i thought gimp was supposed to be pretty good, but i think i am going to have to just stop using it at all. i need ACR for the D200 now...
--
jnorman
sunridge studios
salem, oregon
D200, 18-70mm (calmly awaiting 17-55mm)
Cambo 45NX, nikkor SW 90/8, 135/5.6, 210/5.6
 
james b norman wrote:
i thought gimp was supposed to be
pretty good, but i think i am going to have to just stop using it
at all. i need ACR for the D200 now...
--
Well, maybe... I use GIMP exclusively, but did get a chance to work in-depth with PS-CS in a college course. I was able to get nearly identical results between the two programs, and ended up using GIMP for all my final work (although I must admit to being a little jealous of the healing brush and highlights/shadows)...

A couple of things to check:
1) Did you shoot in ARGB? Gimp is SRGB only...
2) If using NEF, what Raw converter did you use?
--Michael
 
I use Gimp as primary editor in Linux and have to label the processed images to be able to tell whether they were done in PS or Capture from Windows or the Gimp or Bibble in Linux. They all look about the same to me.
Jim
 
Your monitors are likely not calibrated to show the same image. So a comparison with between your GIMP at your office and PS at home is meaningless. It is also likely that your office monitor is off color, so that is why your office prints suck.
 
horsepix nailed it - that was the problem. i am shooting all ARGB. no wonder... duh. i wonder now how i was supposed to know that about gimp. thanks to all.
--
jnorman
sunridge studios
salem, oregon
D200, 18-70mm (calmly awaiting 17-55mm)
Cambo 45NX, nikkor SW 90/8, 135/5.6, 210/5.6
 
horsepix nailed it - that was the problem. i am shooting all ARGB.
no wonder... duh. i wonder now how i was supposed to know that
about gimp. thanks to all.
Not to worry -- simple mistake. GIMP's lack of color space management (my main reason for eagerly awaiting the 2.4 release) means that it's only going to work with the "standard" SRGB space. Any app that's not color space aware (like IE, gimp, etc) is likely expecting SRGB.

--Michael
 
which plugin is it, and what is the name of the dll?
gimp-color-manager-0.1.0

I went back and re-tried the plug-in, and I recall now that I was able to clear up the .dll issue, but I ran into a problem with setting the .icc directory. Anything I enter gives me an error message "Not a directory". I figure this is a latent Linux vs. Windows issue...

--Michael
 
  • well, probably you do not know how to cook them.
I've tried both stir fry and stew.

--
Detroit Reds Wings - Original Six Hockey with Motown Style!
Twenty six, ten, and three, Ottawa is otta luck!

Detroit Pistons - Twenty five and four!
Number 1 in the NBA!

Ciao!

Joe

http://www.swissarmyfork.com
 
it was the issue in 0.0.9; 0.1.0 added revised code to make paths platform-independent. still, end slash may be an issue.

default dir for color profiles is
home/user .gimp-2.0/color/

author can be contacted through [email protected]

--
Julia
 
It sounds like a color management problem. Has nothing to do with gimp. Get a hardware color calibration system like spyder pro. One of these 2 pc's seems to be way off.
 
It sounds like a color management problem. Has nothing to do with
gimp. Get a hardware color calibration system like spyder pro. One
of these 2 pc's seems to be way off.
To the contrary, I'd say this is a color management problem.

Bob Peters
 

Keyboard shortcuts

Back
Top