Ungimping the Gimp, part 3

in design

(As an aside, the above video is my first HTML5 YouTube embed, because it puts flash playback to shame on my Netbook. Technology advances ever onward!)

I used The Gimp for a few solid hours this morning. Observsations:

  1. GEGL grinds The Gimp to a halt. I have no idea if it is tied to the size of the files in question. I eventually gave up on a GEGL unsharp mark and instead just duplicated the layer to sharpen it the old-fashioned way.
  2. The eXperimental Computing Facility (XCF) file format is The Gimp’s native workabout file format. It is equivalent to Adobe’s PSD format in that it It supports saving each layer, the current selection, channels, transparency, paths and guides, but, nicely for me, it seems less of a hog in raw file-size.

    I grabbed Kharanos #1, renamed it as 1.jpg to enhance its aesthetic purity and plugged it into both Adobe Photoshop CS4 and The Gimp 2.7.1. In each editor I created a new and blank layer, saved and exited. The results were:

    • 1.jpg was 4.5MB.
    • 1.xcf was 24MB.
    • 1.psd was 45MB.

    Ah, yeah. I created a new layer and the overall file-size jumped tenfold. Nice one, Photoshop. I love working on panoramas, and I’m restricted to a Netbook. File-size makes a huge difference in performance. Gimp win.

  3. As a result of the above file-size differences, The Gimp is noticeably nippier on my Netbook as compared to similar work (with all three files open at once) when compared to Adobe Photoshop CS4.
  4. Even with the single-window improvements in 2.7.1 (and onward), the defaults still occasionally feel ass-backward. I’ve so far remapped the majority of the “core” keyboard shortcuts.
  5. I like the clone tool. Photoshop’s “preview” is frequently distracting and equally frequently doesn’t reflect the reality of the final finish.

Xlendi Run

in malta

Your email address will not be published. Required fields are marked *