1) FastRawViewer (with standard settings) renders to RGB at GPU side, there is no simple/fast access to screen data. Generally it is possible to download rendered image to CPU side but this may lead to the need to remove the word Fast from the program name.
2) RGB (rendered) values do not help with culling (so: selection from several similar images based on image exposure): image adjustments (lightness, white balance, contast) will change rendered values while source RAW values not change. In fact, culling using rendered RGB values complicates and confuses the selection process see our article on this topic: https://www.fastrawviewer.com/culling-with-raw-converter
lexa
Mon, 04/07/2025 - 06:19
Permalink
1) FastRawViewer (with
1) FastRawViewer (with standard settings) renders to RGB at GPU side, there is no simple/fast access to screen data. Generally it is possible to download rendered image to CPU side but this may lead to the need to remove the word Fast from the program name.
2) RGB (rendered) values do not help with culling (so: selection from several similar images based on image exposure): image adjustments (lightness, white balance, contast) will change rendered values while source RAW values not change. In fact, culling using rendered RGB values complicates and confuses the selection process see our article on this topic: https://www.fastrawviewer.com/culling-with-raw-converter
--
Alex Tutubalin/FastRawViewer team
Add new comment