Just started using Gimp 2.8 on my new MAC.  Had a problem with no text showing up on my project even though I could type in text box.  I could see a mini micro of something happening at the top of the text box but no text appearing.  Searched the net and checked to make sure I was using RGB and checked canvas size, layer position etc etc.  Finally, double clicked on the text tool and found out that the default setting for text size was PIXELS and not POINTS. Pretty darn hard to see your text when it is 24 pixels and not points Changed to POINTS and everything now well.  Just thought I would give a heads up in case anyone else is having problems using the test tool.  Developers should be notified of this default setting and have it changed to points for text size.

GIMP 2.10.4 In order to display the PSD file correctly, the "Merge" function is activated! 
But how should I show all the layers? 

I'm writing a fairly technical doc where a concept of "layers" is heavily involved. So to make schemas easily I wrote a script that transforms a flat stack of layers in Gimp into the 3D stacked image:

   

   

Hey,

I'm a returning Gimp user and I'm trying to access the gimp plugin registry, but it seems to be down or something: it isn't responding.
Did the website change? I'm trying to get the layer effects plugin and I can't find a download link from any other website...

Link: http://registry.gimp.org/glossary/g

Edit: oops, just realized this is in the wrong section, sorry

So I installed the latest gimp earlier and I cant stand it, What happened to these?

Hello all,

I'm attempting to edit an animated Gif file.  This one to be exact:



I want to remove everything prior to when Kreiger says "me too!".  But, every time I delete the frames prior to that, the image gets fuzzy.

This is the end result:


I'm not sure what I did wrong, or how to fix it.  Does anyone have any experience with editing Animated GIF files?  If so, do you know what I did wrong?

Hi folks,

I am following the instructions on https://gitlab.com/CrazyBaboon/GIMP-git_...git-Fedora , and the compilation on my Fedora GNOME desktop was successful until last week.Since then I have been getting a

Error: missing dependency appstream-glib >= 0.7.7

when I compile try to compile Gimp.

The compilation process was fine for the other libraries such as babl and gegl.

I have libappstream-glib-0.7.9-1.fc28.x86_64 and libappstream-glib-builder-devel-0.7.9-1.fc28.x86_64 installed already, so I have no idea on what to do. Any advice?


Thanks!

(04-15-2017, 09:20 AM)rich2005 Wrote: The link between a brush folder name and the Gimp Brushes Dialogue. The folder name is used as a brush tag.
Type a tag in at the top of the brushes dialogue and that will isolate the brushes in that section.

Quote:Fonts Tagging
Michael Natterer introduced some internal changes to make fonts taggable. The user interface is the same as for brushes, patterns, and gradients.

GIMP doesn’t yet automatically generate any tags from fonts metadata, but this is something we keep on our radar. Ideas and, better yet, patches are welcome!

https://www.youtube.com/watch?v=ZEVxoCpTPw4


In the video link above, I demonstrate a glitch I've found with the selection tools.

The first canvas is a 1920x1080 px canvas, which works perfectly fine. I then open a 17x11 in. canvas (for some reason the file menu doesn't show up on the recording), and I get this weird blacking out effect when I try and use the selection tools. 

This happens on any canvas besides the default 1920x1080 px canvas. Does anyone have any suggestions on how to fix this?

I have a camera who's color profile is called sRGB and Gimp has its own color profile called sRGB. When I load a picture from my camera into Gimp, it asks me to keep or convert. Depending on which I pick (keep original sRGB color profile, or convert to Gimp's sRGB) the image DOES LOOK DIFFERENT. This tells me that the color profiles are not identical. I thought sRGB was the name of an international standard for converting linear values (as recorded by your camera's image sensor) into perceptual values (the values between 0 and 255 are proportional to the human eye's perception of brightness), in much the same way that things like USB is a standard (in this case a standard protocol for communication between a computer and a peripheral). So therefore anything using sRGB should be precisely compatible with anything else using sRGB, meaning that "keep" and "convert" should be exactly identical operations in this case. But clearly that's not what's happening.

Can anybody here explain why this is happening?