AnsweredAssumed Answered

Double sided jobs are being sent as discrete pages

Question asked by Tim Strackbein on Apr 21, 2017
Latest reply on Apr 27, 2017 by John Siegel

We're running into a bit of a weird error here.  When someone submits a job as double sided (which is our default submission type), pharos is parsing the job into discrete pages.  So if it's a 10 page job, when I look at it in the queue, I see something like "1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Duplex", 1 page of "612x792,Letter,Blank,Duplex", 1 page of "612x792,Letter,Mono,Simplex" " under the job attributes.

 

The problem with this is then the printer at the other end is parsing each page individually, which is significantly impacting the overall speed output of the device.

 

If we switch the job to simplex, then it shows "10 pages of "612x792,Letter,Mono,Simplex"", which is going to print MUCH faster.

 

Anyone run into this issue and found a fix?

Outcomes