Alexander Sh

Hi, Looks like HSV checkbox in HSL layer seriously cuts dynamic range of 32bit images. You can reproduce bug as following: Open 32bit HDR image Add Exposure layer with +5EV setting, so the image gets blown out above 1.0 range Add HSL layer with +50% saturation Add Exposure layer with -5EV setting to return back exposure to initial Toggle HSV checkbox in HSL layer to see a bug Metal acceleration is enabled.

Hello, I'm experiencing issues with HDR merging in the latest versions. App drops DNGs from processing. I have DNGs where everything is fine, but some are failing to merge. I'm adding 3 DNG photos (DSC100.dng, DSC101.dng, DSC102.dng) with 3EV steps to HDR merging dialog with following settings: Perspective Align — on Remove ghosts — on Noise reduction — on Tone map — off Once I'm pressing "OK" button, app creates an HDR image only from 2 DNG images dropping out 3rd. In "Sources" view I see only following: Deghosted HDR image HDR image DSC100.dng DSC101.dng As a result, the image has totally clipped highlights. Any ideas?

Ok, I've created feature request.

Hi, I have proposals for histograms. 1. At the moment histograms for linear/hdr images representing only linear image. It's quite inconvenient when your histogram doesn't reflect what you see on display or what will be exported in non linear image formats like png/jpg/tiff. It would be nice to see switch in histogram view "Show for display colorspace". 2. Add new logarithmic mode for histogram views where Y axis is in logarithmic scale. Some tools have such feature and it is very convenient to have precise presentation of image with small amount pixels with same brightness. At the moment you can't understand from looking on histogram: is this thin 1-pixel line on X-axis is 1 pixel per sample or there 50 pixels squashed to this 1-pixel line. On logarithmic scale you'll clearly see this.

Reinstalling the app resolves the issue. Looks like 1.7 can't read macros db created by 1.6 and after upgrade 1.7 unable to read this db.

Hello, Constantly crashes on adding macro to library. Crash dump attached. affinity_photo_1.7.0_crash.txt

Hello, When I work with HDR/Linear images histogram/scope views are showing in linear space as well. This is completely inconvenient, since it doesn't reflect what I see on display and I don't understand how histogram will look on exported image: will be there overexposed or underexposed areas, how lightness distributed over image and so on. Now I completely do not understand this aspects. Linear histogram/scope absolutely not representative. So here are questions: 1. Is there any setting to switch histogram/scopes to view in output colorspace instead of linear? 2. Is it possible to export images using OCIO Display Transform which I can also use to preview in 32-bit Preview pane?

Hi, With enabled Metal acceleration OCIO adjustment has issues with color accuracy. I'm using aces_1.0.3 ocio config. Steps to reproduce: 1. Open photo with smooth color gradients. 2. Add OCIO layer with conversion "Role - scene_linear" -> "ACEScc" 3. Add another OCIO layer on top with conversion "ACEScc" -> "Role - scene_linear" Expected result: image should has no color/tone changes since operation is reversible. Actual result: image has color changes – to see them just turn off/on both OCIO layers. Disabling Metal acceleration doesn't show any issues.

Thank you for explaining. Now I see the reason of this behavior.

I've tried either enable or disable Metal and result is always the same. Even in 1.6

Why do you think so? When white balance layer in group, why it shouldn’t be applied to background layer image? What the sense? Group is just for grouping (until it is passthrough). The main problem is that adding disabled Fill layer on top of group affects any number of other layers in group. This is a bug of Fill layer as for me.

Hi, Bug description: Fill layer above all other layers in group makes their adjustments ignored. Doesn't depend on color depth or Metal acceleration. Steps to reproduce: 1. Open any RGB image. 2. Add White balance layer. 3. Set White balance "-100%" 3. Create a Group a with White balance inside. 4. Add Fill layer in to Group and above White balance layer. 5. Disable Fill layer Expected behavior: Fill layer isn't visible and White balance applied. Current behavior: Fill layer isn't visible, but White balance adjustment ignored. You can add any number of layers with adjustments in group below Fill layer and their adjustments will be ignored until Fill layer in this group. Note: this bug is reproducible in 1.6.11 as well

Hi, Here what I've found: image is losing information in overexposed areas for 32bit hdr images developed from raw with saturation settings. Steps to reproduce: 1. Disable Metal acceleration 2. Set assistant to 32bit linear for raw 3. Open raw image in Developing Persona 4. Set exposure +5 5. Set saturation +20% 6. Press Develop 7. Add exposure layer 8. Set exposure -5 Expected behavior: image should restore all overexposed areas like no +5 exposure was applied in Developing Persona Actual result: image looks like all information in overexposed areas is lost. Workaround: Enabling Metal acceleration fixes this and step #8 restores all overexposed information.

Hi, Caught brightness/contrast layer issue on hdr images. Steps to reproduce issue: 1. Open properly exposed raw image as 32bit linear hdr without curve applied 2. Add exposure layer. 3. Add brightness/contrast layer with default adjustments above exposure layer. 4. Select exposure layer and set exposure +2..+3. Overexposed areas are become corrupted with false colors (see screenshot). Once brightness layer is disabled — overexposed areas are back to normal. Workaround: disabling Metal acceleration fixes this issue.