After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 794827 - Limit promotion to floating point on load to lossy formats like JPG
Limit promotion to floating point on load to lossy formats like JPG
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: General
git master
Other All
: Normal normal
: 2.10
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2018-03-29 23:50 UTC by Øyvind Kolås (pippin)
Modified: 2018-05-24 19:23 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Øyvind Kolås (pippin) 2018-03-29 23:50:44 UTC
The current preference to promote 8bit images to floating point - possibly with dithering is very useful for JPGs and I am happy to have it as a default there -
promoting the high resolution JPGs to floating point with dither automatically does what I otherwise want to do for practically every JPG I open for editing, before my initial rotating and perhaps scaling down operations that further bring the histogram and content of the image to be proper floating point images.

For PNGs though - which also can be 8bit, the feature is a liability; by opening a PNG with intent to crop and export, one with the most basic workflow easily end up with a slightly dithered 16bit PNG, by limiting the feature to JPGs (and maybe some other mostly photographic 8bpc format?) workflows would be improved.
Comment 1 Jehan 2018-03-30 11:27:12 UTC
Should this be decided by 2.10? If so, we could make it a blocker.
Comment 2 Michael Natterer 2018-04-01 14:12:47 UTC
This should probably not be restricted to JPG...
Comment 3 GNOME Infrastructure Team 2018-05-24 19:23:58 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1345.