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

Crash on Batch Job


Recommended Posts

I created a custom macro for removing black background on a batch of images. When I try to run a batch job, the complete Affinity Photo program seems to crash and disappears.

The Macro:

https://www.vanoostenbrugge.com/temp/Remove-Black-Background.afmacro

It seems to be something with the macro; other macros are working well with the same settings. I recorded the macro again but with the same result.

Example image file:

Big-Ben-brown.png

 

Affinity Photo version: 1.8.3.641

System information:

OS Name    Microsoft Windows 10 Pro
Version    10.0.18363 Build 18363
Other OS Description     Not Available
OS Manufacturer    Microsoft Corporation
System Name    DESKTOP-QEUBCL0
System Manufacturer    Dell Inc.
System Model    OptiPlex 790
System Type    x64-based PC
System SKU    
Processor    Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz, 3101 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date    Dell Inc. A11, 30/12/2011
SMBIOS Version    2.6
Embedded Controller Version    255.255
BIOS Mode    Legacy
BaseBoard Manufacturer    Dell Inc.
BaseBoard Product    0D28YY
BaseBoard Version    A01
Platform Role    Desktop
Secure Boot State    Unsupported
PCR7 Configuration    Binding Not Possible
Windows Directory    C:\Windows
System Directory    C:\Windows\system32
Boot Device    \Device\HarddiskVolume1
Locale    United Kingdom
Hardware Abstraction Layer    Version = "10.0.18362.752"
Username    DESKTOP-QEUBCL0\Roeland
Time Zone    W. Europe Summer Time
Installed Physical Memory (RAM)    16,0 GB
Total Physical Memory    15,9 GB
Available Physical Memory    8,96 GB
Total Virtual Memory    18,3 GB
Available Virtual Memory    9,01 GB
Page File Space    2,38 GB
Page File    C:\pagefile.sys
Kernel DMA Protection    Off
Virtualisation-based security    Not enabled
Device Encryption Support    Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not Modern Standby, Un-allowed DMA-capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions    Yes
Hyper-V - Second Level Address Translation Extensions    Yes
Hyper-V - Virtualisation Enabled in Firmware    Yes
Hyper-V - Data Execution Protection    Yes
 

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...
×
×
  • 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.