Hi,
I'd like to start saying that some may consider this as NOT a bug yet if all other image viewers behave "the other way" and if re-modifications deteriorate picture quality it's a bug for me like many...
What's? If you ever set a Gamma value in the "VIEWING" section of your settings and perform modifications other than related to color such as crop etc. and try to save your file... Voila you've got your image gamma edited TOO even if it's a "viewing" option...
What others do? Other Viewers simply stick view/gamma settings only for viewing, in case you have no other means of monitor calibration or etc., and apply gamma to file itself if only chosen deliberately via other command, like "Color corrections..." in IrfanView. Why? Because they want user to control his modifications by not auto applying a setting. Many, like IrfanView, have batch processors for that and separate mechanisms of gamma for both viewing and modifying...
In short; a "viewing gamma" setting generally should never modify an image unless it's been authorized, like another setting (in browsing/editing or file handling sections) or user confirmation about the "gamma loop" effect of current IrfanView's "viewing gamma" behavior. The user who wants "modification gamma" can do it so already by "color corrections.." and then save the changed image...
Otherwise "viewing gamma" you set for your viewing easement reflect on image in an harmful loop (all "white" after further modifications) and makes image incompatible for other monitors/systems that you may send your image to since they may also have their "viewing gamma" preferences...
And "please" think troughly and experiment if you have never changed your gamma setting once since only a sufferer may likely to empathize the situation. And for the 'gods' even a simple "not so important" bug rejection is better than "it's perfectly fine" talk...
Anyway, thanks for the program, thanks for the read...
I'd like to start saying that some may consider this as NOT a bug yet if all other image viewers behave "the other way" and if re-modifications deteriorate picture quality it's a bug for me like many...
What's? If you ever set a Gamma value in the "VIEWING" section of your settings and perform modifications other than related to color such as crop etc. and try to save your file... Voila you've got your image gamma edited TOO even if it's a "viewing" option...
What others do? Other Viewers simply stick view/gamma settings only for viewing, in case you have no other means of monitor calibration or etc., and apply gamma to file itself if only chosen deliberately via other command, like "Color corrections..." in IrfanView. Why? Because they want user to control his modifications by not auto applying a setting. Many, like IrfanView, have batch processors for that and separate mechanisms of gamma for both viewing and modifying...
In short; a "viewing gamma" setting generally should never modify an image unless it's been authorized, like another setting (in browsing/editing or file handling sections) or user confirmation about the "gamma loop" effect of current IrfanView's "viewing gamma" behavior. The user who wants "modification gamma" can do it so already by "color corrections.." and then save the changed image...
Otherwise "viewing gamma" you set for your viewing easement reflect on image in an harmful loop (all "white" after further modifications) and makes image incompatible for other monitors/systems that you may send your image to since they may also have their "viewing gamma" preferences...
And "please" think troughly and experiment if you have never changed your gamma setting once since only a sufferer may likely to empathize the situation. And for the 'gods' even a simple "not so important" bug rejection is better than "it's perfectly fine" talk...
Anyway, thanks for the program, thanks for the read...
Comment