NotMyFault

It would be really great to get „crop to opaque“ for every crop tool (dev persona, photo persona) and not only during „panorama“

I’m a long time user both of Affinity Photo and Canon DPP, CR2 files are generally supported in AP, but once in a while I get some issues with CR2 files. Exposure settings get way off initially, and results for denoise could differ in details. And there is no simple way to copy settings to multiple pictures. As a workaround, I will do the raw development mostly in DPP and export as 16 bit TIF. This makes it easy to get consistent results for multiple photos quickly (e.g. exposure adjustment, white balance), as DPP can create “receipts” and apply them quickly to multiple raw files. And previewing / star rating is a bunch of pictures is not available at all in AP. In case of focus merge, it is actually recommended by Serif to pre-process raw files to get better results For advanced work I then continue with AP.

Hi Brakus, maybe a Dust & Scratches Filter will help? Used Radius 2 Pixel and 9% tolerance (on iPad, same is available on Mac or PC)

Files are Uploaded.

Hi Chris, yes according to the settings:

When i start with pre-processed TIF instead of CR2 files, sligthly different issues occur: 1st source image is shown completely black no white box in focus merged picture histogram shows artefacts Using mouse cursor shows artefacts

Picture shows distorted cursor. Should be a white circle.

Hi, there are some remaining issues when focus stacking. Behavior has improved with every beta, but still needs some polishing. At least display is errornuous in several aspects: 1 white rectangle shows up 2 one source images shows artefacts from focus stacking process (_MG_8488.CR2) 3 trailing underscores "_" in source picture names do not show up (this is default naming scheme for canon RAW files using ARGB profile) 4. Cursor is dirstorted (will upload 2nd picture, impossible to screen capture, must use external camera to take photo)

disregard / wrong topic

Another tip: before using color-based selections, check if your document is at least 16bit color mode. In 8 bit modes, selection can become erratic (all or nothing)

Another option in your case: the background seems totally black. You may use selection by color of the background, then invert selection. Could provide better results.

A general tip when selecting on low contrast images like this : just add an brightness/contrast layer and push its settings quite a bit to increase contrast as far as possible. you may use HSL to boost colors, too. then merge visible. the resulting layer can then be used for selection. after having a good selection, simply hide or delete - then apply the selection to the original layer. using this helping layer will give you much more visible feedback of you selection.

@carl 123: The curves layers are the root cause for the slow down. Of course, disabling them makes Photo faster. But this is not the solution, it only describes the bug. slow_selection.afphoto

Hi carl123, the original file used in the video was quite large (>600MB), and failed to upload to this forum. To reduce file size, i copied only the relvenat layers into a new file, and verified that the issue occurs with the smaller file. Upload failed again, so i finally switched to the amazon drive link. I tried the same file with my iPad 2018, it is much faster vs. Windows, but still shows some slowness (below 1 second) I observerd similar issues more than once with older Affinity Photo releases, my high end PC is by factor 10-30 slower than the iPad in many situations, e.g. when switching to tone map persona. It is way faster in all other aplications, e.g. web browsing, video editing etc. Performance clearly depends on file size (megapixel count, color depth e.g. 8/16/32).

Are you using the latest release version? yes Can you reproduce it? yes Does it happen for a new document? If not do you have a document you can share that shows the problem? https://www.amazon.de/clouddrive/share/iQJ8gbNrwzgJCxGzsQaOolSRTuTpgQKiqroeS0Jr4pb If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following: What is your operating system and version (Windows 10, OSX Mojave, iOS 12 etc)? Windows 10 1909 What happened for you (and what you expected to happen) there is a lag of 1-5 seconds between mouse mouse movement and visible effect i expect no noticable lag, or maximum 150ms Provide a recipe for creating the problem (step-by-step what you did). use sample image above select lowest pixel layer select "selction brush" select any area, e.g. one of the beach seats press left mouse button, move mouse to cover a small area, release mouse button wait for Photo to make selction visible. it takes much too long Screenshots (very handy) or a screen capture/video. https://forum.affinity.serif.com/applications/core/interface/file/attachment.php?id=136382 Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers. no. plain vanilla PC Nvidia Gforce GTX 1080 OS Name Microsoft Windows 10 Home Version 10.0.18363 Build 18363 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name System Manufacturer MEDION System Model ERAZER X7731 D/C485 System Type x64-based PC System SKU ML-110000 10021768 Processor AMD Ryzen 7 1800X Eight-Core Processor, 3600 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date American Megatrends Inc. P2A4W0X.206, 12.06.2018 SMBIOS Version 3.0 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer MEDION BaseBoard Product P2A4-EM BaseBoard Version 1.0 Platform Role Desktop Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale Germany Hardware Abstraction Layer Version = "10.0.18362.752" User Name Time Zone W. Europe Daylight Time Installed Physical Memory (RAM) 32,0 GB Total Physical Memory 31,9 GB Available Physical Memory 21,7 GB Total Virtual Memory 36,7 GB Available Virtual Memory 22,7 GB Page File Space 4,75 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes Did this same thing used to work and if so have you changed anything recently? (software or hardware) yes, befor upgdating Affinity Photo from older release (still 1.8.3.xxx)

Hi @Gabe, i hope only the image was missing.To reproduce, select the lowest pixel layer, use selection brush, and try to select any portion. Selection lags about 3-5 second behind the mous movement. record_000003.avi

Dear team, after upgrading to latest release, performance issues with selections start again. While using selection brush, flood select tool, or refine mask, Photo becomes totally sluggish and freezes many times. Issue most severe after adding filters / adjustments above the pixel layer. I'm talking about 2 curve layers, not 10 or 100 layers. Example file can be downloaded https://www.amazon.de/clouddrive/share/iQJ8gbNrwzgJCxGzsQaOolSRTuTpgQKiqroeS0Jr4pb For video, see post below. RGBA/32 Widnows 10 latest lots of free CPU, RAM, and GPU power

It is possible. Just change the “channels” from “master” to ”alpha” and the curve will affect the mask instead of image.

when using a mask, and reducing the opacity of the mask, this will always recude the opacity of the underlying layers, instead of increasing. This behaivior does not make any sense to me. Masks are used to filter out unwanted parts. When you reduce the mask's opacity, you want to (temporary) reveil the hidden parts again. You can disable a mask only completely, but in many cases you want to reduce only the power of the mask by e.g. 50%, meaning black pixels in the mask should act like 50% gray when the mask's opacity is set to 50%. In the moment, i found only a complex workaround: adding a curves adjustment to the mask, select the "alpha" channel, and lift the left node from 0 to e.g. 50%. This requires several mouse clicks, and works only if the mask is not nested, because Photo does not allow to add layers to masks when a mask are already nested. To summarize: If i set the opacity of a mask layer to 50%, this should show an effect equivalent to an alpha channel curve layer to the mask, where the lower left node is set to 100% minus opacity. The attached file shows the results of Affinity Photo when setting the opacity of the mask, or the underlying layer to 100% or 50%, and the simulated result i would expect. To be honest, the reults are really confusing to me. Same results with AP 1.7 and 1.8 beta. mask opacity bug 2020.afphoto

You can see the issue with this file. (de-)activate the curves adjustment to see the difefrence. Tested on iPad (2017) and iPad pro (2018) mask opacity bug.afphoto

When using masks with opacity, in combination with an adjustment layer (which supports alpha, e.g. curves) to the mask, the opacity does not affect the mask, but the layers below the mask. Trying the same on the PC version (1.7.3.487) gives correct results: adjustments affects the mask.

Afphoto file used do demonstrate issue It seems the opacity of the mask is wrongfully applied to the layers beneath when a filter is added to the mask mask opacity bug.afphoto

Hi there, observing strange behavior when combined masks, transparency for the mask, and additional live adjustments or filters to the masks. Every adjustments/ filters which support alpha is affected, e.g levels, curves, gaussian blur, minimum blur. 1. if you use a mask layer, you can use the opacity to reduce the masking effect, e.g. to see what will be masked out. opacity 100 shows only pixels with white mask, and no pixel with black mask. opacity 50 shows pixel with white mask, and 50% transparent pixel with black mask. 2. when you add an adjustment or filter to the mask, even with all parameters at zero, the result changes: now all pixel with white mask will be shown 50% transparent, and pixels with black mask will vanish. 3. Is this a bug or a feature? FullSizeRender.mov

@Daniel: Tank you for those suggestions. I’m already aware of several workarounds, please do not post more of them. These are non-precise and hamper the workflow . In my view this is a AP bug and should be fixed. Whenever I applied crop with e.g. 3:2, AP should respect this ratio and automatically calculate even pixel counts during export with locked ratio. Other applications behave like this, AP should do, too.

@Danielcz: This might work in theory. My expectation to AP is that the software does the math for me Really don’t want to do that manually