Hi Rod,

From the video I noticed that the foreground extraction tool never activates. This is a memory issue since it is quite memory intensive. My guess is that you do not have enough memory on your computer.

Thanks,
Partha

PS: I just ran on an XP with 1.25Gig RAM and I got the same result as you, so definitely a memory problem. With 4Gig of RAM, it works fine. Sorry Rod.

almost exactly what i get..except i don't get a new layer, when i hit enter i get selection around my first outline
really no differnt then when i try it in the install version..got to be something i'm doing wrong


couple of errors when starting portable

Yes that is exactly what it is Partha.Not enough memory...darn. :\

alc59,

The RGGJAN portable seems to be temperamental and giving you an error as well. Did you run it on a Windows 7 machine with enough RAM (4 or more)?

Thanks for the feedback on the crash. The texturetiler plugin seems to be the problem for you. Sharpfeather is part of that plugin. I will look into why you are getting this error. In the meantime, I am afraid you will have to delete them both from the plug-ins directory. The script patchsynth.scm will not work either.

Are you having any other problems using the portable version? Which Windows are you running and is it 32 or 64-bit please?

Thanks,
Partha

win 7 64 bit 4 gig ram

haven't played with the portable much yet
i don't think mines activating either. it doesn't open a new layer and only selects my first trace

Yes i will be upgrading to 4 or more gigs i think.

Should i have downloaded the 64 bit portable or shouldn't that matter. my other gimps are 32

It is probable that the RGGJAN tweak is in a very experimenthal stage:
For gimp there was a very similar SOC project , that from the video seems ready, and for sure was more know and more tested
Still the gimp staff will wait gimp-2.10 to add to gimp not only to have time to test it better but also to be sure that it will not break something else

Now ,even if sometimes they may seems overcautious gimp developers usually knows what they do ,...a experimenthal fork that had apparently nobody working on it from long adapted to a experimental build may well have bugs and even cause apparently unrelated bugs...

Even more considering not only the iteration with a beta version of gimp , but including also the iterations with several gimp extra plugins ,in this case resurrected from the times of gimp -1.2 ( i still think that resurretion a good idea, and i haven't problem with them

I mean combining 3 factors or risk may be a exponential grow of the chances of something going wrong

BTW..quoting myself
"including also the iterations with several gimp extra plugins ,in this case resurrected from the times of gimp -1.2"
( i still think that resurretion a good idea, and i had not problem with them
...but here we are talking about use them from a experimenthal gimp fork, ported to a beta version of gimp...i believe too much risky factors togheter

@ Alc59

it depend from your Ram, if less then 3GB make no difference... if more is better use the 64 bit version
i will suggest the 64 bit portable of THIS viewtopic.php?f=7&t=2606

i mean gimp-2.7.4 is a beta and so could be unstable and a bit buggy, ... but then this RGGJAN fork may be a pre-alpha

just restarted the laptop and tried to run portable and wouldn't start..i did remove the two plugins that were giving me errors the first time

alc59,

You probably have DLL clashes given what you have said. The portable will not interact with the system, but Windows will still try to load DLLs from the system's directory before anything else.

Can you try to run the 64-bit and see what happens. Also, best not to mix and match.

Thanks,
Partha

I will try the 64 tomorrow
it's a mess alright..i have 2.6.11 2.7.3 and 2.7.4 on here

thanks for all your help/work
Andy

Andy,

If you have been using my 2.7.3 builds, you can uninstall and install the current version. Also, if you have plug-ins in your .gimp-2.7 directory then they can interfere. Of course, this will not affect the portable version which you are free to use without uninstalling anything.

Let me know if you have issues after you try tomorrow and we can try to fix them.

Thanks,
Partha

@Partha & Alc59

Just to stress a point i would add with huge letters a big warning:
If you already had Gimp and/or you wish to use more then 1 version of gimp on the same computer
USE ALWAYS AND ONLY THE (also)PORTABLE BUILDS

I had 10 installed on mine at one time all working. - that included Gimp-Photo, and Gimp-Shop.
Not anymore though.
Now i have only -
Gimp-1.2 - installed
Gimp-2.6.11 - installed
Gimp Portable 2.6 - portable revised (with Python, and PSPI) version
Gimp-2.7.4 - install version
Gimp Adaptable - installed

I have the Gimp-2.7.3 with the new Foreground Select tool but it needs a lot of RAM (4 gigs min) to work.

Why would you want so many Rod? I have a hard time keeping two in scripts and plug-ins?

honestly i don't like forks in project as Gimp , not at all !

May be exception for fork that may be easily merged back ...but in case are not really fork.

I like a lot Gimpainter even more if combined with GPS (Gimp Paint Studio) but i do not consider Gimpainter a fork
(as i believe its developer ).

Actually in the gimp git a lateral branch host something very similar to the RGGJAN selection tool ;
a similar but i believe more mature and stable project that from what i heard risk to be merged not before 2.10,

The same for the future replacement of Iwarp that should become a tool with a real-time preview applied to the image

I believe compiling one of those branch would be more rewarding than support a not manteined fork,
 ..and who know may even help to speed up the testing needed to merge in the standard version of gimp.

 I hope my distinction between fork and branch will not sound pedantic:
the first subtract attention,users and energy from the original project,
the second may even help to speed up the integration of new feautures developed in lateral branch...
for me is not a little difference

PC,

Are you thinking about the seamless clone branch? Rod told me about that one.

Thanks,
Partha

that is one, the branch is “soc-2011-seamless-clone2” and..did you saw the video ?



here same more detail
http://www.google-melange.com/gsoc/proj ... yname/6001

BUT there is more ... the cage transform tool aka the new IWarp (that is more or less the equivalent of PS Liquify )



here show some problem but that should be fixed now



BUT i am not sure how much is ready for a pratical use...sure seems cool BUT all video show the effect on something or on a transparent BG or on a solid white BG as here



No video show how would work on a selected object on a normal BG ...

OOPSS no i am wrong here you may see applied on a chessboard
http://libregraphicsworld.org/news.php?readmore=826

and here some more info

http://libregraphicsworld.org/news.php?readmore=753
http://libregraphicsworld.org/news.php?readmore=616

BUT when i was digging information on tools still under development , maybe not yet ready for pratical use..
i was so lucky to stumble on something ready already well tested and kept in sync with last gimp from git..

YUP ...here GimPainter git ..should be build on Gimp-2.7.4
http://git.sourceforge.jp/view?p=gimp-p ... ;a=summary

Even more info and details HERE
http://libregraphicsworld.org/news.php?readmore=675