Chip J.

w0w. After reading this thread, I deleted all of my Affinity software and all of the work I did while using it. Now I'm sitting back with a coffee, congratulating myself for my forward thinking in doing so. I mean, really, if the outfit is d.e.d., why bother any longer?

Can't be. I just used it an hour ago.

1.10.4 appears to have corrected the issues that I was having with funky square boxes and pixilation under 1.10.3..  Thank you.

1.10.4 appears to have corrected the issues that I was having with funky square boxes and pixilation under 1.10.3..  Thank you.

Same issue(s) with same graphics card.  Had to turn off hardware acceleration to work.  Did not have any issues with previous 1.10 version.   A lot of pixelations and square artifacts with latest upgrade. 

Same issue(s) with same graphics card.  Had to turn off hardware acceleration to work.  Did not have any issues with previous 1.10 version.   A lot of pixelations and square artifacts with latest upgrade. 

Thank you... I follow and thought I'd watched all of Olivio's videos, but definitely missed this one.     This is exactly what I was looking for.

NotMyFault - Thank you for the your response.  Switching to the "move tool" did the trick.  None of the other suggestions worked for me, but at least I do have a work around now. 
Affinity Team - While I now have a workaround, please look into this issue.  I also experience same issue with the "Levels" adjustment.
 

NotMyFault - Thank you for the your response.  Switching to the "move tool" did the trick.  None of the other suggestions worked for me, but at least I do have a work around now. 
Affinity Team - While I now have a workaround, please look into this issue.  I also experience same issue with the "Levels" adjustment.
 

I have the same issue, but its mainly lack of patience: it can take several seconds until the histogram gets displayed (>10).
What sometimes helps:
Switch to "move" tool" Click the yellow triangle in the histogram panel Open curves layer again Can you try again and wait ... a lot?

You are welcome, don't give up on Affinity Photo.  As I have found many times myself, it's usually user error.  🙂   This forum is a great place to get answers quickly.

Pedro,  check your brush settings.  I was able to recreate your scenario by lowering the accumulation to 0.  Try raising the the value to 100 and see what happens. See attached vid.
 
MaskBug.mp4

You are welcome, don't give up on Affinity Photo.  As I have found many times myself, it's usually user error.  🙂   This forum is a great place to get answers quickly.

Pedro,  check your brush settings.  I was able to recreate your scenario by lowering the accumulation to 0.  Try raising the the value to 100 and see what happens. See attached vid.
 
MaskBug.mp4

Hey @Igguk,
Welcome to the forums. I have split you off from the main thread so we can try and help you on a more personal level.
I'm sorry you've felt the need to remove the 1.9 update. You can roll back to the older version here - https://store.serif.com/en-gb/update/windows/photo/1/
However I would prefer to assist you with the 1.9 update. I'm not sure why it's slower for you—it should be much faster, especially with the OpenCL addition.
Could you kindly provide some basic info about your machine such as the graphics card and processor as well as the RAM. Also, if you could find out the current driver for your graphics card, that would be super!
You also might want to try disabling OpenCL from Preferences > Performance. What options do you have in the Renderer dropdown box?

Nice. Well done with an appropriate style. What is your problem? Maybe your problem could be solved. Do you expect help from anyone with your attitude?

There will be six full-length tutorials for launch on different astrophotography workflows 🙂 (and probably more in the future).

Hi All,
When much of the world went into lockdown last year we put a few things in place to try to offer some support to the creative community. In the big scheme of things they were fairly small gestures I guess, but we were quite overwhelmed by the positive feedback we received about it.
In particular the 90-day trial of all our apps provided a big help for people who may have lost access to their normal tools through their work or university, and offering a deep 50% discount on our apps was also greatly appreciated.
We reverted back to our normal trial length and pricing as those initial restrictions eased and the situation felt like it was improving. However here in the UK we are back in full national lockdown and in many countries restrictions are tight and livelihoods continue being severely affected as we deal with the second wave of this virus. For that reason, we have decided to re-introduce both our 90-day trial and 50% discount on all our apps and digital content (unfortunately the relatively small margins we have on workbooks means we cannot offer the discount on those). We have also reset the 90-day trial so anyone who took advantage of it before can do so again.
The thoughts of all of us at Serif remain with everyone affected by this crisis and we wish you all the best.
Ash

Welcome to the Serif Affinity forums.
For the display profile Photo will use whatever you have configured in the OS display settings.
What the Color Preferences in Photo control is the working color space and profile for the document, not for the display. And the color profile used for the document depends on how document is defined (8- or 16-bit RGB, 32-bit RGB, CMYK, Grayscale, or LAB).

I'm experiencing same issue with 1.8.2.  I'm using the Extract Detail Macro that Pedro Soares created here:   https://forum.affinity.serif.com/index.php?/topic/36265-extract-detail-macro/&tab=comments#comment-178831 

It too uses Vivid Light filter. Works fine on Jpegs, but creates colored artifacts on raw (NEF) files.  Problem disappears when I convert to RGB/8 bit.
 

Hi carca
You'll need to manually select this area, cut and paste it to a new layer, then flip this layer and rotate it to fit the area. I found after this the original image required come 'inpainting' to remove the missing pixels.
You can find this in the below screen recording -
2020-02-27 14-51-04.mp4
I hope this helps!

I've searched for and found a Affinity Photo roadmap on this forum, but it's dated 2015.  I was wondering if there is a current roadmap now that Affinity Photo released 1.7.1.

Hey jjg61, welcome to the Affinity Forums.
Do you mean you have sat and repeated this over and over for 2 hours or do you mean after 2 hours or so the crash will happen?

No, all of our shipping platforms are equally important to us.
I'm the lead dev for Windows here, as well as being responsible for implementing the GPU compute support. So I can assure you, I'm being neither dishonest nor amazingly ignorant.
We're not circumventing anything. Your example isn't what our application does, and assuming you're talking about YCbCr decoding using WIC and Direct2D,  then this isn't a cross platform solution, and it only applies to a tiny sub-fraction percent of what our application does.
We don't interact with GPU drivers directly.
This isn't true, see next...
If you run out of VRAM then the OS has to page from system memory which has an enormous performance penalty. If you want to access memory from a GPU other than the one you're currently running on, then you have to transfer it across the PCIe bus, to system memory and then back out across PCIe to the other GPU. Again, there's a huge cost there.
The reason they wrote Metal was to have a unified API for rendering and compute, that was as close to the 'metal' as possible (i.e. minimal abstraction around physical hardware). OpenCL does not cover the same functionality as Metal (OpenCL is purely compute, Metal is not), so you cannot even begin to compare them.
Direct3D abstracts the hardware and driver, the same as Vulkan abstracts the hardware and driver, the same as Metal abstracts the hardware and driver, the same as OpenCL abstracts the hardware and driver, the same as CUDA abstracts the hardware and driver (but for NVIDIA only).
You have to accept that there are differences in hardware, software, and ecosystem for macOS/iOS and Windows.
 
 

Perhaps offer two denoise algorithms:
1) Fast and ordinary one (default)
2) Slow and perfect one (option)
The ones, who select 2) have time to wait. The ones who do not care (1)), have fast develop times. Same strategy works well in DxO PhotoLab with ordinary denoise and prime denoise.