[Plugin] ImageTrimmer
-
This is just overwhelming. I was wanting this feature for so long... thank you TIG for making this happen!
As I understand the prcedure, the way to trace a silhouette is to make an inverted transparency for it. With Flatten and Cleanup I get a nice result. Sadly I did'nt get Simplify Contours to work, maybe wrong angle?
( )
-
Very cool, TIG. Thank you.
-
Astonished package!
-
Out of the Blue!
Thank you! -
That is great for png trees shadows. Thank you.
-
This is great! It's been asked for for such a long time.
How about an option to simply the edges - make the resulting silhouette simpler?You can use the Douglas-Peucker algorithm port I used in Edge Tools:
http://forums.sketchucation.com/viewtopic.php?f=323&t=24593#p210736 -
@thomthom said:
This is great! It's been asked for for such a long time.
How about an option to simply the edges - make the resulting silhouette simpler?
You can use the Douglas-Peucker algorithm port I used in Edge Tools:
http://forums.sketchucation.com/viewtopic.php?f=323&t=24593#p210736Thanks for the tip... At the moment it slavishly follows every pixel!
This is only v1.0 so I'm sure there are lots of improvements possible.
My use of using one function specific small Java .jar executables reading 'ini' files to pass arguments etc seems to work better than I expected... So far in alphabetical order, there's...
Bumpmapper.jar and BumpmapperInverted.jar to make gray-scale bumpmap pngs from imagefiles.
EdgeDetector.jar that finds a given png's edges and makes the 'edged' version and a .dat file = 01's used by SUp.
Gifxtractor.jar that makes pngs of all frames in a given animated gif file.
Thumbnailer.jar that makes a 64x64 thumbnail of an image.
ThumbnailerRGB.jar that makes a 64x64 thumbnail of a color from its RGB values.
UnZipDirectory.jar that uncompresses zip files OR skm files.
ZipDirectory.jar that compresses zip files OR skm files in a given folder.
Any ideas for other similar 'jar' tools always welcomed - I only taught myself Java in the last week or two, specifically to do image manipulation parallel to Ruby, but I'm sure there are other possible uses too...
-
You've made a great deal of tools there. Too bad my apartment is such a mess still - don't get much time to look at all these new goodies.
-
With that .jar business I resign right away. just want to put another +1 here: simplifying edges? Oh yes please! (drooling)
-
I had dallied with some outline simplification ideas... but brought v1.0 to market without that functionality as my brain hurt.
I'll think about it again - e.g. even a simple square hole 32x32 pixels currently has 128 edges when 4 would do!!
A square hole on the diagonal has 256 edges when 4 would do!!!
I'm sure I can clone some ideas from others' code
-
@tig said:
I'll think about it again - e.g. even a simple square hole 32x32 pixels currently has 128 edges when 4 would do!!
A square hole on the diagonal has 256 edges when 4 would do!!!
I'm sure I can clone some ideas from others' code With the simplification algorithm I linked to, then those 128 edges should become 4. You feed it a set of points that form a curve (for separate each curve into sets and you get a simplified set.
-
speechlessly amazing!
-
Here's v1.1 http://forums.sketchucation.com/viewtopic.php?p=294815#p294815
It's got an 'outline simplifier' option added.
This is also available a separate tool to simplify the outlines of existing ImageTrimmed components.
See the notes for details...
[Thanks to ThomThom and Douglas-Peucker fro the simplification algorithm ideas...] -
@cadfather said:
not sure what happened but when run, the script opened edge 'detector.jar' file and there it stayed..
it opened with winrar so will check this outYou need to have Java enabled on you computer - it usually is...
Did you extract most files into SKMtools subfolder as the instructions...
The script doesn't open 'EdgeDector.jar' - rather it should 'execute' it as it's a very small app that does just one thing ?
What OS system are you using ? XP ??
What version of IE do you have ?
What version of SUp ? I guess NOT 9.1
-
not sure what happened but when run, the script opened edge 'detector.jar' file and there it stayed..
it opened with winrar so will check this outEDIT: yes if winrar (i guess any other zipping app as well) is set to open jar files too - trimmer will run winrar -- uncheking the file association makes trimmer work fine
-
well TIG, with the likes of you, it feels like SU 10.2!
-
Thanks for the interesting plugin and the inspiration TIG!
@tig said:
I only taught myself Java in the last week or two
Two weeks is not that much. I will give it a try!
-
CADfather
I have looked at your '.jar' issue... I can reproduce it! IF I let a 'zip/unzip' application like AlZip or WinRar 'poach' the '.jar' file-type as one that it will open. If so then when Ruby tries to 'open' a '.jar' file instead of it 'executing' in Java [like it should], it 'opens' in the decompression application...
The solution = look at your WinRar settings and ensure '.jar' is NOT one of its file-types for opening...
-
thanks TIG, that's exactly what i did - (perhaps wasn't too clear in the edit)
one specu-question: could you, adjust the sampling rate/area of the script? suppose you didn't want so much precision, it could perhaps speed up the trimming process - having said that, the simplifier is well integrated
once the trim is achieved -
@cadfather said:
thanks TIG, that's exactly what i did - (perhaps wasn't too clear in the edit)
one specu-question: could you, adjust the sampling rate/area of the script? suppose you didn't want so much precision, it could perhaps speed up the trimming process - having said that, the simplifier is well integrated
once the trim is achievedSorry - didn't see the 'edit' !
It first has to 'get' all of the edges of the solid/transparent areas - it's 'easier' to draw all of the edges as boundaries to these pixels - this is the most complex outline - a Factor 2 simplification will often improve the steppiness of these edges, BUT it can trim small solid areas or leave small transparent areas... Most of the time in the initial processing is finding which edge bits get faces or 'holes' and of course therefore which are part of which 'loops'... The 'simplifier' works on the face perimeter loops once they are made - it's much easier than trying to decide which edges could be the loops initially... You will have seen that the simplifier at Factor 2 reprocesses the faces' loops quite quickly... I can see how to easily recast the code to allow simplification before processing
Advertisement