Inpainting filter
Locked
 
|
Hi list,
Can anyone make the inpainting filter do anything? Once in a while, I try to use this to remove a zit, a dust spot or some other small annoyance in a photo. But it never does anything useful. Currently, it often crashes digikam. What I try to do is, straight ahead: Select an area with a spot, select the "remove small artefact", and press "try". I never get a usable result, as indicated in the manual. A sample of a typical selection is attached. Any demonstration of a succesfull use of this tool would be very wellcome, the more detailled the better. -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
sample spot (5K) |
|
I run Dk3.5.0 on openSUSE 12.3/KDE 4.11.4
Took me a while to find inpainting - it is a tool when edit sub-process is open. I selected an area and "try" - got no useful response, just like Anders. Maybe it would crash if I waited long enough? On 12/10/2013 06:55 AM, Anders Lund
wrote:
Hi list, Can anyone make the inpainting filter do anything? Once in a while, I try to use this to remove a zit, a dust spot or some other small annoyance in a photo. But it never does anything useful. Currently, it often crashes digikam. What I try to do is, straight ahead: Select an area with a spot, select the "remove small artefact", and press "try". I never get a usable result, as indicated in the manual. A sample of a typical selection is attached. Any demonstration of a succesfull use of this tool would be very wellcome, the more detailled the better. _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
On Tirsdag den 10. december 2013 19:06:36, Carl McGrath wrote:
> I run Dk3.5.0 on openSUSE 12.3/KDE 4.11.4 > > Took me a while to find inpainting - it is a tool when edit sub-process > is open. > > I selected an area and "try" - got no useful response, just like Anders. > Maybe it would crash if I waited long enough? 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. Maybe I am wrong when saying crash, inpaint rather disables digikam, it sometimes goes into an infinite, blocking state of doing nothing, with busy cursor on. My only solution to that is to kill the digikam process. The digikam manual contains an example of using inpainting, which is exactly similar to what I want to achieve, but I NEVER made it work. I have to say that I have given up on trying to use this plugin. I try to learn to use krita instead, which offers a lot more options, such as filter masks, layers etc. If you'd like to use krita for retouching, look at the options for the "duplicate" brush, which apart from dumb cloning have a "healing" option that can be enabled for very handy behavior with photos. I'm yet to find out how using krita will affect metadata handling. Anders > On 12/10/2013 06:55 AM, Anders Lund wrote: > > Hi list, > > > > Can anyone make the inpainting filter do anything? Once in a while, I try > > to use this to remove a zit, a dust spot or some other small annoyance in > > a photo. But it never does anything useful. Currently, it often crashes > > digikam. > > > > What I try to do is, straight ahead: Select an area with a spot, select > > the > > "remove small artefact", and press "try". I never get a usable result, as > > indicated in the manual. > > > > A sample of a typical selection is attached. > > > > Any demonstration of a succesfull use of this tool would be very wellcome, > > the more detailled the better. > > > > > > > > _______________________________________________ > > Digikam-users mailing list > > [hidden email] > > https://mail.kde.org/mailman/listinfo/digikam-users -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Thanks Anders. From your description, sounds like intent is similar to
RedEye removal, with greater color selection. I tend to use GIMP for both Red Eye and InPainting, primarily because I have more issues with flash reflection than red eye. I have Krita loaded as well, may give it a try. On 12/11/2013 05:53 AM, Anders Lund wrote: > On Tirsdag den 10. december 2013 19:06:36, Carl McGrath wrote: >> I run Dk3.5.0 on openSUSE 12.3/KDE 4.11.4 >> >> Took me a while to find inpainting - it is a tool when edit sub-process >> is open. >> >> I selected an area and "try" - got no useful response, just like Anders. >> Maybe it would crash if I waited long enough? > 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. > > Maybe I am wrong when saying crash, inpaint rather disables digikam, it > sometimes goes into an infinite, blocking state of doing nothing, with busy > cursor on. My only solution to that is to kill the digikam process. > > The digikam manual contains an example of using inpainting, which is exactly > similar to what I want to achieve, but I NEVER made it work. > > I have to say that I have given up on trying to use this plugin. I try to > learn to use krita instead, which offers a lot more options, such as filter > masks, layers etc. > > If you'd like to use krita for retouching, look at the options for the > "duplicate" brush, which apart from dumb cloning have a "healing" option that > can be enabled for very handy behavior with photos. > > I'm yet to find out how using krita will affect metadata handling. > > Anders > > >> On 12/10/2013 06:55 AM, Anders Lund wrote: >>> Hi list, >>> >>> Can anyone make the inpainting filter do anything? Once in a while, I try >>> to use this to remove a zit, a dust spot or some other small annoyance in >>> a photo. But it never does anything useful. Currently, it often crashes >>> digikam. >>> >>> What I try to do is, straight ahead: Select an area with a spot, select >>> the >>> "remove small artefact", and press "try". I never get a usable result, as >>> indicated in the manual. >>> >>> A sample of a typical selection is attached. >>> >>> Any demonstration of a succesfull use of this tool would be very wellcome, >>> the more detailled the better. >>> >>> >>> >>> _______________________________________________ >>> Digikam-users mailing list >>> [hidden email] >>> https://mail.kde.org/mailman/listinfo/digikam-users _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Hi all,
I agree that inpainting tool is in failure. This is due to unmaintained CImg framework used inside where some regressions are appears. Tools relevant must be ported to Gmic library instead. This include Inpainting and Restoration tools (this last one work fine here). The simplest solution will be to remove inpainting tool as well from digiKam core until code is ported to GMic. We need a student to work on it. I have tried to give this project to a guy this summer without success... Best Gilles Caulier 2013/12/11 Carl McGrath <[hidden email]>: > Thanks Anders. From your description, sounds like intent is similar to > RedEye removal, with greater color selection. > I tend to use GIMP for both Red Eye and InPainting, primarily because I have > more issues with flash reflection than red eye. > I have Krita loaded as well, may give it a try. > > > On 12/11/2013 05:53 AM, Anders Lund wrote: >> >> On Tirsdag den 10. december 2013 19:06:36, Carl McGrath wrote: >>> >>> I run Dk3.5.0 on openSUSE 12.3/KDE 4.11.4 >>> >>> Took me a while to find inpainting - it is a tool when edit sub-process >>> is open. >>> >>> I selected an area and "try" - got no useful response, just like Anders. >>> Maybe it would crash if I waited long enough? >> >> 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. >> >> Maybe I am wrong when saying crash, inpaint rather disables digikam, it >> sometimes goes into an infinite, blocking state of doing nothing, with >> busy >> cursor on. My only solution to that is to kill the digikam process. >> >> The digikam manual contains an example of using inpainting, which is >> exactly >> similar to what I want to achieve, but I NEVER made it work. >> >> I have to say that I have given up on trying to use this plugin. I try to >> learn to use krita instead, which offers a lot more options, such as >> filter >> masks, layers etc. >> >> If you'd like to use krita for retouching, look at the options for the >> "duplicate" brush, which apart from dumb cloning have a "healing" option >> that >> can be enabled for very handy behavior with photos. >> >> I'm yet to find out how using krita will affect metadata handling. >> >> Anders >> >> >>> On 12/10/2013 06:55 AM, Anders Lund wrote: >>>> >>>> Hi list, >>>> >>>> Can anyone make the inpainting filter do anything? Once in a while, I >>>> try >>>> to use this to remove a zit, a dust spot or some other small annoyance >>>> in >>>> a photo. But it never does anything useful. Currently, it often crashes >>>> digikam. >>>> >>>> What I try to do is, straight ahead: Select an area with a spot, select >>>> the >>>> "remove small artefact", and press "try". I never get a usable result, >>>> as >>>> indicated in the manual. >>>> >>>> A sample of a typical selection is attached. >>>> >>>> Any demonstration of a succesfull use of this tool would be very >>>> wellcome, >>>> the more detailled the better. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Digikam-users mailing list >>>> [hidden email] >>>> https://mail.kde.org/mailman/listinfo/digikam-users > > > _______________________________________________ > Digikam-users mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-users Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Inpainting filter
|
|
In reply to this post by Anders Lund
Hi Anders and Carl, Some comments from my personal experience. (I happen to do inpainting and I use both Krita and Gimp, depending on what I want to do.) On Wed, 11 Dec 2013, Anders Lund wrote: > 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. Similar idea, but not exactly the same processing. The healing brush in Krita is a sophisticated clone tool which take in account not only the strict pixels under the clone reference but also some neighbour pixels to "extrapolate" what should be cloned.. It works really well when correcting some small details as you mention, spots, scars. True inpainting relies on a mathematical model of an image area, that can be used to rebuild a whole subarea, the blind spot. It's an image synthesizer. It will give far better results when you want to remove an unwanted area of your image, hamburger box thrown on a lawn, unwanted person on the background of an image, satellite tv antenna from a 18th century straw roofed cottage, etc. Gimp has such a synthesizer. It's not provided by default, you have to download and install the gimp-plugin-resynthesizer-xxxx for your Gimp version. (And also the gimp-plugins-python-xxxx if not yet installed.) For simple corrections (a small spot), usage is really trivial. - select the unwanted area of your image with the free hand selector (lasso) - activate Filters > Enhance > Heal selection - click Ok in the dialog box and you're done 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. Anyway, it's possible to do great things. > I'm yet to find out how using krita will affect metadata handling. From what I know, Krita behaves fairly with metadata. Not Gimp. All versions have a broken XMP management and we'll have to wait for Gimp V 3.0 to have correct handling. The solution for Gimp users is to protect existing XMP data into sidecar files (or Digikam DB), to be restored later into images. Regards, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Thanks for the info, very interesting
I'll give the GIMP plug-in a try while we wait for Digikam In_Painting to return On 12/12/2013 11:34 AM, Jean-François
Rabasse wrote:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Jean-François Rabasse-2
Hi Jean-François,
Thanks for the helpful information! Anders On Torsdag den 12. december 2013 17:34:53, Jean-François Rabasse wrote: > Hi Anders and Carl, > > Some comments from my personal experience. > (I happen to do inpainting and I use both Krita and Gimp, depending on > what I want to do.) > > On Wed, 11 Dec 2013, Anders Lund wrote: > > 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. > > Similar idea, but not exactly the same processing. The healing brush in > Krita is a sophisticated clone tool which take in account not only the > strict pixels under the clone reference but also some neighbour pixels > to "extrapolate" what should be cloned.. > It works really well when correcting some small details as you mention, > spots, scars. > > True inpainting relies on a mathematical model of an image area, that can > be used to rebuild a whole subarea, the blind spot. > It's an image synthesizer. > It will give far better results when you want to remove an unwanted area > of your image, hamburger box thrown on a lawn, unwanted person on the > background of an image, satellite tv antenna from a 18th century > straw roofed cottage, etc. > > Gimp has such a synthesizer. It's not provided by default, you have to > download and install the gimp-plugin-resynthesizer-xxxx for your Gimp > version. (And also the gimp-plugins-python-xxxx if not yet installed.) > > For simple corrections (a small spot), usage is really trivial. > - select the unwanted area of your image with the free hand selector (lasso) > - activate Filters > Enhance > Heal selection > - click Ok in the dialog box and you're done > > 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. > > Anyway, it's possible to do great things. > > > I'm yet to find out how using krita will affect metadata handling. > > From what I know, Krita behaves fairly with metadata. > Not Gimp. All versions have a broken XMP management and we'll have to wait > for Gimp V 3.0 to have correct handling. > The solution for Gimp users is to protect existing XMP data into sidecar > files (or Digikam DB), to be restored later into images. > > Regards, > Jean-François -- Anders _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
In reply to this post by Jean-François Rabasse-2
For anyone trying the gimp-plugin-resynthesizer-xxxx, a caution that
for x86_64 users, you may see a startup error running Gimp.
The gimp-plugin-resynthesizer-xxxx is 32 bit, requires applicable 32 bit libraries. On 12/12/2013 11:34 AM, Jean-François
Rabasse wrote:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
Re: Inpainting filter
|
|
On Wed, 18 Dec 2013, Carl McGrath wrote: > For anyone trying the gimp-plugin-resynthesizer-xxxx, a caution that for > x86_64 users, you may see a startup error running Gimp. > The gimp-plugin-resynthesizer-xxxx is 32 bit, requires applicable 32 bit > libraries. Hi Carl, I don't know what Linux flavour you run, but you should perhaps investigate a bit into your distribution downloadable packages. As for me, I run openSuSE 12.2 and I get 64 bits software from here : http://download.opensuse.org/repositories/graphics/openSUSE_12.2/x86_64/ The plugin I installed and use is a 64 bits RPM gimp-plugin-resynthesizer-2.0-2.1.x86_64.rpm (opnSuSE also provides the 32 bits version gimp-plugin-resynthesizer-2.0-2.1.i586.rpm) Regards, Jean-François _______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
|
|
Thanks for your suggestion.
I did not think to check oS repository fiirst (I run 12.3/KDE4.12.0), so went to gimp on Sourceforge and downloaded tarball. I removed that, installed gimp-plugin-resynthesizer-2.0-2.1.x86_64.rpm and it works MUCH BETTER. On 12/19/2013 02:25 AM, Jean-François
Rabasse wrote:
_______________________________________________ Digikam-users mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-users |
«
Return to digikam-users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |