Yahoo Groups archive

Digital BW, The Print

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

Message

Re: Inks, Epson vs. Cone ( moire pattern)

2001-12-16 by ruhrfoto

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



--- In DigitalBlackandWhiteThePrint@y..., Todd Flashner 
<tflash@e...> wrote:
> > Todd., this is a phaenomenem which has nothing to do with 
the drivers. I
> > should have mentioned this in my data sheet. It has 
something to do with the
> > grade of magnification of the image in PS. It seems to be a 
form of
> > interference of fine structures (lines) during the 
sampling/resampling process
> > in PS  which appears while creating larer or smaller images. 
The raw-files of
> > the images are the same. The interferrence came up by 
downscaling the large
> > image. If I upscale it again, it disappears. You can reproduce 
the same
> > phaenomenem with the piezo test file (lines pattern) which 
comes with the
> > piezo software, it is visible on the monitor by stepwise 
magnification. Best
> > regards Bernd
> 
> 
> Bernd 
> 
> I'm familiar with the type of aliasing you are talking about in PS 
- at
> least I think I am - let's see.... And I *think* it's called aliasing, 
but
> I'm not sure of that either.
> 
>  What I experience is not related to file size so much as image
> magnification. The image has poorer representation on screen 
at odd
> magnifications than even. Thus 33.3% magnification is more 
aliased than at
> 50%, and 66.7% is worse than 75%. (This is one reason to 
never check your
> sharpening, or other filters, at those odd magnifications. 100% 
is the only
> "true" test, though 50% and 25% can be useful, but never 
33.3% or 66.7%,
> etc.)
> 
> However this aliasing of which I speak is never present in print. 
It's
> purely a screen representation. I personally have never 
experienced what I
> see in your print from up or down sizing in PS, but then I'm no 
expert. All
> I know is I always use bicubic interpolation for photos, and so 
far I've
> been lucky as such.
> 
> But the true test to me would be if an Epson driver print of that 
same file
> (that produced the moiré in the Piezo driver) also produces the 
moiré. Have
> you tried that? 
> 
> Thanks,
> Todd
> 
> 
> >> While we are on the subject of Bernds driver comparison, I 
saw something in
> >> there that I had never seen before. Look at the two smaller 
prints that were
> >> both printed with the Piezo driver. The large smoke stack on 
the left has a
> >> moiré  pattern in it's lower third. It's not there in the Epson 
driver print,
> >> but that is a larger print, so I wouldn't expect them to be the 
same. But
> >> what could be the cause of that moiré ?
> >> 
> >> Todd
> >>

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.