3 smart GIMP tricks

No readers like this yet.
amphicar

Opensource.com

If you're interested in improving your GIMP (GNU Image Manipulation Program) skills and you'll be attending SCaLE 14x this month, you'll want to check out Akkana Peck's talk, Stupid GIMP tricks (and smart ones, too). Peck knows a thing or two about GIMP—she's the author of Beginning GIMP: From Novice to Professional. In her SCaLE 14x talk, Peck plans to answer the age-old questions, "How do you get rid of the ugly power lines in that landscape photo, and would it look better with a purple sky?" and "How do you take that picture of you and your ex and replace his face with Brad Pitt's?"

In this interview, she shares three of her favorite GIMP tricks, and she explains how GIMP stacks up against Photoshop.

Tell us about three of your favorite GIMP tricks

I think my favorite depends on what I've been working on recently. Three I like a lot:

  1. The Quickmask for adjusting selections: I'm a born-again Quickmask evangelist, because I went so long without realizing that it was there, and it makes selections so much easier.
  2. Decomposing an image and using the components as a mask to select part of an image—that's an easy way to select skies and get rid of a drab overcast sky, or to change or enhance the color of the sky.
  3. Using the Dodge/Burn tool to make a background really white, for when you want an object to stand out and make the background go away. It can be a lot easier than selecting or erasing.

What's a cool GIMP feature that many users might not know about?

A new one coming in 2.9/3.0: You can get to pretty much any GIMP function by typing / (slash) and then typing some keywords. No more hunting through the menu hierarchy for what you want. As an old command-line junkie, I expect to be using this all the time, though for now I'm still working on retraining myself to remember it's there.

How can I take photos of me with my ex and replace his face with Willie Nelson's?

Come to my talk!

It all comes down to using selection tools. There are lots of ways to make selections, but for cutting objects (like a face) out of a photo, I usually start with the lasso, being sure to feather the edges, and clean things up with the Quickmask.

What are the biggest areas in which GIMP needs to improve before people will think it's "as good" or better than Photoshop?

Honestly, I think a lot of the people claiming GIMP isn't as good as Photoshop are people who have invested a lot in learning Photoshop and want an excuse not to learn a new and different tool. If the GIMP team spent much time trying to make everything just like Photoshop, they'd never have time to implement great new features.

It's true there are some nice features Photoshop has that GIMP doesn't. Some are being addressed for GIMP 3.0, like high-color images. A lot of people will be very happy to see that. Other features, like non-destructive editing and CMYK, are still wish-list items that will have to wait until later.

I have a vision: 2016 will be the Year of the Open Source Haiku. What's your GIMP advice, given via haiku?

Bad photography
Face too dark and sky too bright
Good thing I have GIMP

User profile image.
Rikki Endsley is the Developer Program managing editor at Red Hat, and a former community architect and editor for Opensource.com.

2 Comments

What are the biggest areas in which GIMP needs to improve? Most will quickly reply, without thinking, "usability", but that's a poor answer, you already covered: a 100% Photoshop clone wouldn't necessarily be better. The area where I, as a daily user, I find the poorest is performance. I use Linux, so I can't make a direct speed comparison with Photoshop, but compared with darktable, GIMP is really slow for some image processing.
Yes, I know, somewhere on the roadmap, long after the gegl integration is done, hardware acceleration is supposed to help improve performance, but there are some solid years until then.

Another area where I would like GIMP to fare better, and for which I am not aware about any development is RAW image import where, again compared with darktable, is poor: both as user interaction, features set and performance.

CMYK has been "waiting until later" since the 1.0 release, that is Spring of 1998. Nearly two decades "waiting until later".

Creative Commons LicenseThis work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License.