I recently installed GIMP on my new Mac Mini with Sonoma OS and on start up of the machine, I receive this message every time on Terminal:
Last login: Sat Oct 28 09:46:13 on console /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg ; exit; antonycosta@Mac-mini-2023 ~ % /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg ; exit; /Applications/GIMP.app/Contents/Resources/lib/gimp/2.0/plug-ins/file-jpeg/file-jpeg is a GIMP plug-in and must be run by GIMP to be used
Has anyone else had this issue and know what it is? Do you know how to correct it? If anyone knows how I can stop this coming up each time, I would appreciate the information. I ran Gimp on my old machine, also a Mac Mini, but I never had this issue.
My question is, where can I find documentation to this gimp module object, VectorsBezierStroke? I tried a 'help(gimp.VectorsBezierStroke)' command in the console, but the object lacks any '__init__' description as far I can tell. Searching the Gimp Python Documentation page that is online doesn't seen to have any references to this object either.
For speed, I tweak colors on negatives I've scanned at only 600 PPI. Then I need to get the same results on the same negatives, but on images after scanning at 3200 PPI. Is there a way to transfer the results of the adjustments I made on the 600 PPI negatives to the 3200 ones?
The issue: I draw a circle with the circle selection tool and fill it with black. Its layer is placed below the transparent image, behind which it should function as a background.
However, the black lines in the front image suddenly show white, as if some type of layer mode has been applied, which is verified not the case. Again, you would really need to see the video to truly understand this issue.
I'd be most grateful for a solution.
I use PNGs because they are lossless. I know the compression level with JPGs affects the quality but not so with PNG. Is the only disadvantage with using the highest compression (9) with a PNG is that it takes longer to save? What about decompression? If a PNG is saved at 9 does it affect how another program opens the file? If one wants to minimize file size is there any reason other than extra saving time not to use the maximum compression?
Hi, I'm pretty new to gimp plugins, and I wanted to play around with developing some specific plugins for my project. When I run vscode, however, pylance does not detect gimpfu. That's weird, since my interpreter is set to the python version in GIMP's bin. Additionally, the plugins do work when I run them in the application, so gimpfu exists somewhere. But without any familiarity with the documentation, developing kind of feels kinda blind...
Is there any way I can fix or troubleshoot this problem? I'm not sure where to start. I'm trying to see if gimpfu can work in WSL, if that works I can just move the plugins over to Windows. Thanks in advance.
I know how to do a sphere (sphere.png) and a grid (grid.png), but how can I do that (the 2 last pictures). I am new to Gimp, and I don't have any idea how to do it (pic01 and pic02).
I've used GIMP for simple photo work for several years, but I've just encountered a PROBLEM.
When I have opened a photo in the past, a little dialogue says something like: "Drag your cursor to crop image."
This has disappeared, and in its place there is now a tool makes the image to be worked on LARGER... and LARGER - and no selection occurs!
Thinking perhaps my trusty GIMP had developed a glitch, after switching off & on my machine to clear the problem, I deleted GIMP and installed the latest 2.10 version.
But - Same problem. I cannot use my cursor to make a simple selection / crop of the image.
I can no longer open JPG files of any significant size. GIMP just gets stuck in the opening process. Sometimes it shows the image, sometimes not, but no tools respond after it tries to open the image, though quitting the program responds quickly. Opening GIMP by itself still responds in the same time as always, which is about 6 seconds. These are images similar to images I was opening a month or two ago.
I have an older Mac, but it's not so short of resources to be struggling with the size of files that I used to be able to open until recently.
To get some indictions I have opened the dashboard Window to get some info while it tries to open the image, and also had a look at the system Activity Monitor.
If I could just get some hints what else to try! Or to be more pertinent, where to start looking. Log files, temporary files, settings? I'll stop short of percussive maintenance, emoji here.
Here are the details
macbook pro 2016
2.6 GHz Quad Core Intel i7
macOS Monterey 12.6.9
16GB RAM
SSD drive - lots of free space
Graphics: Radeon Pro 2GB GIMP
GIMP 2.10.34 (Revision 3)
Tile cache size: 8GB
All other settings: default Tried so far
update
uninstall, reinstall
uninstall, delete all temp files I could find (BUT there could be some I missed), reinstalled
File 1 that can't open
Filesize: 209kB
Imagesize: 1152x896
Colourprofile: sRGB IEC61966-2.1
8 bits/channel
dpi: 72
Dashboard says while opening (not always the same, after opening image multiple time)
Cache: goes up to 12%
Memory 1%
Cache varies: sometimes 4.4MB, sometimes as high as 10MB.
Activity monitor (I could only assess if opening image from inside GIMP)
CPU goes DOWN to 0 from about 7%
File 2 that opens easily
XCF file with 4 layers
This file was created in GIMP from a JPEG of 1024x1024 a few months on the same computer and it opened immediately at that time.
Colourprofile: GIMP RGB (no alpha channels on any layers)
Filesize: 12.5MB
Canvas size: 1024x1024
Dashboard after opening
I was a little curious about how the opacity indicator value works with the Paintbrush, Bucket Fill tools, among others.
Even the behavior of opacity between layers follows its own logic.
What I'm trying to say is that intuitively when I select, for example, a value of 50 for Paintbrush opacity, I imagine that I am using half the transparency in that stroke and that if I apply a second stroke over the previous stroke I will have 100% of the opacity achieved.
Or that if the Paintbrush / Bucket Fill opacity value of 34 is applied, with 4 reapplications I will obtain 100%.
However, this is not what happens!
Using the opacity value of 50, as an example, it will take 7 reapplications (not just 2) to obtain a 100% opaque color, as I tried to demonstrate in the image below.
In the case of opacity between layers, something similar occurs.
Although the colors always remain at 100% (ok with that) and the first layer with opacity at 50 displays the value of 50.2% for the effective transparency value, just a second layer will not be enough for 100% to be reached.
In fact, in the test I did, setting the layer's opacity to 50, it was necessary to duplicate the first layer eight times (with opacity of 50) - a total of 9 layers, to obtain 100% opacity.
I confess that I often used the paintbrush opacity value of 34 thinking that I was applying 1/3 of the opacity and that if the effect was still weak I could apply a second stroke before reaching the tool's full opacity.
The question is why does it work this way and not in the most intuitive way (50% - restores 100% with 2 strokes, etc.)?
