AMD Radeon RX Hardware Acceleration

[Tormy]

UPDATE

Partially solved with the last update of the RX590 drivers, published 1-2 days ago.

I say Partially because deactivating the use of the GPU, the three packages of Affinity: work.

By activating it, some hiccup is still occurring and it's frequent. not workable.

Now it's your time to release a real working packages with AMD.

[Photo amateur]

Not nice that the hardware acceleration with update 1.10.3 still doesn't work with my AMD Radeon RX 5700XT. I hope you can get it under control one day. Obviously, the focus depends on it. After the RAW development, the sharpness is out of the picture again.

[Photo amateur]

Not nice that the hardware acceleration with update 1.10.3 still doesn't work with my AMD Radeon RX 5700XT. I hope you can get it under control one day. Obviously, the focus depends on it. After the RAW development, the sharpness is out of the picture again.

[walt.farrell]

35 minutes ago, Thorsten Photo Worker said:

Not nice that the hardware acceleration with update 1.10.3 still doesn't work with my AMD Radeon RX 5700XT. I hope you can get it under control one day. Obviously, the focus depends on it. After the RAW development, the sharpness is out of the picture again.

If I understand what you mean, that does not sound like something that would be the fault of not having hardware acceleration. Hardware accelerated or not, the sharpness of the Developed images should be the same.

Have you discussed that problem elsewhere in the Questions or Bugs forums? There could be a bug, or there could be a user error, so I would start with Questions if it's not already discussed somewhere else.

[Eroica]

Any update on a possible fix?

[Tormy]

On 10/26/2021 at 8:55 PM, walt.farrell said:

If I understand what you mean, that does not sound like something that would be the fault of not having hardware acceleration. Hardware accelerated or not, the sharpness of the Developed images should be the same.

Have you discussed that problem elsewhere in the Questions or Bugs forums? There could be a bug, or there could be a user error, so I would start with Questions if it's not already discussed somewhere else.

It's a bug. Somewhere in the forum I read Serif is studying a solution for such bug that it seems due  AMD.
Meanwhile AMD released several drivers updates. But Affinity still buggy . Now it's better, but not fully solved.

[Lukeslab]

I still get the error.. is there a solution?
I'm on:
AMD studio drivers 21.Q3
Affinity suite version: 1.10.4.1198
WIN:
Edition    Windows 10 Pro
Version    21H1
Installed on    ‎07/‎01/‎2021
OS build    19043.1320
Experience    Windows Feature Experience Pack 120.2212.3920.0

 

[Komatös]

4 minutes ago, lukeslab said:

I still get the error.. is there a solution?
I'm on:
AMD studio drivers 21.Q3
Affinity suite version: 1.10.4.1198
WIN:
Edition    Windows 10 Pro
Version    21H1
Installed on    ‎07/‎01/‎2021
OS build    19043.1320
Experience    Windows Feature Experience Pack 120.2212.3920.0

 

 

I don't think you read the opening post. Otherwise you would not have had to ask the question.

With AMD graphics cards of the 5000 series and newer there are (speed) problems with the real-time compilation of OpenCL code.

[Lukeslab]

48 minutes ago, Komatös said:

I don't think you read the opening post. Otherwise you would not have had to ask the question.

With AMD graphics cards of the 5000 series and newer there are (speed) problems with the real-time compilation of OpenCL code.

Sorry but I've read it and a few things here:
- Opening post is from Feb 2021 (nov it's novemeber)
- Opening post claims this as temporary BUG
- 21.Q3 drivers were updated on September 15th by AMD
So I belive there is some space for an update on the situation.

 

Edited November 8, 2021 by lukeslab

[Komatös]

30 minutes ago, lukeslab said:

Sorry but I've read it and a few things here:
- Opening post is from Feb 2021 (nov it's novemeber)
- Opening post claims this as temporary BUG
- 21.Q3 drivers were updated on September 15th by AMD
So I belive there is some space for an update on the situation.

 

If there was a solution, it would have been communicated in the initial posting.
 

[Subclavius]

@lukeslab, I am also watching the AMD graphics driver releases.  Not one of them to date has mentioned OpenCL so it's presuambly still under consideration by AMD.  There's probably little Serif can do to speed things up.  There is a post where this problem has been reported to AMD: https://community.amd.com/t5/opencl/slow-kernel-compilation-speed-clbuildprogram-with-radeon-5700-xt/td-p/448144.   The last update in that post from AMD was 16/02/2021.  @Mark Ingram says that Serif is in touch with AMD, dated 02/07/2021.

It's incredibly frustrating but there it is.  The error message from APhoto could be more helpful.

[Tormy]

On 11/8/2021 at 8:25 PM, Subclavius said:

@lukeslab, I am also watching the AMD graphics driver releases.  Not one of them to date has mentioned OpenCL so it's presuambly still under consideration by AMD.  There's probably little Serif can do to speed things up.  There is a post where this problem has been reported to AMD: https://community.amd.com/t5/opencl/slow-kernel-compilation-speed-clbuildprogram-with-radeon-5700-xt/td-p/448144.   The last update in that post from AMD was 16/02/2021.  @Mark Ingram says that Serif is in touch with AMD, dated 02/07/2021.

It's incredibly frustrating but there it is.  The error message from APhoto could be more helpful.

Yes they are in touch but nothing is at the moment touched 😛 I still have issue with my Radeon. Ok it's not the suepr-duper card, but it should work. It doen't.  Let's still hope and see

[Rafael Rivera]

Had to disable OpenCL acceleration to get Affinity Photo to stop crashing. RTX 3090. Just throwing this out there, just in case your software-only logic is missing a GPU model/sku.

[DenisD84]

Guten Morgen

es gibt jetzt mehrere Anfragen, wann es eine Verbesserung geben wird. Entweder kam lange Zeit nichts oder es wurde immer gesagt, womit man in Kontakt steht. Es sind jetzt mehr als 9 Monate. Ich habe für Software bezahlt, die nicht wie versprochen funktioniert. Mein Workaround sieht so aus. Auf dem IPAD Affinity Photo and Designer. Auf dem PC ist Photo/Designer/Publisher nicht brauchbar, sobald ich größere Bilder in hoher Auflösung verwende, friert das Bild ein und ich kann mir einen Kaffee holen. Also musste ich in den sauren Apfel beißen und die Adobe Clound-Anwendungen wieder kaufen.

Also hätte ich gerne etwas von dem Geld zurück, das ich für die Programme auf dem PC bezahlt habe. Sind nur eingeschränkt nutzbar. Bitte lassen Sie es mich wissen.

Alles Gute

 

[Tormy]

On 11/18/2021 at 3:10 AM, Rafael Rivera said:

Had to disable OpenCL acceleration to get Affinity Photo to stop crashing. RTX 3090. Just throwing this out there, just in case your software-only logic is missing a GPU model/sku.

Already did times earlier. Nothing. Still have the issue. Hence my interventions here in this thread.

[ziplock9000]

On 11/8/2021 at 1:50 PM, Komatös said:

If there was a solution, it would have been communicated in the initial posting.
 

No it wouldn't. If you look at this thread, any updates from staff are additional later posts not an edit to the original.

[Komatös]

1 hour ago, ziplock9000 said:

No it wouldn't. If you look at this thread, any updates from staff are additional later posts not an edit to the original.

Then there is no solution!  And the support staff hasn't all information. And some info's are not for the public. 

[ziplock9000]

25 minutes ago, Komatös said:

Then there is no solution!  And the support staff hasn't all information. And some info's are not for the public. 

No solution at the time of posting, but time ticks along. Hence that's why it's worth asking again. Simple.

[Komatös]

The problem child is AMD, the OpenCL drivers react slower with RX5000s/6000s GPUs than with GPUs of previous model series; and AMD prefers to optimise their drivers for games.

Unfortunately, the workstation drivers for AMD's workstation graphics cards do not work with the gaming graphics cards.

Hopefully the upcoming Intel dGPUs working well.

[ziplock9000]

Just now, Komatös said:

The problem child is AMD, the OpenCL drivers react slower with RX5000s/6000s GPUs than with GPUs of previous model series; and AMD prefers to optimise their drivers for games.

Unfortunately, the workstation drivers for AMD's workstation graphics cards do not work with the gaming graphics cards.

Hopefully the upcoming Intel dGPUs working well.

Why are you resorting to personal insults now calling me a 'child' ?

Yes the pertinent parts of those details were already made available on this thread.

[Komatös]

1 minute ago, ziplock9000 said:

Why are you resorting to personal insults now calling me a 'child' ?

Yes the pertinent parts of those details were already made available on this thread.

I didn't mean you by problem child, but AMD

In German, Problemkind (Problem Child) means a person, object or circumstance that causes problems.

It was never my intention to insult anyone here.

[Old Bruce]

For what it is worth, I as a lifelong unilingual Anglophone read "The problem child is AMD, the OpenCL ...." as referring to AMD as the Problem child.

[PSDfield]

I reported this issue as a Bug via the Radeon Software - maybe more Affnity user and other creators should do this and go to the AMD Forums because this is not acceptable.

[PSDfield]

If people here understand what this means, does it mean there is progress?

https://community.amd.com/t5/opencl/whitelist-request-and-a-potential-opencl-driver-problem-with-amd/m-p/494244/highlight/true#M40111

[slizgi]

From the first hand from AMD I know they know about this, and working on it but no ETA yet.