- User Since
- Apr 9 2015, 1:22 PM (285 w, 3 d)
May 18 2015
@Brecht Van Lommel (brecht) , aha, I misrepresented it as a bug , you may put it as a feature request :)
also I got some questions that I want to ask you about "related to function callbacks that you wrote "write_render_tile_cb, update_render_tile_cb" and "progressive, progressive_refine"
May 5 2015
Apr 30 2015
sorry for this, my first test was inside blender "no images saved" , and images were the same, thought it would make the same problem after saving "like in Cycles Standalone" , but the save mechanism is different in Blender and Cycles Standalone.
Apr 20 2015
I can't reproduce it from blender, the saved image is exactly = to the previewed image "in any format" , both appear with linear gamma which gives the user wrong impression "at least when he tries to render in progressive mode to test lights and shaders"
Apr 15 2015
well I consider (1) as a bug because it adds wrong values "if I'm correct" , they should be added in XYZ color space (not RGB)
about (2) it is misleading for the user, user expects an antialiasing filter, here it doesn't do any reconstruction
about (3) again it is for the "correct" color viewing during render, so user doesn't add light to dark areas "while they are not black if they got gamma correction"