<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
For anyone trying the gimp-plugin-resynthesizer-xxxx, a caution that
for x86_64 users, you may see a startup error running Gimp.<br>
The gimp-plugin-resynthesizer-xxxx is 32 bit, requires applicable 32
bit libraries.<br>
<br>
<div class="moz-cite-prefix">On 12/12/2013 11:34 AM, Jean-François
Rabasse wrote:<br>
</div>
<blockquote
cite="mid:alpine.LNX.2.00.1312121707250.8728@azrael.victoria.net"
type="cite">
<br>
Hi Anders and Carl,
<br>
<br>
Some comments from my personal experience.
<br>
(I happen to do inpainting and I use both Krita and Gimp,
depending on
<br>
what I want to do.)
<br>
<br>
On Wed, 11 Dec 2013, Anders Lund wrote:
<br>
<br>
<blockquote type="cite">I believe the idea behind inpainting is
something like the healing brush in krita (or that other image
editing app out) - use the surroundings to cover an area that
sticks out, like a spot or zit or ridge.
<br>
</blockquote>
<br>
Similar idea, but not exactly the same processing. The healing
brush in
<br>
Krita is a sophisticated clone tool which take in account not only
the
<br>
strict pixels under the clone reference but also some neighbour
pixels
<br>
to "extrapolate" what should be cloned..
<br>
It works really well when correcting some small details as you
mention,
<br>
spots, scars.
<br>
<br>
True inpainting relies on a mathematical model of an image area,
that can
<br>
be used to rebuild a whole subarea, the blind spot.
<br>
It's an image synthesizer.
<br>
It will give far better results when you want to remove an
unwanted area
<br>
of your image, hamburger box thrown on a lawn, unwanted person on
the
<br>
background of an image, satellite tv antenna from a 18th century
straw roofed cottage, etc.
<br>
<br>
Gimp has such a synthesizer. It's not provided by default, you
have to
<br>
download and install the gimp-plugin-resynthesizer-xxxx for your
Gimp
<br>
version. (And also the gimp-plugins-python-xxxx if not yet
installed.)
<br>
<br>
For simple corrections (a small spot), usage is really trivial.
<br>
- select the unwanted area of your image with the free hand
selector (lasso)
<br>
- activate Filters > Enhance > Heal selection
<br>
- click Ok in the dialog box and you're done
<br>
<br>
For more difficult tasks, it's worth playing with the dialog box
options (Context sampling, Sample from, Filling order) and do some
tests and tries.
<br>
<br>
Anyway, it's possible to do great things.
<br>
<br>
<br>
<blockquote type="cite">I'm yet to find out how using krita will
affect metadata handling.
<br>
</blockquote>
<br>
From what I know, Krita behaves fairly with metadata.
<br>
Not Gimp. All versions have a broken XMP management and we'll have
to wait
<br>
for Gimp V 3.0 to have correct handling.
<br>
The solution for Gimp users is to protect existing XMP data into
sidecar
<br>
files (or Digikam DB), to be restored later into images.
<br>
<br>
Regards,
<br>
Jean-François<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Digikam-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Digikam-users@kde.org">Digikam-users@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/digikam-users">https://mail.kde.org/mailman/listinfo/digikam-users</a>
</pre>
</blockquote>
<br>
</body>
</html>