NotMyFault

Just to add that in Photo persona the destructive noise reduction filter is available, and despite sharing the same name with the live filter version, it works different and much better in my view.: it is far stronger in effect, the live filter effect is often barely noticeable . I would recommend to avoid the live denoise filter and choose one of the alternatives like destructive filter or develop persona.

Hi, several factors could lead to this:

Please look for the most current thread in the feedback section covering this topic, and add your voice there. This section where you answered is about bugs of the legacy V1 version, and 1. the behavior is not rated as bug and 2. V1 will not get any new features or bug fixes except for installation on new OS releases.

Hi, several factors could lead to this: The new document is A4 and uses millimeters as units. The png file uses pixel as units. Please change the units to pixel. Otherwise you may position layers on fractional pixel units, and this will cause blurriness and other issues, e.g. fractional pixels at right or bottom will be rounded up on export and show light or dark seams. use the transform panel (xfm) to inspect size and position. activate snapping, set to enforce pixel alignment, and deactivate move by whole pixels. Deactivate other snapping options (grid, etc) when moving pixel layers. there might be a color profile mismatch. It seems all files are sRGB, but please check the color profile of your display in windows settings. the A4 and PNG document might use different DPI settings. Please use the pixel grid, and rulers and check that the placed PNG file has the exact amount of pixels in x and y position. Zoom level is interpreted differently depending on context (calculated size in physical units like millimeters vs. actual pixel size on display). If you require pixel. Perfect files, always use pixel as units, round up document size to whole pixels, and use same DPI for all layers (placed files).

For unknown reasons, the live filter is weaker. Try the destructive/ non-live filter.

Or the simpler legacy video

https://www.youtube.com/@Affinitybyserif/search?query=frequency

Older experiments

I quick method: in the PT filter, delete the c variable, create it new with type "R" and set a number of 2. This will thicken the lines, but only to the right / down direction. Getting the lines thicker symmetrically will require more extensive refactoring. x y grid V2.afphoto

I will check, will be possible

Everything is a comprise, and it depends on the circumstances. In my perspective - and I could be wrong - those who want to get rid of preview - due to performance / waisted lifetime reasons - normally work more with Photo or Designer and exporting files is a relevant part of their workflow. Meaning you use export a lot. Then the export persona might give you additional benefits, and those quirks (don't know which specifically you have in mind) may not matter at all.

The workaround might get overlooked easily: export Persona does not have preview and probably solves the (performance) issue in many cases. Never the less, I support this feature request.

I switched from PC to Mac to escape all the Windows specific bugs, only to find out Mac has at least the same number of Mac specific bugs, some hurt even more: Editing Procedural texture formulas broken Handling of multiple displays broken numeric input by muse wheel often not possible Some keyboard shortcuts memorised from PC will bring you into trouble, like cmd-Q (for @) will quit most app

If you want to use the lightness value (black: hiding, white: revealing), just set a blend range on the pixel layer from 0/0 to 1/1 on source.

You can use any pixel layer as mask to make parts of a vector shape invisible. Just nest it to the masking position (not child / clipping position). The alpha values are used to mask the vector layer. All color values are ignored (taken from vector layer).

on Mac you can use only 2 stacks, one to each side of the canvas. It is not possible to use more than 1 docked stack at a single side.

created a document of size 256x256 and tested clipping an unclip canvas. After extending the canvas to 512x256, drawing a fresh copy of the checkered PT filter (by merge visible), rotating the layer with crop tool by 90° and later again to 180° (or back to 0°) unclip canvas was unable to reveal the correct document size. It clipped to 256x128px despite the layer is 512x256px and not stretched in any way. File saved with history. unclip canvas bug.afphoto

When you try to crop and rotate a RAW image in develop persona, the cropped area gets automatically set by Photo, but wrong in several aspects: Photo remembers the last used crop setting, which can be totally off from the current document E.g. for me the last remembered is 2:3 aspect ratio, but the actual image is 1:1. Even after applying a 1:1 crop, the default crop becomes 2:3 again. Could not find out to get a value I want as default. In case of 1:1 image and 1:1 crop: as soon as you start to rotate the crop, Photo automatically reduces the size of the cropped area, probably to cover the fully opaque areas. Unfortunately the calculation gets wrong very soon, especially if you rotate back gradually, the calculated size stays at a to low value. PS: affects Photo and Develop Persona, affects Mac and iPad. Screen Recording 2024-01-03 at 21.27.51.mov

Since 8 years an essential feature is not available: Please add the ability to rotate a document in Develop persona. For those who tried to rotate via crop tool in Develop persona: it does not work in a useful way

IMG_7575.CR2 1. Crop does not reveal out of canvas areas, no matter what value "Darken" is set. It does not help if the area is black or dark grey. What we need is revealing the area outside the canvas, similar to crop in Photo Persona. 2. When you increase the crop to get out-of-canvas areas visible, and then start to rotate the document or use straighten, crop tool resets to the original area without asking, killing your manual chosen crop area. This forces you into a 2 step approach (first increase size, apply, enter crop again, then straighten) and possible multipel iterations. TC 0:24 3. After clicking Develop, the cropped area differs from what you have finally selected in Develop persona. TC 0:29 Screen Recording 2024-01-03 at 20.45.01.mov

You are right that my comment maybe too harsh. I'm disappointed that affinity never fixes the root of an issue (e.g. layers become doomed if a coordinate gets to 0) e.g. by allowing to un-zero the coordinates again. Instead, it tries to fix the symptoms: change uncountable UI forms where you could enter zero intentionally or by accident. Or create zero by alignment. This strategy will never lead to a 100% fix. Affinity happily destroys documents by those corrupted layers, and keeps to complaint about proprietary file formats of Adobe and Camera vendors (RAW files). But it does not discloses its own file formats, does not provide tools to check consistency and repair damaged files, intentionally breaks compatibility of file formats to any older release.

The group layer size/position got damaged by the alignment. Once a layer h or w gets to 0, this is irrevocable and the layer is doomed, e.g. you cannot change the x position any more. Those zombie layer may corrupt all other edits. Affinity should fix the app so this never happens again (issue dates back to V1) allow to change a zero height/width to any integer number to rectify this (why the heck is this not possible)? if former is impossible: provide a check and repair tool within Affinity apps for files containing such damaged layers to minimise data loss (save all undamaged layers into new file) if former is impossible: remove the "professional" adjective from advertising.

The crop tool in develop persona acts erratic wrt the bounding box of the RAW layer. Steps to reproduce: open RAW file set lens correction / vertical to -100% activate crop tool adjust area by increasing crop rotate cropped area Expected: the automatic adjustment of the cropped area during rotation should show any meaningful relation to the RAW layer content Observed: the automatic adjustment of the cropped area during rotation seems totally erratic. It has no detectable relation to the actual RW layer bounding box or the edge between opaque and transparent areas, no matter if factoring in lens correction or not. IMG_7575.CR2 Screen Recording 2024-01-03 at 20.02.08.mov

Screen Recording 2024-01-03 at 19.50.39.mov

I hope the video clarifies the issue. RPReplay_Final1704306886.mov