Jump to content
You must now use your email address to sign in [click for more info] ×

Graphic Re-Draw Issue is Back


Recommended Posts

With Open CL active....

First while in Develop Persona, the sluggishness when zooming in/out is present, along with the blocky redrawing of the screen. I thought it was going to crash but didn't.

After processing my CR2 RAW file, the first thing I noticed was the blocks in the image, see screenshot.

This was not present with Open CL unchecked/not active.

Beta-1.9.0.820

beta-190820_BlockyRawDev.jpg

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

4 hours ago, Chris B said:

Thanks Ron P.,

I've seen the occasional blemish with OpenCL on but it isn't consistent.

Can you reproduce it with that same image over and over?

Yes I can.

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

Here you go @Chris B,

I zipped together a copy of the original RAW file and a developed jpg showing the blocky artifact.

blocky-beta.zip

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

Hello Ron,
I downloaded your zip file.
The JPG file has the blocks described above, very strange.
I can develop or edit the CR2 RAW file without abnormalities.
I am curious how Serif assesses this problem.
 
Cheers
 

Affinity Photo 2.4:         Affinity Photo 1.10.6: 

Affinity Designer 2.4:    Affinity Designer 1.10.6:

Affinity Publisher 2.4:   Affinity Publisher 1.10.6:    

Windows 11 Pro  (Version 23H2 Build (22631.3296)

 

Link to comment
Share on other sites

2 hours ago, Gnobelix said:
Hello Ron,
I downloaded your zip file.
The JPG file has the blocks described above, very strange.
I can develop or edit the CR2 RAW file without abnormalities.
I am curious how Serif assesses this problem.
 
Cheers
 

The blockiness occurs when zoomin in/out. It seems to be a problem with the screen redrawing, after processing the image. In my example I done the following in this order:

  1. Exposure adjustment
  2. Black Point
  3. Brightness
  4. Shadow/Highlights
  5. Clarity
  6. Details-Detail Refinement. Here is where I zoom in to around 100% to monitor the sharpness. Generally my settings used were 39% Radius, and 70-79% amount.

The blockiness occurs during this, and if I let the image sit for around 30 secs then it clears up. If I press develop before it clears, it is burned into the image passed into the Photo Persona.

Affinity Photo 2.4..; Affinity Designer 2.4..; Affinity Publisher 2.4..; Affinity2 Beta versions. Affinity Photo,Designer 1.10.6.1605 Win10 Home Version:21H2, Build: 19044.1766: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz, 3301 Mhz, 6 Core(s), 12 Logical Processor(s);32GB Ram, Nvidia GTX 3070, 3-Internal HDD (1 Crucial MX5000 1TB, 1-Crucial MX5000 500GB, 1-WD 1 TB), 4 External HDD

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.