Jump to content

Recommended Posts

Posted
Affinity Publisher V2
Version: 2.5.7.2948 (Retail)
OS: Windows 10 Home (10.0.19045)

This is relatively straight forward to reproduce.

  1. Open the attached SVG file in Affinity Publisher V2
  2. Open the Preflight window
  3. Edit the Preflight Profile
  4. Under "Colors and Inks" set both "Maximum ink" and "Maximum Rich Black" to "240%" and set the Warning Level to "Error".
    1. In my configuration, at this point the document will be set to Color Format: RGB/8 and Color Profile: sRGB IEC61966-2.1. However, this isn't unique to this color profile. The attached .afpub shows the issue reproduced with CMYK settings.
  5. Set "Check" to "Live" or press the "Check Now" button.

The Preflight window should now look like the attached FilterEffect.JPG image which shows 3 "Filter Effect ink density too high" errors and one "Stroke ink density too high error." The stroke error is legitimate. The attached .afpub has been converted to CMYK and that error has been corrected. However, the other errors appear to be erroneous. As best I've been able to tell, "Filter Effects" refers to "Layer Effects" and double clicking on the errors to select the offending objects and checking that panel shows no effects applied and toggling things doesn't appear to have any effect. Additionally, if you delete the circle all errors will disappear except one (the top one). If you double click on this one and press delete the program will crash with the following .NET Runtime error. (Note: You can also create the crash by simply double clicking the top error and clicking "Delete". Deleting the circle first is not necessary.)

Application: Publisher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at <Module>.Kernel.Countable.Release(Kernel.Countable*)
   at Serif.Interop.Persona.CountedPtr<DocumentInspectorNode>.Reset(DocumentInspectorNode*)
   at Serif.Interop.Persona.CountedPtr<DocumentInspectorNode>.Dispose(Boolean)

This issue has reproduced with all the SVG files I've tested; all created with Inkscape. While it is possible to ignore these errors, the density of them in more complex images makes it difficult to identify the real errors peppered among the erroneous ones and there doesn't appear to be any way to filter them out.

While they are clearly not the same issue, parts of this sound similar to this old issue caused by the Outline filter.

FilterEffect.JPG

Test Circle.svg Test Circle.afpub

Posted

Related:

 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

  • 2 weeks later...
  • Staff
Posted

The issue ""Filter Effect ink density too high" error on SVG import" (REF: AF-5556) has been fixed by the developers in the latest beta build (2.6.0.3058). The fix is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.

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.