Gimp 2.10.10 released(gimp.org)
gimp.org
Gimp 2.10.10 released
https://www.gimp.org/news/2019/04/07/gimp-2-10-10-released/
44 comments
Gimp is a fantastic tool for developers. It does well the tasks that can be automated or thought about in terms of algorithms (rotate all images, resize, stretch levels to 0-255, etc.). Great product! Kudos to its developers.
It is, however, a lame duck to photographers (and I think many other artists) when compared with Photoshop. Those who want a visual interface to drag sliders around, instanly see how things would look and edit based on tight coupling with that visual perception still choose Photoshop. I have seen many, many artists try Gimp only to go back. Maybe Gimp does not need to be that tool for artists, but if it does its developer community needs to be more engaged with photography crowd.
As a data point: current Adobe licensing model is almost universally hated. If there were a viable option many users would migrate. I would (and I am just a hobbyist). And it is not for lack of trying -- they do try Gimp (and Liminar, and Affinity and such). But the fact that they curse Adobe but still use Photoshop tells you a lot about the fact that Gimp just does not cut it for them. My 2c.
It is, however, a lame duck to photographers (and I think many other artists) when compared with Photoshop. Those who want a visual interface to drag sliders around, instanly see how things would look and edit based on tight coupling with that visual perception still choose Photoshop. I have seen many, many artists try Gimp only to go back. Maybe Gimp does not need to be that tool for artists, but if it does its developer community needs to be more engaged with photography crowd.
As a data point: current Adobe licensing model is almost universally hated. If there were a viable option many users would migrate. I would (and I am just a hobbyist). And it is not for lack of trying -- they do try Gimp (and Liminar, and Affinity and such). But the fact that they curse Adobe but still use Photoshop tells you a lot about the fact that Gimp just does not cut it for them. My 2c.
As an anecdotal counterpoint, I'm a dedicated amateur photographer [1] who works entirely on a Debian stack (Darktable/GIMP). I've been occasionally curious about Lightroom/Photoshop's capabilities, but have never felt that I was lacking anything so grievous as to consider a switch.
Furthermore, I'd have to run an entirely different OS from the one I've been using since 2002, and lash myself to a licensing model that would be both crippling and expensive.
From my perspective, Adobe's tools do have remarkable capabilities and substantial support. The improved content-aware fill is remarkable, but I never need it. Adobe's close relationships with camera manufacturers (and large developer team) ensures that new cameras and lenses are supported almost at release. Lensfun and Darktable do a great job of keeping up with new hardware, but it often takes at least a few months for new cameras to be supported.
I buy slightly-older hardware, and I check for Darktable compatibility before purchase/rental. (The GFX50R isn't yet on my radar screen in part for this reason[2], though support is clearly on the way[3].)
[1] https://www.charliehagedorn.photography/ https://www.instagram.com/charliehagedorn/
[2] https://www.darktable.org/resources/camera-support/
[3] https://github.com/darktable-org/rawspeed/pull/161
Furthermore, I'd have to run an entirely different OS from the one I've been using since 2002, and lash myself to a licensing model that would be both crippling and expensive.
From my perspective, Adobe's tools do have remarkable capabilities and substantial support. The improved content-aware fill is remarkable, but I never need it. Adobe's close relationships with camera manufacturers (and large developer team) ensures that new cameras and lenses are supported almost at release. Lensfun and Darktable do a great job of keeping up with new hardware, but it often takes at least a few months for new cameras to be supported.
I buy slightly-older hardware, and I check for Darktable compatibility before purchase/rental. (The GFX50R isn't yet on my radar screen in part for this reason[2], though support is clearly on the way[3].)
[1] https://www.charliehagedorn.photography/ https://www.instagram.com/charliehagedorn/
[2] https://www.darktable.org/resources/camera-support/
[3] https://github.com/darktable-org/rawspeed/pull/161
I'm going to chime in my agreement here. I shoot film, develop at home, print in my darkroom, then scan my negatives if I ever want to share them digitally (rare-ish since the whole point of shooting film for me is to get off the computer, but like to share sometimes).
I ran Linux as a desktop for ~10 years and have just switched to OS X, but pulled in GIMP/Darktable/VueScan workflow even though I have access to the Adobe suite. I found GIMP lacking nothing granted I basically just replicate my darkroom process on the negatives when I scan them if I plan to share them digitally (dodge, burn, contrast).
I'm sure there are some advanced layering and other workflows, but I'm not really interested in doing anything I can't replicate in the darkroom. Plus as I said the entire point here is to use the computer less, but still derive joy from an old hobby.
Edit: Also, really enjoying your IG feed. Great work in your color palettes and in the tones across your black and whites as well. May be my love for the Hasselblads and 6x6 frames, but most of those work really well as straight squares as well. Nice to see another PNW photographer on here.
I ran Linux as a desktop for ~10 years and have just switched to OS X, but pulled in GIMP/Darktable/VueScan workflow even though I have access to the Adobe suite. I found GIMP lacking nothing granted I basically just replicate my darkroom process on the negatives when I scan them if I plan to share them digitally (dodge, burn, contrast).
I'm sure there are some advanced layering and other workflows, but I'm not really interested in doing anything I can't replicate in the darkroom. Plus as I said the entire point here is to use the computer less, but still derive joy from an old hobby.
Edit: Also, really enjoying your IG feed. Great work in your color palettes and in the tones across your black and whites as well. May be my love for the Hasselblads and 6x6 frames, but most of those work really well as straight squares as well. Nice to see another PNW photographer on here.
Thanks! -- I've not yet spent a lot of time making square images, but perhaps I'll give it a try someday. If IG were horizontal, I'd probably be working that way :); I primarily use the vertical 1.25:1 because it lets me fill the screen for the reader.
> Those who want a visual interface to drag sliders around, instanly see how things would look
Oh, do you by any chance mean on-canvas preview available for almost every filter since GIMP 2.10.0 released a year ago? With that split preview slider? :)
Oh, do you by any chance mean on-canvas preview available for almost every filter since GIMP 2.10.0 released a year ago? With that split preview slider? :)
I agree. I used to be a professional photographer and videographer. I switched jobs, but I still keep my gear around. One piece of virtual gear that I don't keep around is anything Adobe. Whereas before, I could buy an actual product and use it when I need it, now it would have to become a subscription I constantly turn on and off when I want to do a small, sometimes pro-bono, photo or video shoot.
Affinity Photo is a pretty good alternative. Familiar interface and features, and a one-time affordable purchase. Not entirely sure what an equivalent might be for video.
Affinity Photo is a pretty good alternative. Familiar interface and features, and a one-time affordable purchase. Not entirely sure what an equivalent might be for video.
I still use Photoshop and Illustrator (because for my money there's nothing comparable, and I'll pay for them because of it) but for video I've moved almost entirely over to DaVinci Resolve. BlackMagic's free version is really complete and (possibly because it started life mostly as a color grading application) I find that the way it presents options and tools works better with the way I like to do things.
The Studio version's pretty cheap, too, if you want to upgrade.
The Studio version's pretty cheap, too, if you want to upgrade.
Final Cut
I do light graphics work too. Making blog post images and Youtube thumbnails mostly.
I started using Gimp a few months ago after 10+ years of using Photoshop. My biggest complaint is the quality of scaling an image down. It's really really bad compared to Photoshop (even if you play with the low level details of picking the scale strategy). It always seems to come out blurry or fuzzy, to the point where I stopped using Gimp for that. Is there a better way to scale images?
Also, I just wanted to throw in a comment of, if you're switching to Gimp, don't immediately discount it for not having features you're used to with Photoshop.
For example, with Photoshop, if you copy an image to your clipboard outside of Photoshop, then you when you create a new image in Photoshop, the dimensions of the canvas will be set to the image in the clipboard. This way it's super easy to make a new image, paste the image from your clipboard and now you have a properly sized image.
Gimp has this feature but it's not implemented in a way that's the same as Photoshop. Instead, with Gimp you can just press CTRL + Shift + V to paste the image from the clipboard into a new image and it's all set up and good to go. The menu item is "paste as... new image".
I started using Gimp a few months ago after 10+ years of using Photoshop. My biggest complaint is the quality of scaling an image down. It's really really bad compared to Photoshop (even if you play with the low level details of picking the scale strategy). It always seems to come out blurry or fuzzy, to the point where I stopped using Gimp for that. Is there a better way to scale images?
Also, I just wanted to throw in a comment of, if you're switching to Gimp, don't immediately discount it for not having features you're used to with Photoshop.
For example, with Photoshop, if you copy an image to your clipboard outside of Photoshop, then you when you create a new image in Photoshop, the dimensions of the canvas will be set to the image in the clipboard. This way it's super easy to make a new image, paste the image from your clipboard and now you have a properly sized image.
Gimp has this feature but it's not implemented in a way that's the same as Photoshop. Instead, with Gimp you can just press CTRL + Shift + V to paste the image from the clipboard into a new image and it's all set up and good to go. The menu item is "paste as... new image".
My approach: import unsharpened image from Darktable, scale down with NoHalo (added in GIMP 2.10, along with LoHalo), sharpen final image with unsharp mask. When downscaling a clean image, try 1-pixel radius, strength 0.35, threshold 0.05 as a starting point.
"None" interpolation is occasionally useful as well, in image with really striking edges.
Agreed that the older downscaling algorithms aren't great. My impression is that they do a nice mathematical job of downscaling, but not a great perceptual one.
"None" interpolation is occasionally useful as well, in image with really striking edges.
Agreed that the older downscaling algorithms aren't great. My impression is that they do a nice mathematical job of downscaling, but not a great perceptual one.
But then compare that to Photoshop where you don't need to use any external tools or play with a bunch of settings.
You just scale the image down and it looks flawless and takes like 2 seconds. In over 10 years of using Photoshop I never once noticed a blurry downscaled image, but the first time I used Gimp to resize an image I immediately saw a poor result. I used every resize strategy too (including NoHalo and LoHalo -- they are both really bad compared to Photoshop).
It makes working with Gimp for any web style graphics a huge hassle because down scaling images is something you do all the time, and it's not just the final image too. It's every layer you're working with. Having to export every layer into a third party app and then re-place it is a huge time sink.
You just scale the image down and it looks flawless and takes like 2 seconds. In over 10 years of using Photoshop I never once noticed a blurry downscaled image, but the first time I used Gimp to resize an image I immediately saw a poor result. I used every resize strategy too (including NoHalo and LoHalo -- they are both really bad compared to Photoshop).
It makes working with Gimp for any web style graphics a huge hassle because down scaling images is something you do all the time, and it's not just the final image too. It's every layer you're working with. Having to export every layer into a third party app and then re-place it is a huge time sink.
Haven't noticed excessive blurriness with older cubic, or newer nohalo, but my needs are limited.
convert -resize from ImageMagick is another option.
convert -resize from ImageMagick is another option.
It happens whenever I resize a layer (any type of image) or generally resize an image. It's always so much worse than Photoshop's quality. Very noticeable.
The problem with using an external tool is I often want to resize layers on the fly to fit them into a final image I'm working on. So using a third party tool to do that goes from a 5 second operation to 5 minutes because I first have to resize it in Gimp to get the dimensions and then resize it "for real" with a different program and then place that into the Gimp image.
It's gotten to the point now where I'm looking for an alternative to Gimp, or I'll just go back to using Photoshop full time (even though it's a huge waste of $ since I only edit about 2 images a week).
The problem with using an external tool is I often want to resize layers on the fly to fit them into a final image I'm working on. So using a third party tool to do that goes from a 5 second operation to 5 minutes because I first have to resize it in Gimp to get the dimensions and then resize it "for real" with a different program and then place that into the Gimp image.
It's gotten to the point now where I'm looking for an alternative to Gimp, or I'll just go back to using Photoshop full time (even though it's a huge waste of $ since I only edit about 2 images a week).
Can anyone speak to the UX difference as well? Not just feature comparisons but what it's like to be using GIMP vs Photoshop.
I used Photoshop regularly for a few months in 2009 but that was a public school computer so I'm sure the version was one or two behind. My GIMP use is more frequent/recent but very irregular and for a variety of tasks that are never critical to my livelihood. Today I feel like GIMP is much nicer to use than when I started using it (~2006) but I still remember Photoshop being a nicer experience.
I don't know if that's well shared or has changed.
I used Photoshop regularly for a few months in 2009 but that was a public school computer so I'm sure the version was one or two behind. My GIMP use is more frequent/recent but very irregular and for a variety of tasks that are never critical to my livelihood. Today I feel like GIMP is much nicer to use than when I started using it (~2006) but I still remember Photoshop being a nicer experience.
I don't know if that's well shared or has changed.
I worked as a graphic designer for about 12 years. I've been using Gimp at work (as a programmer) for light graphics duties. Mostly cropping and adjusting levels on images.
It's not been an easy transition, but I'm getting used to it. It's similar in function to Photoshop, but performing said functions is just different enough to make it challenging.
It's not been an easy transition, but I'm getting used to it. It's similar in function to Photoshop, but performing said functions is just different enough to make it challenging.
It have a lot of functions but it is still very lacking on the UX side. I launched it today for small image correction and had to wait literally for minutes. Also, no native file picker, dialog boxes losing focus and becoming unclickable, no way to find how to move text object, all that frustrating things happen in the same 15 minutes of use.
I doubt it'll be GIMP, but i'd like to see a program that follows the UX of Paint Shop Pro (especially PSP7, the last good version IMO before they rewrote the UI and then sold it to Corel that gutted it out) which i always found much easier and more intuitive to use than both Photoshop and GIMP.
For a little while i thought Krita would be it, but i quickly realized that they just copied Photoshop for the most part.
For a little while i thought Krita would be it, but i quickly realized that they just copied Photoshop for the most part.
Was just thinking how great PSP was back in the days I still used Windows.
I would like to point out, that GIMP made a huge progress in recent years :)
I am the author of https://www.Photopea.com, which is the image editor with the second best support for GIMP files (XCF) after the GIMP itself :) In the latest GIMP releases, I really appreciate Editable Text Layers and the support for DEFLATE data compression, which makes XCF files even smaller.
I created a document with a white background layer and a simple text layer both as PSD and XCF, and then ZIPped it:
XCF: 8.25 kB unzipped, 4.03 kB zipped
PSD: 81.10 kB unzipped, 7.96 kB zipped
I am the author of https://www.Photopea.com, which is the image editor with the second best support for GIMP files (XCF) after the GIMP itself :) In the latest GIMP releases, I really appreciate Editable Text Layers and the support for DEFLATE data compression, which makes XCF files even smaller.
I created a document with a white background layer and a simple text layer both as PSD and XCF, and then ZIPped it:
XCF: 8.25 kB unzipped, 4.03 kB zipped
PSD: 81.10 kB unzipped, 7.96 kB zipped
Photopea is amazing, it actually replaced Gimp for me. Only thing I am missing is ability to close many tabs (e.g. close all except this one). Amazing project.
Tons of awesome stuff, especially around GEGL, but this one is truly fantastic:
> This includes support for CMYK ICC profiles in babl (at this point, through LCMS2), direct CMYK support as part of relevant GEGL functions and core operations, and support for reading/writing CMYK data in TIFF and JPEG files. While not done yet, this work goes towards adding first-class CMYK support to GIMP.
GIMP's poorer CMYK handling was one of about three reasons it didn't take pride of center in a small graphic design shop (attached to a professional printer) I joined as an undergrad.
> This includes support for CMYK ICC profiles in babl (at this point, through LCMS2), direct CMYK support as part of relevant GEGL functions and core operations, and support for reading/writing CMYK data in TIFF and JPEG files. While not done yet, this work goes towards adding first-class CMYK support to GIMP.
GIMP's poorer CMYK handling was one of about three reasons it didn't take pride of center in a small graphic design shop (attached to a professional printer) I joined as an undergrad.
It's sad to see Gimp giving in to the CMYK myth. I suppose it was simply too difficult to educate all the users who were somehow convinced of the need to work in CMYK space.
Some of us remember when Microsoft Word document formatting would get all messed up if you moved the document to a computer with a different model of printer. The trouble was that documents were expressed in terms of specific printing hardware. Using CMYK has a very similar problem. You can't get a generic CMYK that just magically works directly on every printer, and even if such a thing existed you still wouldn't be able to see it on your screen. The black is also a problem; a 4-color space is overspecified. You'd really need CMY.
The actual CMYK needed is only known to the printer driver or even just internal to the printer. You'll need to convert. Since you are converting anyway, there is no need to start from a color space as awkward as CMYK.
There are really just two things of use beyond RGB, gamut mapping/alerting and spot colors.
Gamut mapping distorts your color space to fit the output device. Alerting is an alternative, for example by making out-of-gamut colors flash on the screen to tell you that they are not going to be printed correctly. Both of these are deeply problematic, because they require knowledge of the specific printer that will be used. That includes the paper color, the ink currently installed, the hardware model, the driver, and maybe even the intended viewing light.
Spot colors are for crazy kinds of ink that need to be handled separately. The ink might have sparkles, UV fluorescence, magnetism, and so on. These kinds of inks don't normally get treated as part of the colorspace. They shouldn't be affected by operations like adjusting saturation. The way these inks are displayed on the screen may be quite unrelated to how they actually look. You should be able to configure an on-screen appearance with any desired color or filter effect or even with flashing.
Some of us remember when Microsoft Word document formatting would get all messed up if you moved the document to a computer with a different model of printer. The trouble was that documents were expressed in terms of specific printing hardware. Using CMYK has a very similar problem. You can't get a generic CMYK that just magically works directly on every printer, and even if such a thing existed you still wouldn't be able to see it on your screen. The black is also a problem; a 4-color space is overspecified. You'd really need CMY.
The actual CMYK needed is only known to the printer driver or even just internal to the printer. You'll need to convert. Since you are converting anyway, there is no need to start from a color space as awkward as CMYK.
There are really just two things of use beyond RGB, gamut mapping/alerting and spot colors.
Gamut mapping distorts your color space to fit the output device. Alerting is an alternative, for example by making out-of-gamut colors flash on the screen to tell you that they are not going to be printed correctly. Both of these are deeply problematic, because they require knowledge of the specific printer that will be used. That includes the paper color, the ink currently installed, the hardware model, the driver, and maybe even the intended viewing light.
Spot colors are for crazy kinds of ink that need to be handled separately. The ink might have sparkles, UV fluorescence, magnetism, and so on. These kinds of inks don't normally get treated as part of the colorspace. They shouldn't be affected by operations like adjusting saturation. The way these inks are displayed on the screen may be quite unrelated to how they actually look. You should be able to configure an on-screen appearance with any desired color or filter effect or even with flashing.
> The actual CMYK needed is only known to the printer driver or even just internal to the printer. You'll need to convert. Since you are converting anyway, there is no need to start from a color space as awkward as CMYK.
Note that this rarely applies to professional printers - as there is no "driver" as such. It's a several stage process, which relies heavily on the person involved. The 4 colours are mostly for cost reasons, otherwise you have to resort to spot colours.
The Pantone colourset is well-defined, and transfers to process printing well, but it is CMYK.
The average person has no need of it, but the professional will find it essential.
Note that this rarely applies to professional printers - as there is no "driver" as such. It's a several stage process, which relies heavily on the person involved. The 4 colours are mostly for cost reasons, otherwise you have to resort to spot colours.
The Pantone colourset is well-defined, and transfers to process printing well, but it is CMYK.
The average person has no need of it, but the professional will find it essential.
Pantone is not CMYK and can not even be represented by CMYK. From Wikipedia: "However, most of the Pantone system's 1,114 spot colors cannot be simulated with CMYK but with 13 base pigments (14 including black) mixed in specified amounts."
Every printer has something equivalent to a driver. It may be called something else. It may be a special printer program to run, or even a web service on the printing hardware that will accept jobs. All sorts of crazy variation is possible, and it doesn't matter. At some point in the process, there is a mechanism to convert from device-independent colors to device-specific colors. There is no good reason for the device-independent colors to be CMYK, and plenty of reasons to avoid CMYK.
Every printer has something equivalent to a driver. It may be called something else. It may be a special printer program to run, or even a web service on the printing hardware that will accept jobs. All sorts of crazy variation is possible, and it doesn't matter. At some point in the process, there is a mechanism to convert from device-independent colors to device-specific colors. There is no good reason for the device-independent colors to be CMYK, and plenty of reasons to avoid CMYK.
That's good news indeed that I skimmed through. Thanks for pointing it out.
Nice to see G'MIC's smart colorize algorithm making its way into core GIMP. The research team worked with David Revoy, the character designer of several Blender open movies (such as Sintel or Spring), so I've heard a lot about it from him. He's written a few blog posts (e.g. [1]) and videos on how to use the Krita and GIMP implementations of the feature.
[1] https://www.davidrevoy.com/article324/smart-coloring-preview...
[1] https://www.davidrevoy.com/article324/smart-coloring-preview...
Fore those interested, here is the link to the paper introducing the algorithm:
https://hal.archives-ouvertes.fr/hal-01891876/document
It has a lot of nice illustrations.
It has a lot of nice illustrations.
This release contains my first ever contribution to the project! It's a small one, but I still feel proud of it as a novice developer!
GIMP 2.10 felt like a big step-up in quality-of-life changes for me, I really recommend giving it a go if you've got an older version (Ubuntu 18.04 has 2.8)
I'm having a hard time moving to GIMP. But I really want to love it.
I've used Photoshop for almost 2 decades and recently moved over to Ubuntu. I always struggle with shortcuts and generally 'how it works'. Simply opening a file, doing some cropping or resizing and saving it as a different file type causes me headaches because I still think too much in Photoshop concepts.
How do I get out of this?
I've used Photoshop for almost 2 decades and recently moved over to Ubuntu. I always struggle with shortcuts and generally 'how it works'. Simply opening a file, doing some cropping or resizing and saving it as a different file type causes me headaches because I still think too much in Photoshop concepts.
How do I get out of this?
Once of the biggest hang-ups people seem to run into is the concept of layers. In photoshop layers are abstract and infinite. In gimp they are explicit and finite. In gimp a layer has size, that may or may not match the image size. They can be scaled, resized, cropped, etc independent of any such transforms to the image itself.
Differences in workflow themselves are usually not hard to overcome. It's the conceptual paradigm the lies beneath the workflow that people have to wrap their heads around in order to understand _why_ a workflow is different.
Differences in workflow themselves are usually not hard to overcome. It's the conceptual paradigm the lies beneath the workflow that people have to wrap their heads around in order to understand _why_ a workflow is different.
[deleted]
As someone who has used Gimp on/off since the pre 1.0 days ie. when it was a Motif (Lesstif?) app, it certainly has come a long way.
One of the things that held it back (for me) for a long time was the lack of 16/32-bit colour processing, which it didn't get until the 2.9 (development builds) in 2015:
https://petapixel.com/2015/11/29/gimp-version-2-9-2-brings-1...
And of course this didn't make it into stable builds until around a year ago. I am very pleased with 2.10 overall, and these days I only start up Photoshop if there is something I can't do in Gimp 2.10.
One of the things that held it back (for me) for a long time was the lack of 16/32-bit colour processing, which it didn't get until the 2.9 (development builds) in 2015:
https://petapixel.com/2015/11/29/gimp-version-2-9-2-brings-1...
And of course this didn't make it into stable builds until around a year ago. I am very pleased with 2.10 overall, and these days I only start up Photoshop if there is something I can't do in Gimp 2.10.
Is it easy to for someone to transition from Photoshop to, yet?
Or is there any easy-to-underatand transition guides?
Or is there any easy-to-underatand transition guides?
I was a Photoshop user from the late 90's until about 3-4 years ago. It was a slow transition to FOSS tools, because there was never a concerted effort to switch to FOSS, it just happened because I like the tools better, and it's easier to not have to deal with licensing.
Photoshop is a bit a of jack of all trades, and the FOSS tools are usually more targeted. So Gimp may have all that you need, but that depends on what you use Photoshop for. I would look at the capabilities of not only Gimp, but Krita (for digital painting), Darktable if you want a more specialized tool than Gimp for photo manipulation, Inkscape for vector editing, Libresprite for pixel art (which is a fork of Aseprite, which went from open to closed source).
As far as being easy to transition to, I would say that it's a bit easier now than it has been in the past, but they make no effort to be a Photoshop clone. The biggest hurdle is re-training your muscle memory. I would suggest to do what I did, and do a project here and there using Gimp, and eventually the muscle memory problem will not be such a hurdle.
Photoshop is a bit a of jack of all trades, and the FOSS tools are usually more targeted. So Gimp may have all that you need, but that depends on what you use Photoshop for. I would look at the capabilities of not only Gimp, but Krita (for digital painting), Darktable if you want a more specialized tool than Gimp for photo manipulation, Inkscape for vector editing, Libresprite for pixel art (which is a fork of Aseprite, which went from open to closed source).
As far as being easy to transition to, I would say that it's a bit easier now than it has been in the past, but they make no effort to be a Photoshop clone. The biggest hurdle is re-training your muscle memory. I would suggest to do what I did, and do a project here and there using Gimp, and eventually the muscle memory problem will not be such a hurdle.
Just for clarification, Aseprite is "source-available": you're free to browse [1], clone and build the source for your own usage as long as you don't redistribute your build. There's even a tutorial for it. Official builds, of course, are paid.
[1] https://github.com/aseprite/aseprite
[1] https://github.com/aseprite/aseprite
I don't know if it's still true but while Gimp doesn't have filters on layers like Photoshop has I won't make the move. Example: applying a drop shadow and a border on a layer, doing a thousand other things to other layers and then tweaking the settings of the filters of the first layer like it was just applied.
I tried switching and certainly didn't put the effort Gimp deserved but these days I use Krita for quick editing (but I never do webdesign anymore).
I tried switching and certainly didn't put the effort Gimp deserved but these days I use Krita for quick editing (but I never do webdesign anymore).
Love gimp and have used it forever, but not sure what they did with arbitrary rotation in the 2.10 branch, it's a bit of a mess. It used to be easy to fix photos with non-level horizons.
Now, every time I need to select the higher interpolation quality, preview results (huh), and put in my own guidelines manually since the builtin rotation guides are on the image itself (and rotate with it) instead of perpendicular to the window (wtf). Bass-ackwards?
Wonder if that was fixed, or perhaps I'm doing something wrong?
Now, every time I need to select the higher interpolation quality, preview results (huh), and put in my own guidelines manually since the builtin rotation guides are on the image itself (and rotate with it) instead of perpendicular to the window (wtf). Bass-ackwards?
Wonder if that was fixed, or perhaps I'm doing something wrong?
Have you tried straightening with Measure Tool? Just create a line along the horizon, then press "Straighten" and voila. Another option is corrective rotation with Guides set to "Number of lines" with a sufficiently large number.
Interesting. The number of (non-manual) guides is meaningless to me however, since the are attached to the image instead of the window.
Anyone know if editing large images is less sluggish now than it was in the previous iteration of 2.10? I'm still using 2.8 because of that.
It'd be interesting to hear from Photoshop power users, who've made the switch, what they miss and what Gimp does better.
For those who didn't make it past the highlight list, here's the donation/support link: https://www.gimp.org/donating/ I just made a small donation and encourage others who use Gimp regularly to do the same.