no printing of large pages in Publisher 2.2.1 with Epson stylus pro printer

[Frankyboy]

I use: windows 10 , publisher 2.2.1 , epson stylus pro 4880 , epson stylus pro 4900

my pc has: 32 GB ram and have a NVIDIA GeForce GTX 1630 with 4 GB

the problem is: large pages (more dan 1000 mm in length to build a leperello) will not print. In the print screen I can fill in the size etc, after clicking print there should show up an preview of the print, but there is nothing to see.

smaller pages (less then 800 mm) will show the preview, but on strange positions.

i had these problems not in V1.

it looks like a missing , inproper contact between Publisher and the printer protocols.

my tempory solution is to export as a PDF and print the pdf, without any problem.

is there a solution or is this a bug?

please help we.

Walter

 

 

[MickRose]

If I was using a large format printer I would always make a PDF first and then print from Acrobat or InDesign. I would do that with any software. You don't want to be printing for several minutes and then have something go wrong. Just my opinion.

[Dan C]

Hi @Frankyboy,

Can you please confirm for me, what are the exact dimensions and DPI for your document within Affinity?

[Frankyboy]

the critical dimension of the documents is larger than width 1000 mm and 432 mm height.

the rasterization is 300 dpi.

larger then these will lead to a preview with no data shown. Mostly on the pages are pictures in either black-and-white  or color.

smaller ( A4 and A3) pages will be printed properly

i hope this will give any explanation.

Walter

[Dan C]

Thanks for confirming that for me - as I understand it, PDFs (and therefore printing using a PostScript driver) has a display file size limit of 200" x 200", so anything larger than this will not be displayed. This is a limitation of the PDF format and not the Affinity apps directly.

33 minutes ago, Frankyboy said:

larger then these will lead to a preview with no data shown. Mostly on the pages are pictures in either black-and-white  or color.

I can see in your Affinity print dialog screenshot above that the preview contains these images, and is currently set to 4640mm x 432mm - so I'm not certain what you mean by this. Are you referring to a preview dialog that is not part of the Affinity app?

You mention that these issues did not occur within V1, can you please confirm if you've tested with documents of the same size in both versions? I ask as thus far in my testing, I have found similar limitations between V1 & V2 so I'm not certain how this has worked for you previously at this time.

I have therefore escalated this internally to request further information from our team. If you can provide as much information as possible here, I'll be sure to reply ASAP with any suggestions I am given.

Many thanks in advance!

[Frankyboy]

Dan,

answer on item 1 : you see two screenshots, one taken from AP-V2 print-menu and one from the transfer from AP-V2 to the Epson driver. This last one should be the same as the one seen inAP-V2. My conclusion is that AP-V2 is not communicating with the driver of the Epson printer. This communication between AP-V1 and the Epson driver was correct. I had no reason not to print from AP-V1. You can see in the heading of screenshot 2 that this is from the Epson driver (EPSON afdrukvoorbeeld).

answer to item 2 : I have printed files via AP-V1 up to 8000 mm, no problem there. The screenshots from AP en from EPSON diver where correct as they should be. I never had used the bypass through PDF-files. by the away i was not awere of the 200 by 200 limit of the PDF files. Due to the change of version 1 to version 2 I can not repeat this (this change is some what confusing in relation how to maintain the old format).

answer to item 3 : if it is helpfull to supply you with some *afpub files, I can do that. I have added some screenshots of the process with a simple file that worked fine.

thanks for the effords you are puting in to this problem.

 

best regards, Walter

[Dan C]

Thanks for your patience here @Frankyboy!

I can confirm that a colleague of mine has been able to test this issue on an Epson Stylus Pro 4800 - where we've been able to replicate this bug.

Therefore I have logged this with our development team, providing all the information you've provided here to help our team resolve this in a future update.

I hope this helps