[AMD Radeon RX Hardware Acceleration]

Good to know, thanks.  Performance seems to be much improved with live filters.

[AMD Radeon RX Hardware Acceleration]

Just wanted to report that I just installed V2.1.0.1799 and saw a very large improvement in benchmark results with my AMD Radeon RX5700.  Thank you to Affinity Developers!!

 

 

 

[AMD Radeon RX Hardware Acceleration]

Disappointing

CPU Ryzen 7 3700x

GPU AMD Radeon RX 5700

36 TB M.2 SSD

 

[AMD Radeon GPU OpenCL poor perfomance]

Continues to be an issue with me as well.  Disappointing this was not resolved with this major update.

 

AMD Ryzen 7 3700X

AMD Radeon RX 5700

32 GM RAM RAM

1 TB M.2 SSD

[AMD Radeon RX Hardware Acceleration]

Thanks Mark.

[Create manually Frequency Separations layers]

Not available in the Windows Beta yet.

[AMD Radeon RX Hardware Acceleration]

@Mark Ingram Thanks for responding.  Happy Easter!

[AMD Radeon RX Hardware Acceleration]

@walt.farrell I was hoping there might be some progress to report, other than waiting on AMD, particularly since GPU acceleration seems to be fine for my card in other graphics programs.  Might Serif be working the issue from their end as well?  Just a thought.  Mind you, this has very little affect on my use of AP.  I just get hopeful when I see a new release.

Kind Regards.

[AMD Radeon RX Hardware Acceleration]

Version 1.9.2 did not correct this issue.  Would it be possible to get an update on the progress toward resolution?

Thanks.

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

@Subclavius, I was trying to stay optimistic.  But you wonder if AMD even knows Affinity Photo exists.  

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

Ok.  I see the note in the Release

• Disabled hardware acceleration for AMD Radeon RX 5000 series and later cards (awaiting response to bug filed with AMD)

I hope the contact with AMD is fruitful.  Please keep us updated on progress.

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

Now with the 1.9.1 update I get the following message indicating my configuration is not compatible with hardware acceleration.  Is this because I have Windows 10 Pro and not Windows 10.  If so, will this be addressed.

 

Thanks.

 

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

@Mark Ingram, I certainly agree it would be great to be able to utilize my GPU.  The issues occur regardless of what type of what file or what type of file is being loaded.  The load time is at least an order of magnitude slower when OpenCL is activated.  Attached is an example file.  One is a tif and one is an raw NEF.  Here is a description of the behavior I see.

Start AP, attempt to load a raw file for the first time.  Loading of the raw file happens in stages.  The first stage takes about 20 seconds.  At the end of 20 sec. I see a rather grey representation of the final raw image.  After 30 additional seconds (50 seconds total) I see a proper representation of the raw image.  After the raw image is loaded and while in the develop persona, if I attempt to use any slider, e.g., exposure, the firs time, it does not move.  But upon a second click and drag, it will move properly.  This happens with each slider.  Sometimes clicking between different tabs in the develop persona, causes the system to freeze.  Sometimes closing the undeveloped file causes the system to freeze.

In the same session as above, (without having closed down AP) if I load the same NEF file, it will only take 2-3 seconds to load fully and the sliders seem to respond properly.

The first time I attempt to load any tif file (as the one attached), it will take 10 seconds to fully load.  Again, when attempting any adjustments for the first time, the slider movement is delayed by a second or two.  After that, they seem to "loosen up."  

During the same AP session, after loading one raw and one tif file, loading of any subsequent raw or tiff  seems to be normal (about 3 seconds for a raw file and 1 second for a tif).  If however, I  close down AP and open it up fresh, the same slow behavior occurs the first time files are loaded. 

Of course, if I turn off OpenCL, all files seem to load quickly (about 3 seconds for a raw file and 1 second for a tif). 

Hope this is helpful in tracking down this issue.  Thank you again for your attention to this.  Let me know what else I can try to assist.

Have a great day.

_7105251.NEF _7105251.tif

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

Also, interestingly, like @Subclavius,I am also running a Ryzen 3700X CPU.

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

@Mark Ingram 2 Benchmark screen shots are attached.  The first is with OpenCL ticked and the second is with it unticked.

Thank you for your attention to this issue.

Regards.

[1.9 slow]

Have same issue with OpenCL activated with AMD RX5700 GPU.

[OpenCL Activation Slows AP 1.9 for Windows with AMD RX 5700 GPU]

First, thank you to the developers for all their hard work in bring us 1.9.

I've reported this issue several times on the 1.9 Beta, going back to November.  Running AMD driver 20.12.1 on a RX 5700

Loading documents into both the Develop  and Edit personas is slower.  For example, loading the same 24 MB tif file took about 0.2 sec. for AP 1.8 and about 5 seconds for AP 1.9 (when accelerated). 

Moving between the Tabs (Layers, Adjustment, Effects, Styles) caused the program to not respond for about the 30 seconds.  These issue do not occur when hardware acceleration is disabled.

I'd like to know if there is any effort underway to resolve this.  

 

[Hardware Acceleration is v. 1.9.0.852]

I have an Huion Tablet driver installed, but don't use the Tablet much in AP.  As I said, the most obvious issue for me seems to be loading files.  I would say this takes on the order of 10 times longer than when OpenCL is disabled.  Not sure how a Tablet driver would be having that effect.  Based on @VolkeMB comment above, it seems that this might be related to the AMD GPUs not being handled correctly in AP.  Hopefully, one of the developers can get their hands on a Radeon RX 5700X and see if they can recreate the problem. 

[Hardware Acceleration is v. 1.9.0.852]

Now Running Beta 1.9.0.911 with AMD Driver  20.12.1 and still having the slow and lagging performance, particularly when loading files.  Unticking Open CL corrects the issue.  If I monitor my GPU, it is clearly being utilized.  However, it takes on the order of 30 seconds to load a raw file.  Once, loaded, this Beta version, seems less laggy than the previous versions, but I can't quantify this.

[Import from darktable in linear prophoto colorspace seems not be properly implemented]

Thanks for the response.  Darktable is implementing a linear workflow as their preferred raw development method (filmic RGB module).  I suggest Affinity Photo developers check it out as I suspect many Affinity Photo users may use darktable to develop raw files non destructively, before doing additional work in Affinity.

[Hardware Acceleration is v. 1.9.0.852]

Now Running Beta 1.9.0.885 with AMD Driver  20.12.1 and still have the slow and lagging performance.  Unticking Open CL corrects the issue.

[Import from darktable in linear prophoto colorspace seems not be properly implemented]

Walt, thank you for you quick response.  You make an excellent point.

When it comes to colorspace and profiles, I am out of my depth.  I'm not sure linear profiles are limited to 32 bit.  At least that doesn't seem to be the case for darktable's raw processing.  Nonetheless, the only built-in Prophoto profile in darktable is linear.  It would appear that AP isn't recognizing this profile.  I am not able to locate the linear prophoto profile in the darktable installation files in order to provide it to AP.  As a work around, I have taken the ROMM RGB profile from AP and loaded it into darktable as a new output colorspace.  This seems to have done the trick.   This seems to give the same result as converting the file to ROMM RGB within AP.  I am also able to convert from linear prophoto to ROMM in ACDsee and Krita.  However, Krita seem to be able to recognize a correctly display the linear prophoto profile.  In the end, I am unlikel to work in ROMM very often, but wanted to be able to in there was a need.

Thanks again and Happy New Year.

[Import from darktable in linear prophoto colorspace seems not be properly implemented]

I exported from darktable a 16Bit tif in linear prophoto rgb colorspace.  I opened this document in AP (first attachment as screenshot).  AP seems to be crushing the blacks with a purple cast in the shadows.   I've opened the same file in several other programs (Capture One, Capture NXd) and the file seems to be rendered much closer to what it does in darktable.  Then I convert the file to ROMM RGB and it seems to lighted the shadows and remove the color cast (second attachment as screenshot.  Is it possible that AP is not recognizing the tif file color space properly, i.e., it doesn't recognize linear prophoto rgb as ROMM RGB?  I've also attached the 2 tif files.   

DSC_2409_Prophoto.tiff DSC_2409_ROMM.tiff

[Hardware Acceleration is v. 1.9.0.852]

Now Running Beta 1.9.0.876 with AMD Driver  20.11.2 and still have the slow and lagging performance.  Seems like the Beta doesn't like my RX 5700 GPU.  Unticking Open CL corrects the issue.

[IMPORTANT: Annual Company Closure 2020]

Merry Christmas.