ripping issues

  • Thread starter Thread starter eager
  • Start date Start date
E

eager

i had a customer telling me that because the printer driver is installed on
the server it takes twice longer for the job to be printed because it's
being ripped twice, once on the server and once on the fiery ....

any comments?

thanks!
 
eager said:
i had a customer telling me that because the printer driver is installed on
the server
Click to expand...

What server? Print server, file server, web server?
it takes twice longer for the job to be printed because it's
being ripped twice, once on the server and once on the fiery ....
Click to expand...

"Fiery" presumably being a RIP for one of the Canon departmental
printers...

Was the customer telling about something they observed, or asking about
what would happen if they bought one?

Not enough details, but either way it sounds incorrect. A RIP converts
a PDL to a raster. Once you've done that, there's no reason to do it
again.

(Well, unless the raster is expressed for one native PDL and you have to
convert it to another.)

(Also possible is that one RIP converts to large bitmap data that takes
longer to send than a small PDL file.)
 
i had a customer telling me that because the printer driver is installed on
the server it takes twice longer for the job to be printed because it's
being ripped twice, once on the server and once on the fiery ....
Click to expand...

dont think this can be said so general.
for example if you sent someting simply to the defoult printer of the
server, you do not use any conversion of the data local (you will
probably not need any driver or similar at all)
 
"eager" <[email protected]> said:
i had a customer telling me that because the printer driver is installed on
the server it takes twice longer for the job to be printed because it's
being ripped twice, once on the server and once on the fiery ....

any comments?
Click to expand...

This needs much clarification before anyone can comment.

The print driver being on the server has nothing to do with RIPing the
file. The print driver generates Postscript and sends it down to the
Fiery, which then RIPs the job.

??????
 
Elmo P. Shagnasty said:
This needs much clarification before anyone can comment.
Click to expand...

it's a very classical setup:

The fiery, which is attached to the printer, is connected to the LAN.
The print drivers are installed on the LAN server ( whatever services are
running there, who cares) and the net admin installs the network printer on
each workstation ...

The print driver being on the server has nothing to do with RIPing the
file. The print driver generates Postscript and sends it down to the
Fiery, which then RIPs the job.

??????
Click to expand...

correct. that was my answer as well. I just needed to confirm.

thanks!
 
Back
Top