jake klein
Member
Well I got the trial going as you will see form the watermark. Can't wait to have some extra cash and pick up this software!
Kudos, Sebastian,Hi,
SNS-HDR v1.4.10 has been released.
1. Improved dynamic range compression.
2. Added "Highlights" parameter.
3. Improved "Black" parameter.
4. Modified presets.
Regards,
Sebastian
Hi,
SNS-HDR v1.4.10 has been released.
1. Improved dynamic range compression.
2. Added "Highlights" parameter.
3. Improved "Black" parameter.
4. Modified presets.
Regards,
Sebastian
Fully agreed. These areas need to be "highlighted" (pun intended) for us to use the product to the best of our abilities.Hi Sebastian,
Thanks for your continued effort, it's much appreciated.
Could you explain the function of the Highlights parameter? Am I correct in assuming that SNS-HDR in principle does not clip or shift shadows and highlights after reading the input file(s), it squeezes all the tonality that's present in the input files in the data we will modify with SNS-HDR.
However, if the lightest frame is light gray at the most, and/or the darkest frame is dark gray, then the Highlights and Black controls do allow to move that maximum/minimum tonality separately (towards or away from the limits), much as the Contrast control does for both at the same time?
I (and I know I'm not alone) would still love to have a visual feedback (preferably on the preview) when clipping occurs, especially useful now that we can easily modify the highlight position on the tonescale ...
Cheers,
Bart
Highlights parameter is equivalent to the Shadows parameter but this parameter is responsible for the bright areas. You can darken the sky by using this parameter.Could you explain the function of the Highlights parameter?
Yes, SNS-HDR never cut shadows and lights. SNS-HDR always operates on the curves.Am I correct in assuming that SNS-HDR in principle does not clip or shift shadows and highlights after reading the input file(s), it squeezes all the tonality that's present in the input files in the data we will modify with SNS-HDR.
However, if the lightest frame is light gray at the most, and/or the darkest frame is dark gray, then the Highlights and Black controls do allow to move that maximum/minimum tonality separately (towards or away from the limits), much as the Contrast control does for both at the same time?
I wonder what criteria to adopt.I (and I know I'm not alone) would still love to have a visual feedback (preferably on the preview) when clipping occurs, especially useful now that we can easily modify the highlight position on the tonescale ...
Highlights parameter is equivalent to the Shadows parameter but this parameter is responsible for the bright areas. You can darken the sky by using this parameter.
Yes, SNS-HDR never cut shadows and lights. SNS-HDR always operates on the curves.
I wonder what criteria to adopt.
Thanks Bart for your advice, I will think about this.Here things get interesting (and with an opportunity to again do better than the rest of the industry). Traditional clipping is often seen simply as pixel values that exceed a certain limit (an upper or lower threshold, either fixed or user selectable). For example, one could say any pixel value above 254 in 8-bit in one color channel is considered clipped. But that isn't necessarily so, because perhaps that pixel was originally indeed 255, a little bit brighter than 254.
What I would consider to be clipping, is when I increase the exposure a little, and a pixel that was 254 now becomes 255, thus losing the difference with the real 255. Information gets lost, and I'd like a warning that that is the result of my editing. Maybe that's not a problem for the rest of the image, because there are now more pixel values for the other tones to use, but that's up to the judgement of the photographer. Sometimes it is no problem to clip a few specular highlights (losing the color and turning white), but sometimes it is important to keep the original subtle color differences (e.g. the colors of stars).
I understand that that is not easy to implement, because it requires comparing 2 exposure levels and histograms in at least 3 color channels, that's why traditionally the simple approach is taken (anything that's 255, or some other value, is considered clipped). It would be wonderful if you could implement a more revolutionary type of indicator than traditionally is done.
I used 255 as an 8-bit example, but there are also good arguments for setting an upper limit a bit lower (e.g. 253), because that will allow to avoid issues with featureless whites in inkjet prints where the dithering will be almost absent. Allowing the user to determine that limit would be perfect, but it adds a bit complexity to the user interface I understand that. A similar line of thought applies to the shadow end of the image, where printing on matte paper may lose some shadow detail, so one would like to avoid losses due to processing as much as possible and hope that the printer profile is good in keeping the detail that's there.
Thanks Sebastian, I have downloaded it and it looks good as usual. However: in my humble opinion not everything gui is better. I actually liked being able to change the RGB parameters numerically. The new tool is too rough and one can only make adjustments visually without knowing how much of what is being adjusted. This also makes repeating the same adjustment for another picture impossible unless one saves the adjustment as a preset. Just my 0.02 cents.Hi,
SNS-HDR v1.4.14 has been released.
1. Modified white balance tool.
2. RGB parameters replaced by a graphical tool.
3. Added ability to specify a color profile for the source images stored in Radiance HDR and OpenEXR formats.
4. Fixed reading of grayscale images.
5. Fixed saving of images on the desktop.
Regards,
Sebastian
Ok, I would add the possibility to switch the view - graphics field / sliders.Thanks Sebastian, I have downloaded it and it looks good as usual. However: in my humble opinion not everything gui is better. I actually liked being able to change the RGB parameters numerically. The new tool is too rough and one can only make adjustments visually without knowing how much of what is being adjusted. This also makes repeating the same adjustment for another picture impossible unless one saves the adjustment as a preset. Just my 0.02 cents.
Ok, I would add the possibility to switch the view - graphics field / sliders.
You are too generous Sebastian and I appreciate it. However, you need not change it purely on my account. Let's wait and see if some other users shall also comment on that aspect.
Even better than three R/G/B controls, would be a color temperature and tint control when we are changing the color balance. It's a more natural way of thinking for a photographer, even if the actual controls are implemented as R/G/B in the program code.
Cheers,
Bart
You know how to convert?Even better than three R/G/B controls, would be a color temperature and tint control when we are changing the color balance. It's a more natural way of thinking for a photographer, even if the actual controls are implemented as R/G/B in the program code.
You know how to convert?
Ok, I change this.Currently when you define a mask and then click one of the presets (with the mask active), the underlying image changes according to the preset. I think it would be useful, fast and powerful if only the masked area changed to match the preset.