Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: 1400

2008-05-22 by pr_roark

Andre wrote:

> --- In DigitalBlackandWhiteThePrint@yahoogroups.com, "pr_roark"
> <pr_roark@> wrote:
>  
> > The only place I have a problem is within one inch of the top and 
> > bottom edges of the paper.  So, I usually print with wide margins.
> > 
> 


> I have an Epson 1400 on order and just read this message.
> 
> If I understand correctly, the maximum image size that 
> can be printed without banding with an Epson 1400 using 
> 13"x19" paper is 17" on the long side. 

I'm only talking about the B&W inksets I make/use.  I'm not sure 
about OEM color.  I'm also not sure about all papers, etc.  However, 
I've noticed a pattern that if margins on 1.5 pl printers at top and 
bottom are less than about 1", the probability of microbanding at 
these top and bottom edges is rather high.  It does not affect the 
sides of the print.  It's almost certainly a paper transport issue of 
some type.  The thickness of paper may also be a factor.

By the way, the URL below is to a graph showing the Lab A & B tones 
for the "Matte-Neutral-1" curve used with H. Photo Rag and the 1400 
with the UT-14a beta inkset. 

http://www.paulroark.com/BW-Info/UT-14a-PhotoRag-Tones.jpg 

A similar straight-line tone curve between paper white and deep 
shadows appears to result when this curve is used to print many matte 
papers.  As such, I'm hopeful that one curve will be enough -- 
particularly when used with Create ICC-RGB -- for many papers.  I'll 
make similar curves for other tones.  Glossy prints of various tones 
as well as 100% carbon matte and glossy (neutral 100% carbon glossy 
prints must be sprayed with Print Shield) are within the UT14a's 
reach without changing inks.  

But, this is still beta and not available from MIS yet.

Paul   
www.PaulRoark.com

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.