NotMyFault

steps to reproduce: open the raw file set vertical lens correction to -100% choose crop tool rotate crop to about -30% use crop tool to make the full layer visible apply crop develop (switch to photo persona) use move tool to inspect bounding box of embedded raw layer switch back to develop person develop persona shows areas exceeding bounding box, invisible in Photo Persona

Please revise the toggle for lens correction. Currently you have a global switch lens correction, and the additional switch for lens-specific correction (from lens-fun DB). If you want to deactivate the manual correction temproarily, but keep the automatic correction, this combination is not possible.

That is interesting. Develop Person has a Split View option to show the modified version side by side or in-place with slider. It seems i misinterpreted the toggle slider to just deactivate the lensfun-based automatic / lens-specific correction (and not the manual sliders below). Can be closed.

In case output is set to pixel layer, exceeding areas are destructively cut off. This differs from V1 where you could re-develop a pixel layer and recover those areas.

Having a second look: Develop Persona shows the RAW layer „unbound“, so lens corrections can extend beyond the rectangular layer bounding box. Photo Persona seems to use a rectangular shape with a fill of the processed raw image. This means any areas exceeding the bounding box get clipped off. This rendering discrepancy is at least totally surprising. It would help if Develop Persona would show the edge of the invisible bounding box to give an indication what parts of the RAW file will get cur off when finishing Develop.

I would expect that the slider value and the rendered scale always match. in this case, the slider stays at 50%, but the actual rendered scale reverts back to 100%. This is an UI inconsistency and very annoying. I would prefer to keep the scale at 50% to allow checking the effect of lens correction. At 100% zoom the effect is difficult to spot because the barrel extends in the middle of the edges, but this is always cropped off when toggling lens correction.

A made a new bug report for iPad with a simplified setup. Can you replicate the issue on Desktop? Not sure if this thread covers the exact same issue.

Photo on iPad renders different cropping areas in Photo vs. Develop Persona in case you are using lens correction and rotation by cropping. trigger conditions: lens correction that affects edge (barrel / horizontal / vertical) Crop with rotation maybe embedded / linked RAW file IMG_7575.CR2

Hi, when toggling lens correction on/off, the scale setting reverts to 0 but stays on e.g. -50%. if you touch the scale setting, rendering will again reflect the slider value.

Agree that there are redraw issues. Never the less, in my perception the bug of this thread is not caused by or related to those redraw issues. Redraw issues could be overcome by changing zoom level, or inspect navigator panel (which can be enlarged to full screen size if panel is detouched) and/or layer thumbnails, or channels panel. When combining lens correction (barrel distortion) with crop-in and rotation by crop, the crop gets misplaced after develop. This is new to V2.3 since the crop behavior changed to auto-crop to opaque areas (my assumption). Affinity behaves very special when using linked RAW and barrel distortion and rotation by crop. Only in this case, the edge areas impacted by barrel distortion get hidden after switching to Photo Persona, whereas cropped areas can be uncropped any time later. But you can re-develop the RAW and recover those areas. To see what I mean use move tool and unclip canvas.

I need to check on my Mac later how Affinity behaves in such extreme situations. Possibly a bug (on specific OS), possibly by design.

It should not take too much time to redraw from scratch with pen tool / pencil tool. create a new document place the source image reduce opacity to 50% now start drawing the shapes along the edge using the tool you prefer plan ahead the sequence of shapes, e.g. green magenta Brown light blue dark blue this allows to cover part of the edges of lower shapes, so you don’t need to model them exactly.

Hi, this effect is only a temporary split-second issue. The video may exaggerate the effect due to 50 hertz sampling and video compression. It happens often when you hit develop (apply) that effects like lens correction become temporary invisible and get replaced by the unedited RAW image. I would suggest to keep this separate, meaning ignore it for now as it is not related to the cropping issue topic discussed in this thread. If you want to discuss that detail, it would be better to create a new thread to keep everything organized.

Affinity allows RGB values between 0.0 and 100.0 But no display can render such colors values. There is a maximum nits value configurable in 32-bit preview. When memory serves me well SD displays typical 200-400 nits, HDR displays 800-1600. so you might get lightness values to 4.0 or 8.0 actually rendered, the rest can only be clipped. Depending on color profile of Display clipping may occour asymmetrical per color channel.

Any chance you can upload the file showing the issue? If Photo renders the same different than Designer, the issue is probably caused by HW acceleration. What happens if you switch view mode to pixel in Designer?

Hi and welcome to the forum. i cannot reproduce the issue, maybe i missed some details. can you give the exact x/y position of the pixel you are sampling from? which color picker do you use, the color picker tool, or the color panel picker? which OS, GPU, display do you use? is your setup HDR capable end-2-end?

hi Bernd, welcome to the forum. Just export the document to a bitmap file format like jpeg. If you want to edit the stacked images further in Photo, you may use merge visible or rasterize and trim.

The file is perfectly fine. The only issue: there is an active pixel selection, with a very low opacity value. this renders all brush strokes almost useless. You need to only use the menu command "Select->Deselect (CMD-D / CTRL-D)" once to get rid of the selection. Then the brush will work again.

Nice find. simpler set up: create new file add any layer, e.g. rectangle in blue add empty group layer on top add mask to group in masking position delete via brush from mask: mask escapes group and impacts layer below no matter which blend mode is used for group this issue exists in 1.10.7 and probably all v2 releases. to add more insanity: Remove mask layer add a pixel layer in masking position to group start painting on pixel layer you observe the rectangular bounding box around the painted content gets erased from lower levels. you may need to zoom for manual redraw. Canvas, layer thumbnail and navigator preview don’t match. classical Affinity „non deterministic behavior of alpha channel handling in layer blending“

It is rude from William to post such unwanted content again in this exact place where another forum member asked explicitly for an option to filter out spam like this. Can you please consider stopping this behavior? You are straining the nerves of many people by ignoring essential rules.

You need at leas 2 layers in the document to trigger the bug. Now I can reproduce.

Just ignore them. Unfortunately there is no blocking of threads opens by users on the ignore list. i think there are alternative browsers for forums like this who offer additional functionality. It can be done on client side with some scripting (I’m unable to do this myself).

As the image layer is nested to the group, the mask will impact this layer, too. if the mask should not impact the image layer, you can move it out of / below the group.

Hi, I tried to rasterize a pixel layer which has a blend range applied to make white areas transparent. To my surprise, the blend range effect does not get factored in the rasterization. What is possible is export to a bitmap file format and import again. Is there any other way to internally get the blend range factored in, meaning you get the blend range settings applied / baked in without exporting?

The perspective mesh warp tool works only on vector objects, actually the nodes which define the shapes or curves. It does not work on bitmap objects or fill content. This is by design. Use the perspective live filter from Affinity Photo instead. Unfortunately this live filter is unavailable on Designer on iPad in contrast to the desktop version of Designer