Re: Wow! The Resynthesizer
(but typing E at the console gimp is running on kills the plugin without crashing the gimp too) Huu.. (this seems usefull) can someone explain this to me ... Is this a feature of having debugging compiled in..? On Sat, Jul 15, 2000 at 12:45:57PM -0400, James Smaby wrote: Just out of curiosity, for all those who are having touble with Resinthesizer, which compiler are you using? It works fine on my x86 box with ecgs, however, I'm having troubles on my alpha using gcc. At first I just assumed my problem was having a different architecture (linux programs always seem more stable on my x86 box), but after hearing that lots of people are having problems with it I wonder if it might be the compiler. gcc does tend to have trouble sometimes at making runnable code (perhaps it's more unforgiving). I am actualy getting segmentation faults on quite a few of my plugins. If I bring up the gimp, and pick the first plugin I come to (sethspin), I get a seg fault (but typing E at the console gimp is running on kills the plugin without crashing the gimp too) -James Smaby Thanks, Jeff -- | Try not to screw up. | | This will satisfy a few people,| | and amaze everybody else. | | -- Forrest Gump | | -- Winston Groom | -- | Jeff Sheffield | | [EMAIL PROTECTED] | | - http://buzzard.kdi.com/jeff/family/ | | - http://www.team-linux.com/ | --
Re: Wow! The Resynthesizer
I tried it out today and it comes out with a message "plugin crashed. this plugin messed up gimps internal state. save image and restart gimp" I use gimp 1.1.24 Perhaps the author read this and could help us out. Jens I just tried it, and both it and homogenizer crashed on initialization with segfaults. I have gimp 1.1.23 here; I'm updating from CVS at the moment and will try it again after that completes (which will probably be sometime tomorrow).
Re: Wow! The Resynthesizer
Just out of curiosity, for all those who are having touble with Resinthesizer, which compiler are you using? It works fine on my x86 box with ecgs, however, I'm having troubles on my alpha using gcc. At first I just assumed my problem was having a different architecture (linux programs always seem more stable on my x86 box), but after hearing that lots of people are having problems with it I wonder if it might be the compiler. gcc does tend to have trouble sometimes at making runnable code (perhaps it's more unforgiving). I am actualy getting segmentation faults on quite a few of my plugins. If I bring up the gimp, and pick the first plugin I come to (sethspin), I get a seg fault (but typing E at the console gimp is running on kills the plugin without crashing the gimp too) -James Smaby
Re: Wow! The Resynthesizer
On Sat, Jul 15, 2000 at 12:45:57PM -0400, James Smaby [EMAIL PROTECTED] wrote: I wonder if it might be the compiler. gcc does tend to have trouble sometimes at making runnable code (perhaps it's more unforgiving). I am actualy getting I use gcc-2.95.2 and pgcc-2.95.3 and both work fine with current gimp, including the resynthesizer. I doubt that this is the problem. Most probably, some people use a broken version of glibc (redhat for example delivered an alpha version of glibc for quite some time, this is now fixed and redhat is not the only offender in the "we have the latest version" tragedy). If that is the case, specifying -D__NO_STRING_INLINES -D__NO_MATH_INLINES on the gcc commandline usually fixes that. (But there could be another reason) vanilla glibc-2.1.3 should be fine with respect to these problems. -- -==- | ==-- _ | ---==---(_)__ __ __ Marc Lehmann +-- --==---/ / _ \/ // /\ \/ / [EMAIL PROTECTED] |e| -=/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+ The choice of a GNU generation | |
Re: Wow! The Resynthesizer
I am actually using resynthesizer right now, and while I'm dissapointed as to its speed (um, can we say days to render?), the output is generally very nice and seems stable (at least on my x86 box). I recently emailed the maintainer to ask if it is supposed to be as slow as I am getting it. I think that make seamless is what I should be using (it works much faster), but this sometimes makes odd-looking tiles, and so resynthesizer is a good alternative (just let it run over night :) -James Smaby
Re: Wow! The Resynthesizer
On Fri, 14 Jul 2000 10:31:17 -0700, Alex Harford [EMAIL PROTECTED] said: http://www.csse.monash.edu.au/~pfh/resynthesizer/ Has anybody on the list tried this plug-in? I'm at work right now so I can't try it, but I am going to as soon as I get home. Basically it is for removing things from images automatically, and also working with textures/tileable images. I just tried it, and both it and homogenizer crashed on initialization with segfaults. I have gimp 1.1.23 here; I'm updating from CVS at the moment and will try it again after that completes (which will probably be sometime tomorrow). Kelly
Re: Wow! The Resynthesizer
Alex Harford wrote: http://www.csse.monash.edu.au/~pfh/resynthesizer/ I downloaded, read the README, and installed Resynth is nowhere to be found?! HELP! I'm using the latest developer edition of gimp on a RedHat 6.2 box with Helix. (but Gimp is not the Helix gimp, I compiled it) Thanks -- Jon Winters http://www.obscurasite.com/jon/ "Everybody Loves The GIMP!" http://www.gimp.org/
Re: Wow! The Resynthesizer
I downloaded, read the README, and installed Resynth is nowhere to be found?! Should turn up in image/filters/map/resynthesize -James Smaby
