Are there any famous/popular graphic designers that use GIMP?
Gimp 2.9.2 Released
41–50 of 64 posts
Re: Gimp 2.9.2 Released
#42Finally, 16 bit per channel. It took freaking forever. Good job, guys.
Re: Gimp 2.9.2 Released
#43Using Gimp since the 90's, sure has changed for the better. Lately trying 2.9 on Linux, most recent versions seemed to have ironed out bugs pretty well and I can get work done with it.
Under Windows, gimp 2.8 has been marginal at best, runs quite slowly, sometimes crashing or freezing, kind of frustrating to use. I downloaded the 2.9 development binary this morning. While still slow, seems a bit faster than 2.8, and didn't crash. More testing will show if this holds up.
I know about people disfavoring workflow of gimp vs. photoshop, but given cost of latter, gimp remains a potentially worthy alternative. It depends on improving the efficiency of operations at least moderately, if so, it looks like the new version of gimp can succeed, even on Windows.
Re: Gimp 2.9.2 Released
#44Great, lots of new features. But the crucial thing for me is still marked "wontfix": allow saving to external formats directly. I often open some png or jpeg, edit it and want to save it. But no, I have to export it, confirm that I want to overwrite the file I am editing, and then confirm that I don't want to save to .xcf before closing file or Gimp. Infuriating. It makes me want to fork it just fix this nonsense, bu…
If that is your primary use case, all you need to do is to assign Ctrl+S to Overwrite command instead. Boom, you got your saving back.
And assuming you have dynamic keyboard shortcuts turned on (and why wouldn't you? Best thing ever.) this is about as painless as it gets.
Re: Gimp 2.9.2 Released
#45Great, lots of new features. But the crucial thing for me is still marked "wontfix": allow saving to external formats directly. I often open some png or jpeg, edit it and want to save it. But no, I have to export it, confirm that I want to overwrite the file I am editing, and then confirm that I don't want to save to .xcf before closing file or Gimp. Infuriating. It makes me want to fork it just fix this nonsense, bu…
There's a plugin for that :) Maybe this is for you: https://github.com/akkana/gimp-plugins/blob/master/save-expo...
THANK YOU!!! Didn't know that, will try it as soon as I can. You made my day. :)
Re: Gimp 2.9.2 Released
#46Earlier quoted context omitted.
I'm using 2.8.10, and this behavior seems fixed. If you open a JPEG or PNG, there's now a menu option in File called "Overwrite file.jpg". If you do an export, this menu option is replaced with "Export to file.jpg" that repeats your last export without a dialog box. The shortcut is Ctrl+E.
The Overwrite option has been in there a long time and is essentially just an alias for the Export funtionality. Although it does help alleviate the situation, I totally agree with what Drdrdrq is saying - just make Ctrl-S work properly!
I don't think it's really clear that this is proper behaviour, though? If we're talking JPGs, every time you go through opening that file and "saving" it, it's going to be more and more mangled by the compression. (Also, each time you have to ask yourself "how much do I want to mangle it this time?" - which doesn't make sense). Effectively, the file you save definitely does not preserve what you have in the editor. On the other hand, with the current behaviour, Ctrl-S provides a certain guarantee that the output will be lossless.
And, sure, one can go off and appeal to nature and say "it's standard," but, I really don't buy that argument. There really isn't that much software that deals with the same stuff as GIMP. This isn't like a text editor or something. They are very much in a position to set their own standards when the defacto behaviour is wrong.
Re: Gimp 2.9.2 Released
#47Great, lots of new features. But the crucial thing for me is still marked "wontfix": allow saving to external formats directly. I often open some png or jpeg, edit it and want to save it. But no, I have to export it, confirm that I want to overwrite the file I am editing, and then confirm that I don't want to save to .xcf before closing file or Gimp. Infuriating. It makes me want to fork it just fix this nonsense, bu…
I haven't used Photoshop in quite a few years, but I'm pretty sure it works (or worked) the same way as Gimp. Maybe people who do a lot of work in image editing software are accustomed to this workflow? It seems reasonable, since exporting flattens layers and such, which a professional would probably want to preserve (and may not want to risk accidentally losing).
I don't use PS, but in my use case this behaviour is really annoying. Maybe I am not their target user, I don't know - the problem is that Gimp is really nice piece of software and it is exactly what I need.
I am baffled why they changed this and why they stick to this decision. But it looks like there is a plugin which fixes that (see one of the other answers), so - yay! :)
Re: Gimp 2.9.2 Released
#48I'm still using 2.6.12 ... would like to try the new versions if they work well.
Re: Gimp 2.9.2 Released
#49Earlier quoted context omitted.
If that is your primary use case, all you need to do is to assign Ctrl+S to Overwrite command instead. Boom, you got your saving back.
And assuming you have dynamic keyboard shortcuts turned on (and why wouldn't you? Best thing ever.) this is about as painless as it gets.
Not really, no. I just use Edit -> Keyboard Shortcuts to configure GIMP, since it doesn't happen very often. (I didn't assign Ctrl+S to Overwrite for myself though, I like the new behaviour.)
Re: Gimp 2.9.2 Released
#50Earlier quoted context omitted.
The Overwrite option has been in there a long time and is essentially just an alias for the Export funtionality. Although it does help alleviate the situation, I totally agree with what Drdrdrq is saying - just make Ctrl-S work properly!
I don't think it's really clear that this is proper behaviour, though? If we're talking JPGs, every time you go through opening that file and "saving" it, it's going to be more and more mangled by the compression. (Also, each time you have to ask yourself "how much do I want to mangle it this time?" - which doesn't make sense). Effectively, the file you save definitely does not preserve what you have in the editor. O…
It's not just lossy compression you lose things like layers and stuff when you flatten the file to a bitmap.
In the general sense this is the correct behaviour but in the specific instance of doing simple bitmap manipulation like cropping "export as save" is expected and since thats the most common use case for many people it's probably frustrating.
To be perfectly honest people using gimp for image cropping should use something else, gimp gui is clunky, it starts slowly and there is no benefit.