Slashdot Mirror

← Back to Stories (view on slashdot.org)

GIMP Resynth vs. Photoshop Content Aware

Posted by CmdrTaco on from the in-this-corner dept.

aylons writes "Just after Adobe released videos showing off the content-aware feature of Photoshop CS5, the GIMP community answered by showing the resynthesizer plugin, which has been available for some time and can do a similar job. However, are they really comparable? (In original Portuguese, but really, the images are pretty much self-explaining.) Compare them side by side removing the same objects from different kinds of images. Results do vary, but the most interesting part may be seeing the different results and trying to understand the logic of each algorithm."

4 of 269 comments (clear)

  1. I'm sure... by AcquaCow · · Score: 4, Insightful

    I saw that site a few weeks ago when folks were going gaga over PS's "new" feature (GIMP Resynth has been around for a few years now)...

    I'm sure Adobe has seen it, I'm sure Adobe took the time to try and make theirs better.

    The question is the Adobe implementation worth the cost of PS, or is the GIMP plugin "Good enough"

    That really comes down to the consumer though. I think it is "Good enough" for my needs...I can easily touch-up anything it does that I disagree with.

      -- Dave

    --

    up 12 days, 22:30, 2 users, load averages: 993.20, 994.21, 994.56
    *makes note to limit user processes...
    1. Re:I'm sure... by Rogerborg · · Score: 4, Insightful

      Bingo, we're into Drake Equation territory here.

      Hell, even if you do know about it, good luck actually using it. After 15 minutes of apt-get fiddling and chanting mantras, I'm still unable to get the damn thing working in GIMP 2.6.7. For a feature whose primary purpose is to save you time, it sure could do with an FONT OF GOD sized install guide that explains how to (actually) get it working.

      --
      If you were blocking sigs, you wouldn't have to read this.
    2. Re:I'm sure... by Alphathon · · Score: 5, Insightful

      I think the main problem most "pseudo-professionals" have with GIMP is familiarity. I myself use OpenOffice.org regularly and the transition from Microsoft Office was extremely simple - download it and start using it. The same is not true of GIMP since it's UI is so different than Photoshops. These "pseudo-professionals", almost certainly have a long history with Photoshop, so understand how to do things using it's UI, but likely don't even know where to start with GIMP and write it off as useless. It is closed minded, but certainly understandable on a professional/semi-professional level. Blender seems to suffer the same problem, since it's UI is vastly different than any other 3D program I've tried (although since there are more available than in the photo-editing world no one program has a "monopoly" on the UI so it's not quite as bed).

      Most FOSS doesn't tend to have this problem because it either does a specific task that has no industry standard UI, Emulates the industry standard UI (like OpenOffice.org) or is so simple that it makes little difference how the UI is designed as long as it works (things like 7-zip for example - its function is to open and create archives. You don't have 100s of filters and tools to use so everything can be put into a couple of menus and not be confusing).

  2. Re:Moot point by MrHanky · · Score: 4, Insightful

    Most of the 'prosumers' I've seen dismiss Gimp just repeat stuff they've read on Slashdot, knowing that it makes them look +5, insightful. They're probably as lazy when it comes to learning new tools as they are when it comes to independent thought.