I agree with you about the old; does a better job with with seamless textures too. I use both since now, thanks to the efforts of some cool folks, compiled both to work synergistically and I do have both in my plugins folder.

and you just ninja'd me Esper.

yes i know..
i included both in my Gimp_PhotoComix_Lab with all the scripts and even Texture Ops..
Well i adding now Texture Ops to the version on the server but was already in my local copy

Thanks for the feedback, guys! I figured that possibly the most common use of the plugin would be around Heal Selection (for image retouching), so that was my primary focus.

I did try to link to one of lylejk's neat (recent) tutorial on seamless textures to kind of show what other things could be done... (Honestly, it would probably be worth it's own tutorial for using Resynthesizer bare without the Heal Selection script).



I honestly wasn't aware of other scripts that made use of Resynthesizer (well - geared towards photographic retouching). Any chance you could point me in their direction (I'd love to see some other cool uses!)

you just posted a message in the place where are a group of scripts for resynthesizer all in python, from Bootchk, and his version of Resynthesizer

Because actually are 2 version, the original that anyway still work,(and was recompiled not long ago to work with gimp 2.8 ) and that of Bootchk that decided to maintain the plugin that was no more maintained from long and was risking to die, and each cannot use scripts written for the other

that why me and lylejk have both the version installed the older seems work better for the use you did in the tutorial, the newer anyway is also interesting even if don't give exactly same results

I'm sorry, I wasn't clear in my response - I guess I meant scripts other than the packaged ones (enlarge, heal trans, fill pattern, sharpen, etc) that bootchk had bundled up.

Of course you're right - these probably deserve a look all on their own (and might be helpful to see them in the context of other options as well ie: enlarging methods and the results from each to compare).

And to be honest, this is kind of a bummer when trying to track down which version of Resynthesizer + scripts to install for the average user. It's not really clear which way to go from the registry...

What would be nice would be a package maintainer for GIMP plugins/scripts (like apt/yum built into GIMP directly). A GIMP "App Store" if you will. I wonder how hard it would be to put something together?

Had to give it a try. Before and after.

Nice job O. I was playing around with it last night. It works very well.

Lylejk mentioned an old and a new version of the Heal Selection plugin. How can I tell which one I have, and is there a link where I can download both the old and new scripts? (I'm assuming that it's only a difference in individual scripts and not the Resynthesizer plugin/executable itself).
Thanks
(added) Gimp 2.8.2 Portable, Windows 7 64bit

Well, if we're going to be sharing our fiddling around with this - how about a rejected image that I was originally going to lead the blog post off with?




To be fair, I cheated by using a clone tool to fix the ropes, but only for the top two ropes - everything else was pure Heal Selection. (And only took about 2 minutes to do!)

I'll let Lyle/PC answer, but I believe the problem is that the difference is actually the compiled resynth.exe/resynthesizer.exe and not the scripts (though they may need to be modified to point to the correct version).

To complicate things, there are two versions of the old plugin and scripts. The newer old plugin and scripts needed 2 more parameters passed to it. than the old old one did.

I solved as Salomon i have both (luckily Samj recompiled the old version to run alongside the newer with no conflict ) and i even installed both in my customized Gimp builds (see new board)

But if i am sure that will work in Windows i am less sure for other OS

Chose only and install only one seams more complex and less rewarding

Both version support a "Heal selection " script but not the same (that for the newer version is in python )

@charlie34

It is as patdavid said, the registry.gimp.org site has pages of comments and old links. Also git is not much use unless you want to do your own compiling.

On another forum the same question came up (but for win7 32 bit) and I found the 0.16 + python plugins produced very strange results. I did find the the v1.0 from samj worked fine.
Win7 64 bit, you will have to do your own try-out but compiled versions are here:
http://samjcreations.blogspot.co.uk/201 ... -gimp.html
look a bit further than half-way down the page for this section.

Resynthesizer
http://www.aljacom.com/~gimp/bootchk-re ... 64bits.zip
9295371 octets

Ancien Resynthesizer compatible avec la nouvelle version.
http://www.aljacom.com/~gimp/resynthesi ... 64bits.zip
2313573 octets

Ancien Resynthesizer.
http://www.aljacom.com/~gimp/Resynthesi ... 0-i686.zip
9265550 octets

Just had a look in the bootchk zip and I would pop the 2 .exe files + whatever python scripts you want in your plugins folder (wherever that is in a portable version).

Two I've written are:

resynthesize along a path: viewtopic.php?f=9&t=3716#p46302
resynthesize pattern fill (direct link): http://www.silent9.com/incoming/scripts ... n_fill.scm

-Rob A>

I put this on another forum, a bit off topic here so appologies

Resynth along path used to work on my installation Gimp 2.6.12 but now

In Gimp 2.8.0 (both PCLOS linux and WinXP) I get this error

Resynth along Path Message
Error while executing script-fu-resynth-path:
Error: (<unknown> : 143982218)
Procedure execution of gimp-edit-stroke-vectors failed on invalid input arguments:
Item 'Unnamed' (3) cannot be used because it is attached to another image

Its a really useful script, hope you can help.

Just a note that I've updated the script to work with 2.8 It should also still work with 2.6

http://www.silent9.com/incoming/scripts/resynth_along_path.scm

-Rob A>