Melissa M
-
Posts
4 -
Joined
-
Last visited
Posts posted by Melissa M
-
-
2 hours ago, RichardMH said:
If it is turned on ,try with OpenCl acceleration turned off. (Edit-Preferences->Performance). I was getting something similar exporting jpegs and tiffs.
Thanks! I just checked and it was turned on. I'll try printing with it unchecked and see if that solves it.
-
Hi, Sorry for the delay in responding.
It just happened a third time, with a completely new file. I've attached it for you. Another white block appeared on the top of the right-most print. Here's a picture so you can see what it looks like.
I'm running Windows 10.
I can print the same file twice and sometimes it happens and sometimes it doesn't. I'll try exporting to a PDF like you explained and see if it happens then.
Thank you!
-
Hello,
This is the second time this has happened to me when printing from Affinity Photo desktop. I go to print and a blank white box or white line show up on the image. I only have the image layer and several adjustment layers on top, no blank white boxes. I have printed the same images from Affinity Photo without this error. It seems as if something is getting lost in communication between Affinity and my printer and it is "forgetting" to print parts of the image. I use a Canon Pixma-Pro 10. I've attached a few images to show what it looks like. The first one is more obvious, the one on the red print is just a small line about one pixel tall. (The white dots are part of the illustration.)
Has anyone else encountered this issue? Is there a fix? It's a little frustrating to have to throw away expensive photo paper. (I use Moab.) :(
I've printed from other photo editing programs with this printer many times and haven't had this issue before, so I'm suspecting it's something on Affinity's end.
Thank you!

Printing error: White boxes appear on print
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
I just wanted to come back after printing for while with no issue to say that turning off OpenCL acceleration fixed the issue--thank you so much!