NotMyFault

I would suggest to start with a less complex document. Use RGB only, not adjustments at this time. Stroke in mode "top". parent child clipping masking.afphoto

again, rendering bug caused by curves in CMYK mode.

you have added curve adjustments in CMYK mode, in a RGB document. bad idea. I strongly suggest to never use adjustment for anything in CMYK mode (either document or adjustment). Adjustments are only defined for RGB (Lab and GREY work, too. But CMYK is different). In CMYK, you have an inherent redundancy of K channel to CMY, leading to unexpected / wrong results in almost all cases. Don't use it. Except you totally know what you are doing, or intending to get "creative" effects.

The curve adjustment triggers an old unfixed bug. It seems to affect (erroneously) the alpha channel. When you switch to photo persona and channels panel, activate alpha channel. When toggling visibility of the curves adjustment, you see that about half of the canvas gets black. This is a bug.

Yellow: the adjustment affects the mask brush as expected … but why does the Mask not mask anymore? The mask is misplaced. Use the move tool and select the mask in layer stack.

The legacy tutorials are still available, unfortunately direct links no longer work.

Hi Conrad, i think you need to create a selection of the areas with dust, and save this as mask and/or spare channel. You can re-use this mask (selection from layer) and re-apply inpainting on any image (or use it for other adjustments and filters). Unfortunately the type of correction normally depends on content (e.g. brightness/ colors / blurriness by depth of field) which may change between images. Another hint: most cameras (at least Canon) have an option to create „dust delete data“, by taking a image using specific instructions. These data can then be used with Canon DPP to automatically correct RAW images. This is explained in the linked article, so superfluous.

Maybe depends on features used like RAW compression.

The child layer position (masking/clipping) influences how colors and alpha values of the child layer get used. in masking position: alpha values will impact the full canvas, unrestricted color values (e.g. RGB channels) are simply ignored. Only color values from lower layers incl. parent will be blended, but the alpha value impacts the blend results. in clipping position alpha values are clipped to the parent layer (where parent alpha is above 0) color values are used (blended regularly), but again clipped to the parent layer nonzero alpha pixels. this applies to all layer types (pixel, mask, adjustment, filter). there are some exotic edge cases (stack use alpha as binary values), and groups (including Layer layers, symbols, compounds) are beasts on their own.

Double post, we had this before.

This tool can help to convert some unsupported RAW formats (by Apple and Serif): https://helpx.adobe.com/de/camera-raw/using/adobe-dng-converter.html

YES, Apple will add support for Z8 some time in future, but Affinity will never add Z8 support for V1. So hoping for Apple is the only option for users who don’t intend to upgrade to V2.

Of course, after switching between Affinity and Safari, plus going to Affinity home screen to save the file, the issue is no longer immediately reproducible. Never the less, a get this ten times a day on iPad: rendering within Photo (or any Affinity app) suddenly goes crazy in multiple forms. Often showing freezed content (does not react to toggle layer visibility, view mode, zoom), or showing pure black canvas. UI elements react to user input, but rendering simply gives up. You need to go to home screen and re-open, occasionally more than once. Happens since V1, on 4 different iPads, on any iPadOS since 2019 until today on M1 iPad. Happens only on Affinity apps, no other App misbehaves in such a way wrt rendering. Happens on Mac Mini M1, too, but only about once a week.

Just played with the screenshots of your file on iPad. Made a new stack to compare the layers, and rendering gets erratic when switching layers in the stack (which changes nothing in the file). There are some rendering gremlins on all platforms. RPReplay_Final1695469888.mp4 rendering bug on iPad.afphoto

Probiere mal den zoomlevel zu ändern. Das triggert ein redraw. Und blende das Navigator panel ein - die Daumennagel-Vorschau hilft verschiedene Ursachen von Darstellungsproblemen zu unterscheiden. Zeigen beide das gleiche oder unterschiedliche Inhalte?

Enthält die Datei eine verlinkte Bilddatei, insbesondere RAW?

see This new Camera is not officially supported by the old Affinity Version. On Apple Devices, you can switch to Apple RAW and may have better luck.

In Designer, you can use „expand stroke“. This will convert the area containing a stroke into a filled area, and allow the layer to be used as parent for clipping. never the less, it would be best to not use strokes for defining areas. What you used to create something looking like a circle is just a very short straight line with ultra-thick stroke. there are „creative sessions“ videos where other artists explain there workflows, where you can find inspirations. https://youtu.be/GnjCYuVw3Y8?si=tavKF06YD_lbLc3e https://affinityspotlight.com/article/get-inspired-with-31-creative-video-sessions-for-affinity/

Add your full list of device specs. Mac or PC, external tablet, mouse, …. OS and patch level. All details matter.

We would need a full screen recording, plus the edited file, saved with history to reproduce. check you brush settings, including „more“ settings. check specifically wet edges, blend mode, protect alpha, color, color transparency, layer transparency. any time you think a brush mis-behaves: Start screen recording the full edit session add a pixel layer set pixel layer to solo mode / isolation mode use the brush to make some strokes. Inspect this layer carefully. create a new document (rgb/8, reasonable size below 4K), repeat. save all documents incl. history. try again, select a basic round brush of 16 or 32 px

More specific, create a black to white gradient brush as explained her then you can add gradient adjustment to colorise as you like it gradient hor brush.afdesign

I don't see any bug. The PDF contains an image layer which is stretched to the extremes. Depending on zoom level, you will see rendering artefacts caused by bilinear resampling. Works as designed for me. Apple Preview creates almost identical preview. Just change the zoom level to see all the to be expected rendering artefacts.

The main criteria for the parent layer (to allow a clipped child layer becoming visible) is actually: the curve must enclose an area. Open curves are kind of automatically closed by a straight line from end to start node. The actual colors for fill and stroke do not matter (except coloring that parent layer - no impact to visibility of child layers) The stroke is always added in the specified order. So it is correct that a stroke in the wrong order may cover the clipped child layers with its color. If you use a semi-transparent color, child layers will shine trough partially. it can become more complicated by using Layer FX or appearance panel / multiple fills and stroke, or by using vector brushes in Designer, or by using arrow heads as decoration. The „dual personalities“ of curves wrt their fill (enclosed area) and stroke (additional coloring along the curved edge) are a fundamental principle, but the rules are sometimes unintuitive and leading to unexpected results.

I Hope it is now clear why the method you used does not work in the way you expected. Do you need support to find a new/better method to achieve the desired results?

Ideally, you would take images using a tripod, and a telephoto lens. All images should overlap at edges, and the angle you rotate the camera must be small. Images with wide-angle lenses are not suitable for stitching, as the distortions would be too large. E.g. straight lines would not be straight when covered in 2 images. Moving the tripod to diffrent position is another no-go. you can shoot hand-held, but try to mimic the tripod as close as possible.