NotMyFault

Hi, the mostly used workflow is to keep edits in Develop persona to the absolute minimum. This will reduce the chance that you have to "make further changes to the RAW image" to almost zero. Besides the technically required conversion from RAW to RGB pixel layer, almost all other edits can be made in Photo Persona (or Tone Map Persona), and non-destructively. This is the charm of Affinity Photo that most edits can be done nondestructively. So use Develop Persona only for: Initial exposure adjustments (including shadows & highlights) Lens correction CA correction But nothing else. Then use Photo persona for the rest. If required, you can simply re-edit in Develop Persona, but this might conflict to some later changes.

You are right that i could not reproduce any "faulty" rendering. It would be great if you could take screenshots (or save "merge visible" layers), but please describe the exact context how they were created. If you get different results on MAC, this is certainly a bug. Never the less, to make the potential issue more clear and reproducible: Below i made 3 layers to compare side by side: 1. left: your "issue statement", blend of "Merge Visible" and "Alpha Zones" layers. Red is darker because alpha increases to 177 from 114 by alpha compositing. As this is the only area where i spotted the color changed described by you, my first answer relates to this area. If there is another color change, i misinterpreted your post. 2. middle: "Merge Visible" layer 3. right: "Alpha Zone" layer. 2 and 3 look absolutely identical, the info panel shows identical RGBA values (3 samplers positioned into the semi-transparent area)

I think this is by design and expected (not a bug), based on the blend formula. Ares = 1- (1-A1) * (1-A2) https://en.wikipedia.org/wiki/Alpha_compositing so from 114 you get 177 (using 114/255 to normalize range) The next topic is by design, too: If you want to create a selection from the mask layer (Curves Adjustment), you can select the adjustment layer (not the pixel layer) and use Select>Selection From Layer Can you explain? Channel mixer works perfectly fine, but the resulting effects could be un-intuitive.

Nice to see 3 different renderings (2 views and navigation panel): 1: 0% 2: 50% 3: 100%

It seems that coverage maps do nor work for pixel layers (other than the default map). vector pixel anti-aliasing issue.afphoto

Hi, i reported a similar issue before, but cannot find the report right now. In Photo the UI for "coverage map" and "save profile" is still slightly broken. You can now save one profile, but "delete" (by clicking the small "x" in the profile) has no effect after having stored 1 profile, if you try to save another, it does not show up (but it is stored and visible in the stroke UI). Sometimes it shows up after closing / selecting a different layer / re-selecting layer / reopening the UI

Just press "add preset" - its at the bottom right in you own screenshot.

Unfortunately this is not possible. The gradient editor is part of the gradient map tool. It is not the same tool as the fill tool. These are two completely independent tools - of course they can be used atop of each other. To summarize: step: add a fill, and select e.g. a linear fill, from black to white. A fill can (must) be applied to an existing layer, or a (new) fill layer. step: add a gradient map. This will show up as a separate layer in the layer stack.

Hi, when you adjust the "Output Black Level" of the Levels Adjustment (on alpha channel), Photo renders wrong: Depending on zoom level, a rectangular bounding box gets impacted. When you merge visible, the complete canvas gets impacted. Tested on W10 and iPad with same results. Bonus question (bug or feature): Why can the levels adjustment nested to the vector shape impact any pixels outside the vector shape? nested levels on vector shape bug 1.10.0..afphoto

Gradient fill (using the fill tool) on text layers works perfectly fine for me. gradient map is a completely different animal. Do you select the right tool? You could press the question mark on the bottom right to see the description of the symbols. https://affinity.help/photoipad/English.lproj/pages/Clr/gradientEditor.html To edit the gradient, just click one of the nodes and change the color via the normal color studio.

I can confirm that the issue occurs on my Windows 10 PC with 1.10 by just applying any of blur/sharpen/median tool once in the middle of the picture. So no partial alpha is required. Once you have advanced to the state, no operation (except undo) gets you out of the state. Seems it triggered a flag which cannot be reset. But 1.10. once again is showing an issue started with 1.9 that the preview rendering of some adjustments (like blur brush) is wrong (transparent instead of actual preview), see

The new versions shows an old issue: The blur tool shows a transparent circle instead of the effect preview while hovering. When click-dragging, the effect is applied correctly. 2021-08-08 14-21-45.mkv

I would start with two lines of text (upper and lower), rasterize them individually Put a circle/ ying yang curve as helper layer at the bottom use mesh warp tool to distort the pixel layers with text (one after each other) until happy Never the less, i assume the letters are either hand-crafted curves, or a special tool (not Affinity) is used to create this effect. Other options is to experiment with recangular-to-polar filter, after carefully crafting the text layer.

I think this might be another symptom of the known bug handling alpha channel with nested layers targeting alpha channel. Did you try on latest beta? Currently traveling with iPad only, there (1.9.2) i cannot reproduce this issue because of the older bug overshadows your issue. Workaround: adding a group to the pixel layer, and applying the blur to the group.

Könnte etwas mit dem MS AppStore und dem genutzten Konto zu tun haben. Ggf. abmelden/neuanmelden probieren.

Hi, The menu item to change the stack mode does not fit on screen. iPad 5 / 2017 all screen settings e.g. text size are default

+1

Levels, curves and channel mixer can be used to specifically target alpha channels And not to forget procedural texture filter

Changing opacity on group or individual layer by design leads to different results, see example below. Untitled.afdesign

Below an oversized (>256000 px per side) file which is not crashing Untitled.afphoto

That’s interesting. Do you get an error message? I’ve experimented a bit and you can use the crop (and zooming out) tool to create even large files (on iPad) But I don’t know if the documents handle correctly or you run into an issue later. It seems there is an 32bit value limit for vector objects: I create a 256000x10000 rectangle and then used to transform tool with “coupled” x/y to increase. Above 80000 for y, the x got truncated.

When using RGB32 color format, Photo shows the exposure/gamma correction dialog. Unfortunately, for exposure only the digits left of the comma are shown. On Windows, Photo has a slider which gives more information about the chosen value. On iPad, values are rounded/truncated so it is hard to spot if you change the slider by accident. I recommend to show 2 decimal digits for exposure, just like the gamma value.

On IPad, you can create documents with up to 256000 pixel height and width. When you use crop (in Pixel Persona), it shoes 65535.0 constantly, until you shrink the area below this limit. Higher values entered manually will be truncated to the max values. It seems crop tool uses a 16bit unsigned max value to show the pixel dimension. The crop itself seems to work correctly. Tested with a fill layer and gradient fill from black to white. PS - Photo is able to create vector shapes up to 2^31 (signed 32 bit integer) Photo can handle much larger pixel sizes for vector shape, and by unzip canvas create larger documents. But after created such a file with a vector shape positioned at the edge, so that it reached out even beyond, Photo Beta crashed while attempting to save the document again. Warning: the attached file crashes Photo immediately oversized.afphoto

There is currently no way to inverse a vector mask directly (based on unsolved issues). Never the less, if you follow the process described in the tutorial, it will work perfectly (using groups, blend ranges and blend mode erase). As this thread is about the tutorial, i would suggest that you create a new separate topic under „questions“ to keep everything organized.

You could try displace filter in combination with a crafted layer