Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Re: Inks, Epson vs. Cone ( moire pattern)

2001-12-16 by Todd Flashner

Thank you Bernd.

I don't understand it either, but at least we know it's outside the driver.
I guess certain patterns have resonance at certain magnifications, and it
doesn't matter if that frequency is viewed on screen or in print.  (Forgive
what I'm sure is improperly used terminology.)

Todd

> Todd,
> you are right in respect of the monitor aliasing.
> At 33 and 66 (or at 500)% the aliasing is extrem, while on 100 %
> is it completely gone.
> 
> The moire pattern in my image may not be the same thing, but
> maybe of the same origin.
> 
> Actually the moire pattern is printed with the Epson driver not only
> if I print the file on my 1160 with MIS FS inks  - but also on my
> 1290 with MIS VM inks.
> I suppose this "aliasing" has to do with something I would
> discribe as "interference" between the resolution (actually the
> distance) of the bricks on my negative (wich is 8x10) - the
> scanning resolution - and the amount of magnification in
> photoshop (which actually is no "magnification" in the case of the
> smaller prints, but a "minorisation").
> 
> Neither am I a mathematic nor a technican - nor do I really
> understand anything about  the inner workflow of a scanner ...
> So these are just thoughts.
> 
> The essence is, the moire pattern is independent of the driver,
> so you should ignore it in the driver-discussion.
> 
> BTW, I´m sorry that I hadn´t already got the MIS FS inks at the
> time I printed my exchange images, I would have added a  MIS
> VM print from my 1290. At 2880 it prints virtually as dotless as the
> piezo driver does, but is much slower.
> 
> Bernd
> If anybody seriously wants to have a 1290/MIS VM hex print from
> the same file, mail me offline - Paul yours is on its way at last.
> Bernd

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.