NotMyFault

The Min/Max Blur filter, when applied to a mask layer, in my view work exactly like the original author wanted. You can use them in "Quick Mask" to get thinner / thicker lines. So can someone with knowledge about Photoshop explain where you see any remaining difference? Please focus on missing functionality. Affinity UI can differ by far from PS.

To be honest, in my view the Develop Persona is overdue to an complete refactoring. It is almost useless - except to get RAWs as fast as possible converted into pixel layers. There are so many unsolved UI issues, and except initial exposure and lens correction, all edits can be done better (non-destructive) in Photo Persona. Want a crash? Select Blemish Removal Tool, set radius to 4096, click once. Photo is gone immediately. Yes, input is erratic, but apps must check for and clear erratic input instead of crashing. Several UI actions temporary remove all edits (info panel, cross-hair usage) > 6 month. Defringe quirks (on Windows), e.g. Remove opposite hue not working since >6 month. Defringe UI: Affinity tried hard (and successful) to mix up every UI element vs. Photo Persona Ignores most parts of Canon's "picture profiles" Low-quality CA removal (vs. Canon OOC and DPP) Destroying 3:2 aspect ratio by including 20-24 garbage edge pixels for 24 Mpx RAWs Every time i'm bored and try something in Develop Persona i found old or new issues. More to be discovered Missing ability to really create "recipes" (presets) and batch-apply to multiple RAWs.

For me the issue is nor bound to WB, but any adjustment. When creating a preset, it is "active" as chosen preset. Apply to develop the RAW to pixel layer. When re-entering Develop Persona, the last used preset is shown as selected, but it is not applied. To apply it, you need to select default (or another preset), and the select the saved preset again. It the becomes applied. So at this time i see only the UI issue that the last used presets is shown as selected, but is not applied before getting re-selected. So the best correction would be to always select "default" when re-entering Develop persona. I may have missed other issues you are trying to explain.

Hi, i don't expect that there is a build-in function in Designer. If you rotate a rectangle of size w*h 3*1 by 90°, how should the gradient look when rotated? compressed by factor 3, of cropped to 1/3? Assuming that the gradient should use the individual shape positions and stretch them individually (instead of a "global" gradient across the whole canvas) I have a draft idea which might get into you intended direction: The document used a procedural texture filter to create a black to white gradient, at first across the whole document. It can be limited to the layers size with a trick using the mouse. The document is currently limited to 100px (can be extended in a later version by adding a multiplier input) When the PT filter UI is opened by double-clicking it in the layer stack, you can set the origin point. Its x-value is used as starting for the gradient, the y-value as endpoint (on x-axes). A gradient map adjustment (or LUT for complex cases) can be added to change the B&W gradient to your target gradient. When rotating the vector shape, the PT formula always keeps the gradient in horizontal direction / x-axis. If wanted, i can add input values to select any angle. If someone finds the secret parameters that can provide the min/max x position of the nesting layer to the PT filter, it would be fully automatic. locked gradient.afphoto

Hi, it would help if you post the URL to the video and the exact time (mm:ss). Most issues with painting on mask can be solved by go to "brush" panel selecting a basic round brush resetting the brush in "more" resetting the brush parameters opacity to 100, flow to 100, hardness to 100 uncheck "protect alpha". It is hidden in my screenshot, click the small >> arrow below "1" at edge

Started Upload - 8 hours remaining at 10 Mbit/s

You need 8 semi-cycles.

Images look absolutely OK for me for the resolution. If you prefer a even crisper look, you may deactivate anti-aliasing for text layers. See discussion here:

This tutorial might help

Welcome to the forum. Unfortunately there is no direct replacement in Affinity Photo for this workflow. If you want to mass-process 200 images with priority on throughput (not quality), you may use some tricks. Instead of Developing images individually, you could create a New Stack, and add lots of RAW images (limit to 20 images initially to avoid issues) Affinity will run a simplified RAW conversion (no adjustments possible). Remove the stack Then continue to edit the image layers in Photo Persona Use self-created LUTS as a way to apply lots of adjustments in one step Use Macros to apply filters / adjustments which cannot be materialized in a LUT Use Export Persona to mass-export layers

OpenCL is on. I know i could turn it off, but i want the root cause to be investigated. OpenCL works kind of ok since introduced, except occasional buggy GPU driver versions and some bugs in Photo. Assuming a memory leak, as reports about this symptom are increasing. Issue is not directly reproducible, but it happens about once a day of relaxed app usage. Didn’t want to wait more that 5 minutes, as Photo did not want to crash on its own, and memory exhaustion speed was too slow for my level of patience

Photo is freeing when editing. DMP file is 12 GB, too large to upload. Available if you can provide upload link of sufficient capacity. Last edit action was adding a contrast / brightness adjustment to HF layer. Memory usage increasing until killing process after ~5 Minutes. Starting at ~0,5 GB, killed ~6GB.

Congratulations. You found one of the most wanted hated omissions of the Affinity suite. 😉

So true. But this is a adrenaline boosted race to provide the first answer - no time to consider details. As i entered my answer and heard the sound that @Old Bruce beat me by a split second i had to click "Submit Reply" before i could correct this obvious amateur mistake. At least i beat you by almost a full second 😂😂😂 including a screenshot

create text layer convert to curves use node tool set stroke, Dashed

Hi and welcome to the forum. Can you please provide the essential information according to https://forum.affinity.serif.com/index.php?/forum/78-photo-bugs-found-on-windows/#elForumRules As a standard measure, please deactivate OpenCL in Edit>Preferences>Performance

It is a bit complicated. OpenCl boost performance for those lucky guys (like myself) with a wide range of GPU models, correct (means non-buggy) GPU driver releases, and otherwise clean and current HW and OS configuration. Affinity is a totally rare example of an App fully capable to utilize your GPU. But this means it will consume maximum power, produce maximum heat for extended time, and is absolutely sensitive to every potential misconfiguration - especially insufficient cooling on hardware. The other apps named by you are mostly unable to fully utilize the GPU, never running into the issue. Affinity can be blamed for all open software issues on their side. But issues caused by hardware vendors, GPU vendors etc. should be addressed to them, not Affinity. If your race car got damaged while speeding over a pothole, its not the fault of the car manufacturer.

This could further reduce the pain, but not fully. Photo already has two safety nets included - 1000 step history and auto-safe in case of crash. But this does not help in case of file corruption, or app hangs (not crashing). I frequently start with 24 Mpixel 20-25 Mbyte RAW files, and after a few edits must deal with 1000 Mbyte afphoto files - saved without history, RGB/16. This is another unsolvable issue- the massive memory bloat of the file format. Load and store times are excessive- Photo uses a single core and a fraction of SSD IO Performance. The only way to solve this file corruption issue to make the file format robust, and especially ensure that every file what has been stored is actually sane and not corrupt. Could mean reading load file immediately after store (in separate sandbox to avoid collateral damage to open document) and giving option to save open document in other more robust format. this means more a sequence of edit steps similar to a database log, usable for recovery (and manual corrections)

The results could be identical. The effort to achieve the result could vary by a factor of more than 10x Lens tools gives an immediate preview, allows an stepwise approach: first rotation, then horizontal/ vertical. No interdependence between them when done correctly making it totally easy to align straight lines to a grid, with butter smooth slider moves or numeric input at ideal steps of 1/10px via ctrl-mouse wheel. after 1-2 minutes i get a perfect result with all edges within 1px of a perfect rectangle In perspective filter, every change to one node can influence several other nodes, leading to multiple iteration cycles until everything fits. The tool grid is distracting and must be deactivated every time. The initial position of nodes is sometimes unfortunate (e.g. document edges) The default „destination“ mode needs to be changed to „source“ every time. can only be used with mouse (no numeric input possible for 1/10px position adjustments) usually i spent several minutes while non-stop swearing Never the less, it is the more powerful tool for cases where the limited effect of lens tool becomes a constraint

I really miss a live filter in Photo Persona having this functionality

A vector brush does not result in a real vector object, It uses a bitmap for the brush aligned to a vector path. If you use a real vector tool like vector shapes, pen tool, text etc it will work. So you may try creating the patch shape on you own using the pen tool.

For similar reasons as we have blurring and sharpen filters resize with up or downscale convert between 8/16/32 bit in any direction convert between color formats in any direction B&W / threshold adjustment/ posterize filter and recolor / gradient map adjustments different blend mode categories …

Maybe intentionally Affinity leaves it to the user if he needs pixel-alignment or not. Both have totally valid use-cases. Affinity cannot distinguish between them or what the user intents. There are uncountable more functions where some users might need a warning. Other users may hate warnings unnecessary for them (e.g when closing Develop Persona). I share your frustration learning that you wasted hours based on app behavior that seems unintuitive to you. But maybe it isn’t Affinity to blame.

Tricky to give an advice. I would try to use the latest beta (before 1.9.2 retail was published) which can be installed in parallel to test this. Affinity said occasionally that „final“ beta and retail are code-wise identical, they use same version id. Similar, a new 1.10. beta could be worth testing. it totally depends on your risk appetite and how much time you can dedicate testing different versions. 1.9.2 seems a lot more stable to me than current 1.10.

The crop tool works good for simple cases, e.g only rotated. If you handheld the camera often it gets more complex when not held perfectly parallel to the subject I prefer using the Develop Persona and Lens Correction tools (rotate, horizontal and vertical) in combination with a grid. Actually i often use iPhone Apps like dropbox, PhotoScan (google), OfficeLens (Microsoft) for ebay items as these provide automatic straightening you miss in Affinity Photo. If required you can still edit in Photo.