Yahoo Groups archive

Digital BW, The Print

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

Message

Re: OPM - 2200 - black only tests - initial report

2003-04-04 by grdglass@aol.com

Antonis,

Thanks for the black-only profile, the 26-patch, and the methodology.

I just finished my tests and my observations are somewhat different, but 
before I get into that, I want you to know that I emailed a scan of my OPM 
problems to Charles at BowHaus.  He sees what I am encountering and they are 
going to try to reproduce the problems.  Hopefully they will solve it.

OK, now to my tests using your methods.  

1.  Using the OPM black-only profile, I still get banding in the 100% patch.  
My thinking is that if it's ink starvation, a faulty black cartridge, or a 
bad black head, I would be seeing banding throughout your 26-step patch.  Do 
you agree?

2.  Using black-only with the Epson driver, no banding.

My visual observations are somewhat different than yours:

1.  You see a herringbone pattern in the Epson driver; I do not.

2.  My Epson driver has a nice long tonal scale, unlike yours which dips into 
dark from 50-100.  Like yours, the dots are most apparent in the midtones.

3.  The OPM driver is more compressed.  From 0 to 44, I see white striations 
in the top part of the scale.  I see these with my eye but cannot see them 
under a loupe.  Patches 68-84 seem to be the same tone.  OPM's midtone dots 
are less apparent than Epson's.

I will put everything under a densitometer later today or tomorrow and let 
you know.

Helene

> Given reports that some here have seen banding in the black when printing 
> with OPM but not when printing with the Epson driver, I did a test using 
> the 
> files I uploaded earlier: The black-only profile and the 26-patch test 
> scale.
> 
> 
> 
> 
> Here is the methodology, so that others may do the same and we can then 
> compare notes:



[Non-text portions of this message have been removed]

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.