Release of G'MIC 2.1.3

This is the changelog for the release of a new minor version (numbered 2.1.3) of the G’MIC image processing framework. This new stable version stays backward compatible with the previous version 2.1.1.
Few improvements on the language syntax and script parser have been done.

What is G’MIC?

G’MIC (GREYC’s Magic for Image Computing) is a full-featured open-source framework for image processing. It provides several different user interfaces to convert/manipulate/filter/visualize generic image datasets, ranging from 1d scalar signals to 3d+t sequences of multi-spectral volumetric images, thus including 2d color images.

The following is the full Changelog of the version 2.1.3, as compared to the previous stable version 2.1.1.
Enjoy !

New features:

  • New syntax $$name or $${name} allowed, substituted by the G’MIC script code of the custom command name. This allows to save and restore the definition of a command in/from a variable for instance.

  • Hanoi tower game has been added, with command x_hanoi. The game now appears in the main demos menu.


Changes / Improvements:

  • Syntax extension: Invoking a command with a double hyphen --command can be now equivalently written with a +, as in +command.

  • Math parser function date(attr,_filename) now accepts a vector-valued argument attr, to retrieve multiple date info at the same time (e.g. day/month/year).


I may have done something wrong but:

gmic sp tiger gcd_infomap 0

[gmic]-0./ Start G'MIC interpreter.
[gmic]-1./ Input sample image 'tiger' (1 image 512x512x1x3).
[gmic]-1./ Input file 'gcd_infomap' at position 1
[gmic]-1./ *** Error *** Unknown command or filename 'gcd_infomap'.

Command is from gmic-community/andy_kelday.gmic at master · dtschump/gmic-community · GitHub.

Works for me. Try $ gmic update to be sure you get the update213.gmic file downloaded into your $HOME/.config/gmic§ folder.

Ha ha, I am so forgetful. Just updated to G’MIC 2.1.3 because I like +.

1 Like

I noticed another problem. Try

gmic sen_4.gmz p n 0,255 p o _.jpg o _.cimg && gmic _.jpg _.cimg p

Cropped image: (46.7 MB). Max value in the JPG isn’t 255 (it is 204) but for CIMG it is.

My quick guess: JPEG being a lossy compression format, it doesn’t ensure your min/max values are maintained in the output file.

PS :Try the same with a .png instead of a .jpg and you’ll get [0,255] as well.

Here is more info. I converted CIMG to TIFF for easier comparison.

gmic sen_4.tif p n 0,255 p o _.jpg && gmic _.jpg # max0 = 209.739; max1 = 255

magick sen_4.tif -auto-level -quality 100% dst.jpg

gmic _.jpg dst.jpg p # max2 = 204; max3 = 253

Well, this doesn’t change anything in that case.
JPEG compression introduces lossy artefacts in generated files, changing the min/max values of the pixels, that’s why you don’t get a [0,255] range when you read the JPEG file again.

That is fine. I just never noticed this before. I meant to confirm that it happens in IM as well :slight_smile:.

Hey, David. Any plans for G’MIC to support sound? The reason I ask is I like the Ms. Pacman demo, but it would be better to have sound too. lol


1 Like

I thought about it yes some times ago, but this would mean add another dependency to a sound playing library. And for an image processing tool, it’s probably a bit too much :slight_smile:

I know; still had to ask. lol


@lylejk Maybe if you have the programming chops, you could link a music / sound library to gmic and then, with some magic sauce, we can procedurally generate music and images :wink:.

David already knows this, but coder I’m not. lol

Now you know too. :wink: