Have been there only once, in the late morning hours and the view was great.
Checking the taken pictures, it was disappointing to see the jpg ooc.
Luckily that time, i had started to keep the RAW files and this pic challenged me to learn processing with RT. Lateron I also tried Lightroom, but came back to RT very quickly.
Interesting exercise. To put some definition into the peeps, I did some “capture sharpening”, not @heckflosse’s well-crafted tool, just a bit of convolution sharpening on the full-resolution image. A bit of additional whitebalance correction over the as-shot, filmic curve put in some punch. That’s it, here’s the full-resolution image (JPEG quality=85), from rawproc:
@ggbutcher I know that you usually don’t go full resolution, so I’m not sure you would have noticed the “blockiness” in the dark areas pointed out. Otherwise, very nice!
JPEG compression. Much reduced when I saved it with quality=95, but that image is almost 9MB, so I won’t impose it on the forum.
That’s one of the reasons I don’t post full-resolution; I prefer to do a quality resize to the approximate viewing dimensions and save with as little compression as possible. PNG looked fine at full resolution, but 44MB…
I just spent quality time comparing 100, 95, 92, and 85; viewed at 100%, you can start to see the DCT blocks at 92, but in that cave they look more like the deep shadow variation of the cave wall. 85, definitely visible. I had it set to 95 before I started this PlayRay, going back to that now…
I hadn’t implemented an interface to PNG compression level, but I might do that before I issue rawproc 1.1.
Are you using the same library? Quality may differ depending on the library and internal settings. I.e., 95% of app A could be different from that of app B.
I’ve just finished inventorying the different JPEG, PNG, and TIFF libraries I’m using, and I think I’m going to need to individually compile each for releases. Particularly the AppImage, as this just picks up whatever library the OS deems sufficient. What I want to be using for JPEG is libjpeg-turbo; I know I get this with my Windows mxe static builds, but everywhere else is a bit of a crapshoot.
I know some probably think I’m nuts for static linking, but it gives me control over stuff like this.
