It is currently Wed Aug 19, 2026 9:04 am


All times are UTC - 5 hours [ DST ]



Post new topic Reply to topic  [ 99 posts ]  Go to page Previous  1, 2, 3, 4, 5
Author Message
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Mon Mar 31, 2014 2:08 pm  (#81) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Ronounours wrote:
Here it is : http://gmic.sourceforge.net/tutorial/_g ... norm.shtml

I need to find a way to group commands by themes, because the list of described command becomes quite large.
Thanks a lot Garry for this hard work you are doing day after day.


Thanks a lot David! Like a jet...

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Mon Mar 31, 2014 6:02 pm  (#82) 
Offline
GimpChat Member
User avatar

Joined: Mar 15, 2014
Posts: 115
Location: Brooklyn, NY
dinasset wrote:
Why this command uses the parameter("isovalue" says the documentation) 1?

'iso' = 'all the same.' Picture a weather map with contour markings called isobars, often encircling regions of low pressure. These lines connect points of equivalent pressure (measured in 'bars' hence 'isobar' == 'points at the same pressure')
With -distance, we ask G'MIC to start measuring the distance of every pixel in an image to the nearest pixel with the designated 'isovalue'. Pixels from the input image which are at the designated isovalue are zero (black) in the output image. All other output pixels are assigned positive values commensurate with the distance the corresponding input pixel is to the nearest isovalue. The lightest parts of the output regions correspond to input pixels furthest from the isovalue. -distance frequently follows images comprised of boolean 0 or 1, so eight times out of ten, probably more, the isovalue given to -distance is 1.

dinasset wrote:
(btw, my guru friends: which number does 1e10 correspond to? in my poor scientific calculator it says 27.1828...but this is certainly wrong, if I replace 1e10 by 27 in the command I get a much more limited sharpening; the result is approximated if I put 270000 instead..)(continues)


Poor calculator. Methinks it took 'e' to mean the transcendental 'e', the base of the natural logarithms, 2.718281828459045..., and multiplied it by ten.

In G'MIC-speak 'e' means 'exponent' and tells the parser to raise the number to the left of it by the power to the right of it, base 10. so '1e10' = '10,000,000,000' As a practical matter, this sets -sharpen off to doing an insane amount of sharpening. ;)

I've made a private copy of '-stained_glass' where this is a settable parameter. The results can be quite lovely with -sharpen given less insane values. I think I am out of Gimp Chat Purgatory now, and can attach images. We'll see if I can find something pretty.

Garry


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 2:03 am  (#83) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Thanks a lot Garry!
Now it's all much clearer for me.
Hope to see the link to your version of -stained_glass.
Curiosity: it's a version of the native command or a version of the gimp-gmic filter? I guess the first one...

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 3:40 am  (#84) 
Offline
GimpChat Member
User avatar

Joined: Mar 15, 2014
Posts: 115
Location: Brooklyn, NY
Native -stained_glass. The documentation engaging me so far is the G'MIC interpreter, which runs outside of Gimp. The premise page is at http://gmic.sourceforge.net/tutorial/index.shtml. For some of the work that I do, invoking the same effect on a lot of images, the standalone G'MIC interpreter is a better fit than the Gimp plugin. I've long felt that the use cases for the standalone interpreter deserve a better airing. In My Own Humble Opinion, of course.

Garry


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 3:55 am  (#85) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
OK, my guess was correct.
In the meantime I tried to apply different values (different from the "extreme"1e10); in effect, I may get nice results ...

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 12:32 pm  (#86) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Tip #18 part 6

let's continue

-neq[-1] 0

After having looked at the results, my interpretation of this command is (G'MIC gurus pls check!):
-every pixel of the image is examined
-every totally black pixel stays as it is (0)
-every non totally black pixel (not equal 0) is set to 1
the resulting image -if option "cut" is selected- looks apparently totally black (values 1 do not show easily!); no grey pixels around; but, if we change the option from "cut" to "normalize", we see a B&W image where all pixels not 0 are now white.
So, if we compare the resulting image (normalised) with the image to which ended up the previous post (image2e), we notice much more white (see image2f)

Attachment:
image2f.png
image2f.png [ 43.02 KiB | Viewed 2249 times ]


-if $3
-skeleton[-1] 0
-endif

this command is applied if the third (boolean) parameter is set to 1 (yes, true, on...).
Again having looked at the result, my interpretation of this command is (G'MIC gurus pls check!):
- every white area bigger than 1x1 pixel in the picture is reduced to inner lines of 1 pixel ("bones" of a skeleton).
At least this is what appears to me by comparing the outcome with the previous image (see image2g).

Attachment:
image2g.png
image2g.png [ 48.68 KiB | Viewed 2249 times ]


But "how" are the "bones" generated? This is a mystery, for me; I tried to do a couple of experiments:
first defining a white star and applying only the -skeleton command; afterwards defining a white circle and applying again only the -skeleton command.
Well, I see the lines ("bones") as being not uniformly generated: look at each of the five points/triangles of the star or at each of the four quarters of the circle: the quarters look uniform among them, but the lines (bones) are not uniform inside a quarter; the points/triangles of the star are not even uniform among them.
So here, it's necessary (for me at least, but also for some of the readers, I guess) to get some nice explanation from a guru.

Attachment:
Test_Skeleton.png
Test_Skeleton.png [ 42.07 KiB | Viewed 2249 times ]


(continues)

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 12:45 pm  (#87) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
(continued)


-distance[-1] 1

we know already this command, we should get an expected result; here it is: image2h

Attachment:
image2h.png
image2h.png [ 100.75 KiB | Viewed 2246 times ]


-watershed[-2] [-1]

watershed is a common word in geography; here it seems to work analogically, in the sense that image2h is taken as a "watershed" profile and is applied to the image we left a few steps ago: image2c; the resulting image can be see here: image2i.

Attachment:
image2i.png
image2i.png [ 146.03 KiB | Viewed 2246 times ]


How really the function performs, is a matter for gurus, I hope to get here (again) a nice explanation

-sub[-2] $im

here the original values -modified by the statement "-add $im" during the initial steps- are restored

-normalize[-1] 0,1

well, what we have always seen in the examples, was a "normalised" image, because I adopted the choice "normalize" in the custom code panel; in the command it must be stated explicitely to get a normalised appearance. Therefore, nothing new has to be shown here.

-pow[-1] $2

the default value for the second parameter is 0.2; by using this "power" (less than 1), all pixel values are drastically reduced, but not linearly: big values are reduced much more than small values; if we take this sequence of pixels:
1, 3, 7, 15, 31, 63, 127, 255 the resulting values once applied the power of 0.2 are respectively:
1, 1.24573094, 1.475773162, 1.718771928, 1.987340755, 2.290172049, 2.634879413, 3.029061117;
What does this mean:
1-if we look at the resulting image using option "cut", we get an almost totally black image
2-if we switch to option "normalize", we get a much more luminous image.
I show here the latter (image2j)


Attachment:
image2j.png
image2j.png [ 115.97 KiB | Viewed 2246 times ]


-mul

the two images ([-2] and [-1]) are multiplied, so that we get the final (single) image.
Look (on the next post, only 3 images per post): image2k

-endlocal
-done
-verbose +

we know already these statements, nothing new.
We came to the end, eventually!
Hopefully, we learned something on coding G'MIC.

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 12:46 pm  (#88) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Attachment:
image2k.png
image2k.png [ 266.63 KiB | Viewed 2246 times ]


final image

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Tue Apr 01, 2014 6:59 pm  (#89) 
Offline
GimpChat Member
User avatar

Joined: Mar 15, 2014
Posts: 115
Location: Brooklyn, NY
-neq[-1] 0 - you've about got it. All the boolean commands behave similarly: Apply a test to an input pixel, write the corresponding output pixel 0 (false) or 1 (true) depending on the outcome of the test.

-skeleton[-1] 0 - if you see how -skeleton is put together in gmic_def.gmic, you'll discover that you have seen it already: it is -distance to zero, and the resultant is -sharpened a fantabulous amount. Then there is a new bit: a copy of the skeleton is made and eroded two pixels, and the eroded copy is subtracted from the uneroded copy. In effect, any field of white is replaced with a hairline perimeter.

-watershed[-2] [-1] Yep. Is inspired by water flowing downhill. Watershed takes a marker image and a 'geography' image. Markers indicate where 'liquid' begins flowing and is usually (not necessarily) a set of points. The color of the liquid stems from the color of the marker. The geography image indicates where the hills are, how steep are their slopes; the geography image determines how liquid will flow. Liquid flows until it hits another flow of liquid (a border appears indicating a barrier separating the two catchments) or until it finds a local minimum.
Roughly the midpoint of some catchment. The process stops when liquid has flowed everywhere, leaving no 'dry' (unmarked) pixel.
Markers are also called 'labels.' Recall your 'J&B' remarks some number of posts ago. -watershed furnishes some context for that mysterious comment.
Good to see you over the finish line. I have enjoyed you unfolding the whole sequence.
Garry


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Wed Apr 02, 2014 2:07 am  (#90) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Thanks, Garry!
I will "study" your explanations, by making also some personal experiment.
Maybe I will ask you some additional help in the next future...
Thanks again for your continuous support

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Wed Apr 02, 2014 2:33 am  (#91) 
Offline
GimpChat Member

Joined: Sep 24, 2012
Posts: 275
Location: Scotland
Your tutorials and explanations are always fantastic Garry, better than the programming related books I have. We're lucky to have you writing about G'MIC :yup


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Wed Apr 02, 2014 6:03 am  (#92) 
Offline
GimpChat Member

Joined: Mar 29, 2014
Posts: 21
I recently downloaded this program because I needed it in a tutorial. Then I found out how good it actually is. I hope to get to know it better in the future


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Wed Apr 02, 2014 7:29 am  (#93) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
@Garry

my first curiosity

Hi Garry,
I come back to you very soon...don't hit me please!
I had a look (as you suggested) to the code implementing the command -skeleton.
From there I took only the first two lines of code plus the fourth one (omitting blur):
-ge 50%
-distance 0
-sharpen 1e10
and put in the "custom code" panel of Gimp-G'mic.
Then, I just created a square image filled in with a gradient red to black.
(BASE)
Attachment:
BASE.png
BASE.png [ 129.42 KiB | Viewed 2524 times ]

Then I run those three lines of code.
As expected, the command -ge 50% cuts the image into two horizontal sections:
the bottom half remains totally black (all those pixels are below the limit of the threshold so none of them is affected by the next commands), the top half is converted into a sequence of many red lines; but they seem to be "drawn" at different horizontal distances among them, and there are also small segments.
Is there a ("simple") understanding of this result for poor users like me?
(GE_50pc)
Attachment:
GE_50pc.png
GE_50pc.png [ 4.01 KiB | Viewed 2524 times ]

But, this is not all!
I tried a different test by changing the limit of the threshold to 0.1%; I thought I would have seen
an upper part 99,9% high having lines similar to the previous ones; surprise!
The lines are multicoloured, very nice but totally unexpected by me, and the part closer to the bottom
0.1% black zone has even a kind of coloured sand, like in a sand-glass.
Is there a simple understanding for me?
(GE_0-1pc)
Attachment:
GE_0-1pc.png
GE_0-1pc.png [ 25.33 KiB | Viewed 2524 times ]

Many thanks in advance.
(note: should I bother you with all these questions, just tell it to me, and I will stop, I can understand you are busy with much more interesting tasks...)

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Wed Apr 02, 2014 5:40 pm  (#94) 
Offline
GimpChat Member
User avatar

Joined: Mar 15, 2014
Posts: 115
Location: Brooklyn, NY
dinasset wrote:
As expected, the command -ge 50% cuts the image into two horizontal sections:
the bottom half remains totally black (all those pixels are below the limit of the threshold so none of them is affected by the next commands), the top half is converted into a sequence of many red lines; but they seem to be "drawn" at different horizontal distances among them, and there are also small segments.
Is there a ("simple") understanding of this result for poor users like me?

-sharpen, as used in -stained_glass, attempts to unblur what has become blurred.
Blurring is like squeezing toothpaste from a tube. Bit treacherous for four year olds, maybe, but they get the hang of it.
Unblurring is like getting the toothpaste back in the tube again.
-sharpen is faced with a task of reconstruction - make sharp again that which has been smeared by blurring. Now, there are all kinds of ways to blur an image. What is more, there are even some ways to unblur an image, but such ways usually depend on knowing what the original blurring method was and also knowing that this method was not destructive. Usually, though, when an image comes from out of the blue, and blurred, we have no idea what mechanism blurred it or whether it was destructive.
So we punt.
-sharpen is a tool with which we punt.
-sharpen embodies two unblurring technique. One is called shock filters, which we haven't been using, the other is called inverse diffusion, which we have.
Inverse diffusion is an interesting technique grounded on the analogy that a warm room with a hot rock used to be a cold room with a red hot rock - but that heat has diffused out, cooling the rock but warming the room.
-sharpen assumes that the sort of white areas in an image were once very white, the sort of dark areas were once very dark, and by implementing a process of inverse diffusion - pushing the hot back to the hot spots and the cold back to the cold - that maybe it can reconstruct the sharp transition edges that used to be betwixt the two.
Like I said, pushing toothpaste back into the tube.
-sharpen does a pretty good job, considering what it is given to go on, which usually isn't much. The amplitude we give -sharpen controls its diligence. Low amplitude means "Awww - just get the main edges and don't sweat the details." -sharpen won't sweat the details. High amplitude means "Don't come back here until you've found ALL the edges, and - I - *DO* - mean - ALL of the edges!!!!" -sharpen will sweat the details.
Even those that aren't there.
OK. That's -sharpen. Plus a little bit on how to make it manic-depressive.
dinasset wrote:
surprise!
The lines are multicoloured, very nice but totally unexpected by me, and the part closer to the bottom
0.1% black zone has even a kind of coloured sand, like in a sand-glass.
Is there a simple understanding for me?

Now there's -distance, which also has to sometimes do two impossibilities before breakfast. -distance has to find the Euclidean distance of a pixel from the nearest reference pixel endowed with a particular intensity level - usually one or zero.
Seems straightforward. In fact, that's the first impossibility.
Euclidean distances are found with Pythagoreas' Formula: the beast which rubbed the ancient Greek noses into the smelly business of incommensurability. That there are numbers which cannot be represented as integral ratios sounded the death knell of arithmos - the echoes of which still sound in the English language today: rational. Nice sane ratios of integers. In terms of computer store, they take only what they need. How polite. Irrational - darn crazy numbers like the square root of two which cannot be precisely expressed unless one has an infinite store of memory handy. So, as often as not, -distance paints intensities which aren't quite right, because it has maybe sixty four, maybe one hundred twenty eight bits of storage, which can never be enough for the idiotic irrationals. That's the first impossibility. The second impossibility is that the distance, so figured or mis-figured, is for a point, dimensionless, infinity small, but a pixel has area and dimensions, so exactly to what does the distance refer? The middle of the pixel? One of the corners? No matter how you call it, the distance is going to be slightly not right for all but one point in the pixel, and it is probably not right for that either.
But -distance is a trooper. As best as it can, it paints a gradient of grays that (more or less) approximate how far pixels are from the benchmarks, suffused through the work, however, is an error pattern.
Now, along comes -sharpen (remember -sharpen?), to which Ronounours has handed an amplitude parameter of 1e10, for cat's sake, 10,000,000,000, alas, and not 27.128, and it's desperately insane about finding edges. Even ones that aren't there. -sharpen latches onto the diffuse error pattern that -distance has dribbled throughout the gradient and exclaims "Hell-on, these are edges or I'm not Harry!" and proceeds to sharpen them out as only a sharpener beset with an amplitude of 10,000,000,000 can. And that, dear dinasset, is what you are looking at - a faint error pattern left by -distance, which -sharpen has pulled from the murk.
And - as an aside - there is a certain sweetness to the thought that what is a bit of annoyance in the realm of computation can be a thing of beauty in artistic hands. So we don't have arithmos -- we never, ever, really had arithmos -- but there are compensations. Just need to know where to look for them.
Hope this helps.

Garry


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Thu Apr 03, 2014 3:59 am  (#95) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Thanks Garry.
By reading your detailed description of the functions, I ended up with the conviction of having entered a dangerous field, for my low-level mathematical mind.
BUT, because I am also "pigheaded" (I hope to have found the correct translation in English of the Italian word "cocciuto"), I restarted my thinking process and I said to myself:
1-I just wanted to know why the resulting lines were not uniform, as I was expecting
2-I read about the complexity of the used functions
3-I know that mathematics "is not an opinion" (as we say here in Italy)
4-thus, whatever the complexity of the function, with same input I must get same result
5-I tought to have a uniform input, with each pixel varying down from red to black uniformly
6-I wanted to verify this assumption
7-MY ASSUMPTION WAS WRONG! filling a big area with a gradient in Gimp is not leading to a set of uniformely distributed values (at least using my hand)
8-thus, I prepared an area large only ONE pixel (still with a height of 500 pixels)
9-I filled it with the gradient red to black
10-I scaled the image to 500x500
11-NOW I had a uniformely gradient area!
12-I performed again the test and I got .... a gradient area also as a result, without any line.
13-which is also correct for my low-level mathematical mind: THERE WERE NO EDGES TO DETECT!
So, your detailed info was helping myself in going deeper into my thoughts, thanks a lot!

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Thu Apr 03, 2014 12:10 pm  (#96) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Tip #19

After having analysed some nice ways of using G'MIC commands in a filter, why not to take advantage of some of those brilliant ideas we found in there and create an own filter?
For instance, I liked the part related to the steps to enhance the overall colours/contrast of the input base image in the gimp_stained_glass filter, just discussed in details during the last days, with also the excellent support/contribution of the gurus, on the way on.
So, just to start, I extracted only that part from the filter and build a new simple filter: gimp_enh_col.
Yes, I know there are excellent filters already in the rich treasure of G'MIC, but maybe someone -among the readers of this post- would like to try writing a personal filter.
So I decided do put here an example of such a "by-product" of our readings.

#@gimp Enhance colours : gimp_enh_col, gimp_enh_col_preview(0)
#@gimp : Equalize = bool(1)
#@gimp : Colors = float(1,0,3)
#@gimp : Gamma = float(0,-1.2,1.2)
#@gimp : Contrast = float(1,0,4)
#@gimp : Brightness = float(0,-255,255)
#@gimp : Sep = separator(), Preview type = choice("Full","Forward horizontal","Forward vertical","Backward horizontal","Backward vertical","Duplicate horizontal","Duplicate vertical")
#@gimp : Sep = separator(), note = note("<small>Author: <i>just me as a thief;</i>.      Latest update: <i>2014/04/04</i>.</small>")
gimp_enh_col :
  -repeat @#
    -local[$>]
      -split_opacity      #separate colors from opacity
     -local[0]            #work only on colors
        -if $1
         -equalize[-1]
       -endif
        -rgb2lab[-1]
       -shared[-1] 1,2
       -mul[-1] $2
       -remove[-1]
       -lab2rgb[-1]
        -apply_gamma[-1] {10^$3}
       -sub[-1] 128
       -mul[-1] $4
       -add[-1] {128+$5}
        -cut[-1] 0,255
      -endlocal
      -append c
    -endlocal
  -done

gimp_enh_col_preview :
  -gimp_split_preview "-gimp_enh_col $*",$-1


If you like to, take it, copy it in your "gmic" file (which is under user/AppData/Roaming), modify it, play with it.
Note: if you do not have yet a "gmic" file, remember -when creating it copying this piece of code- to put as the first line something like
#@gimp My Directory
and, at the very end
#@gimp _

As an example, I took one of my old photos, not very nice as you can see,
Attachment:
Fuji_20041019_Image007.JPG
Fuji_20041019_Image007.JPG [ 524.47 KiB | Viewed 2472 times ]

and tried to improve it a little bit.
Attachment:
Fuji_20041019_Image007_after-filter.JPG
Fuji_20041019_Image007_after-filter.JPG [ 765.56 KiB | Viewed 2472 times ]

I run the filter with these parameters:
1 (equalize), 1.3 (colors), -0.3 (gamma), 0.88 (contrast), 0 (brightness)

Enjoy..

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Sat Apr 05, 2014 11:38 am  (#97) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
Tip #20

Today let's take advantage of other brilliant ideas we found by analysing existing filters, and create another own filter.
Very simple, still trying to improve the overall appearance of a photo.
We may call this new simple filter: gimp_enh_photo.
We make use of the command -orientation and again of the -apply_gamma.
Here is the code:
#@gimp Enhance photo : gimp_enh_photo, gimp_enh_photo_preview(0)
#@gimp : Gamma centre = float(100,31,223)
#@gimp : Sep = separator(), Preview type = choice("Full","Forward horizontal","Forward vertical","Backward horizontal","Backward vertical","Duplicate horizontal","Duplicate vertical")
#@gimp : Sep = separator(), note = note("<small>Author: <i>just me as a thief;</i>.      Latest update: <i>2014/04/05</i>.</small>")
gimp_enh_photo :
  -repeat @#
    -local[$>]
      --orientation
      -normalize 0,255
      -blend overlay
      power={-(ia-$1)/255}
      -apply_gamma 10^{$power}
      -normalize 0,255
    -endlocal
  -done

gimp_enh_photo_preview :
  -gimp_split_preview "-gimp_enh_photo $*",$-1


With the command --orientation we create a additional image which shows nice nuances of the colours of the image.
The output of this command has to be normalised.
Then we blend this new image with the base image, applying the overlay mode.
Now we want to take care a little bit of the overall gamma of the image.
Maybe it's too dark, maybe it's too bright.
So, we apply a gamma correction assuming a "normal" average value of 100.
If the average value is greater than 100, the image is probably too light.
If the average value is less than 100, the image is probably too dark.
We use the formula {-(ia-$1)/255} to calculate the power used in the -apply_gamma command.
The power takes a value inside the range -1 and 1.
A positive value will determine a brighter image.
A negative value will determine a darker value.
I applied this new little filter to two different base images: dark_base and light_base.
The light_base is the same of the last post (tip #19), so it's not attached again.
You may see the resulting images.
Try yourself, if you like, with some of your images.

Attachment:
dark_base.JPG
dark_base.JPG [ 1.01 MiB | Viewed 2440 times ]

Attachment:
bright_base_afterfilter.JPG
bright_base_afterfilter.JPG [ 678.58 KiB | Viewed 2440 times ]

Attachment:
dark_base_afterfilter.JPG
dark_base_afterfilter.JPG [ 938.93 KiB | Viewed 2440 times ]

_________________
"Where am I ?"


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Sat Apr 05, 2014 12:09 pm  (#98) 
Offline
GimpChat Member
User avatar

Joined: Nov 16, 2011
Posts: 5127
Location: Metro Vancouver, BC
dinasset, I admire your curiosity with G'MIC and interaction with David and Garry, you're posts remind me of Fred's ImageMagick Tidbits.

_________________
Image
Gimp 2.8.18, Linux, median user
Gimp Chat Tutorials Index
Spirit Bear (Kermode)


Top
 Post subject: Re: G'MIC - tips and curiosities
PostPosted: Sat Apr 05, 2014 12:41 pm  (#99) 
Offline
GimpChat Member
User avatar

Joined: Jan 20, 2013
Posts: 14831
Location: roma, italy
thanks for your nice words!
I didn't play with ImageMagick, if I'm not wrong it's primarily a command line software; also G'MIC is, natively, a command line software but it's now interfaced by Gimp, so I can play with it! (still with a lot of difficulties, because of its high level base of knowledge, but there are around some helping gurus...)
thanks again

_________________
"Where am I ?"


Top
Post new topic Reply to topic  [ 99 posts ]  Go to page Previous  1, 2, 3, 4, 5

All times are UTC - 5 hours [ DST ]



* Login  



Powered by phpBB3 © phpBB Group