Jump to content

Failures on batch processing

Brad Brighton
 Share

Recommended Posts

  • Moderators
Justin

Justin

Posted
  • Moderators
Posted

Thanks for trying that Brad. I think this suggests the data has already been corrupted by the time it does the noise reduction and corrupted in such a way that the noise reduction code doesn't cope with it, which narrows things down a bit.

Link to comment
Share on other sites
Brad Brighton

Brad Brighton

Posted
  • Author
Posted
48 minutes ago, Justin said:

Thanks for trying that Brad. I think this suggests the data has already been corrupted by the time it does the noise reduction and corrupted in such a way that the noise reduction code doesn't cope with it, which narrows things down a bit.

Glad to help. If you need additional info, just ask.

https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers

Link to comment
Share on other sites
Brad Brighton

Brad Brighton

Posted
  • Author
Posted
17 hours ago, Justin said:

Brad, could you try turning off hardware acceleration in Preferences|Performance please?

Thanks

Justin

Turning off Hardware Acceleration appears to have eliminated the image result corruption in the 1-test-pass-per-version (production and beta) against the same dataset. 

https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers

Link to comment
Share on other sites
Brad Brighton

Brad Brighton

Posted
  • Author
Posted
52 minutes ago, Justin said:

Hi Brad

We've fixed a bug that was probably causing your issue so you might want to try it again when the next beta is released, which shouldn't be too long.

Cheers

Justin 

I'll keep an eye out, thanks!

https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers

Link to comment
Share on other sites
  • 2 weeks later...
Brad Brighton

Brad Brighton

Posted
  • Author
Posted

@Justin @Chris B @MEB

Recreating the test with Beta 1.8.4.186, Metal accelerator on:

Crash: NO

Corruption: NO (at least none seen through my 2x QuickLook scan of the 487 images, the same visual scan that easily found errant images in the past)

Looks good.

https://bmb.photos | Focus: The unexpected, the abstract, the extreme on screen, paper, & other physical output. Tools: macOS (Primary: Ventura, MBP2018), Canon (Primary: 5D3), iPhone (Primary: 14PM), Nikon Film Scanners, Epson Printers

Link to comment
Share on other sites
  • 1 year later...
titan3025

titan3025

Posted
Posted

Hi all,

 

I am seeing these corruptions as well with Affinity 1.10.5.

 

My hardware setup:

AMD 3800X and a nVidia RTX 2060

 

When I try do batch convert a bunch of images I see the same type of corruption in the files if I do parallel porcessing. If I disable parallel processing the corruption artifacts are gone. 

Is this know and is a patch already in the works?

 

Cheers

Link to comment
Share on other sites
walt.farrell

walt.farrell

Posted
Posted
54 minutes ago, titan3025 said:

Hi all,

 

I am seeing these corruptions as well with Affinity 1.10.5.

 

My hardware setup:

AMD 3800X and a nVidia RTX 2060

 

When I try do batch convert a bunch of images I see the same type of corruption in the files if I do parallel porcessing. If I disable parallel processing the corruption artifacts are gone. 

Is this know and is a patch already in the works?

 

Cheers

Welcome to the Serif Affinity forums.

You have replied to an old topic, about a bug that was already fixed, and was occurring on Mac systems.

As that one was fixed, and as you're not on the same OS, it would be better for you to post your own new topic, I think, in Photo Bugs found on Windows and give full details of the problem you're seeing (including your OS, and whether you have Hardware Acceleration enabled in your Photo Preferences).

-- Walt

Desktop:  Windows 11 Home, version 22H2 (22621.1413) 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 
Laptop:  Windows 10 Home, version 21H2 (19044.2728) 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
        Affinity Photo 1.10.6 (.1665) and 2.0.4  and 2.1.0.1732 beta/ Affinity Designer 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1732 beta / Affinity Publisher 1.10.6 (.1665)  and 2.0.4  and 2.1.0.1732 beta
iPad Pro M1, 12.9", iPadOS 16.3.1, Apple Pencil 2, Magic Keyboard
      Affinity Photo 1.10.7 and 2.0.4 and 2.1.0.1732 beta/ Affinity Designer 1.10.7 and 2.0.4 and 2.1.0.1732 beta/ Affinity Publisher 2.0.4 and 2.1.0.1732 beta

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.

  I accept