Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
You don't, this is now the intended operation in 2.8. When you "Save" you are saving to the GIMP's format so all of your work (I.E. layers) is preserved and editable in the future. If you want to flatten that work down to a simple image, then you aren't saving it, you are exporting it.
Funny, but true. I just pulled out the 2.6.12 code and rebuilt for Slackware 14.
I could no longer stand the absurd slowness of the crop and selection tools (for example), esp on >20MB images at 400% (16G/quad core Phenom that does nothing but graphics and video, and using rawtherapee for all color preprocessing).
The team did make 2.8 design/time/resource choices well in many cases, the detail that most processors today are multi-core seems to have been lost.
Why in the world would you want to save in .jpg? Have the results to someone and they say can you tone down that red a bit or add this...Congratulations now you get to rebuild your image. Ps defaults to .psd why should GIMP be different when you're finished control shift S name it, control E name (merged)one to keep and one to mail away.
Normal for me is 4928x3264 but the panos are typically 3-6x larger.
Pulled gimp 2.8.8, brought gegl/babl up to current and got a significant performance boost, and the poor multi-core utilization comment is still valid.
Thanks for the VIPS/nip2 pointer. I'm going to try a modified workflow:
nip2(split up large image) -> gimp -> nip2(recombine).
I would expect normal workflow would be to save files in a non-lossy format preserving all layers, etc. And certainly save your work multiple times during your editing session(s). And then when you're all done, you might create a jpg to send to a less savvy user who wouldn't know a format from a marshmallow. All the while retaining the original image, and your non-lossy layer-preserved working copy for yourself.
The Gimp is a pretty sophisticated editor, along the same lines as Photoshop (which doesn't save to jpg as its default either). Maybe lesser newbie type photo editors could get by with saving by default to jpg, but I doubt any halfway serious photo editing person would want that. And the people who use The Gimp and/or Photoshop are at least "halfway serious" usually.
nip takes a bit of time to get used to .
It also has a built in function to split images
tile to something x something with or without an overlap
and is good for putting together panoramas
with one or two tie points
all of these mosaics were done with nip
( within a few days of the rover landing on mars ) https://plus.google.com/photos/10269...985?banner=pwa
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.