Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
- Subject: Re: Re. inkjets: An open letter to Tom Lianza and Lars Borg
- From: "edmund ronald" <email@hidden>
- Date: Mon, 19 May 2008 23:33:00 +0200
Dear Lars,
I am thankful that you are taking this issue seriously.
I agree with your comments 100%. Certification is not what we require
for Joe User.
I propose the opposite of certification, namely error alerts and then
interactive diagnostics. Let's define a process that will allow us to
easily spot and diagnose known categories of errors.
Concretely I propose the following diagnostics:
1. Profile and media settings can be checksummed into a few digits
that can be *printed on the profile target,* printed later discreetly
on the edge of the print if requested , and maybe even act as a menu
key to restore all the print settings -both in PS and in the driver-
cleanly without interminable menu choices.
2. System printing bugs can be spotted either by checksumming the
dither pattern and storing this in a file (proposed by Gutenprint
author Robert Krawitz) . Or in last resort they can be spotted by a
spectro reading.
3. Hardware faults can be spotted by visual comparison to a known good
print -the one which made the profile- or again by spectro readings.
Profiling targets are not made for visual comparison, but the eye can
judge a select few *large* patches quite well if they can be overlaid.
Appendix:
----------------
(A) Here are some known *user* errors in inkjet photo printing with a
profiled workflow from the industry standard photo editing
application:
1. Wrong PS print settings leading to no profile or double profile application
2. Wrong profile selected (does not correspond to the media)
3. Media settings that do not correspond to profile.
(B) Now here are some typical *system-level* bugs
4 Double profile application because of driver bug.
5 Printer driver drift because of driver update
6 Corrupted driver settings eg. by applying settings for one printer to another
7 General corruption because of bit-rot.
(C) And then there are of course the inevitable hardware issues
8. Printer failure eg. Blocked nozzles
9. Severe Ink variation.
On Mon, May 19, 2008 at 9:38 PM, Lars Borg <email@hidden> wrote:
>
> Let's uplevel. You're assuming a certification process would solve the
> problem in the field. Would it? I don't think so.
> A certification process would only tell us it is possible to get correct
> output, not that we're getting correct output right now.
> A certification process doesn't verify that Joe's system is correct right
> now. Maybe his paper is too moist, or an ink nozzle is performing below par.
>
> It seems the user needs something that can verify the system live, including
> hardware deviations.
> As far as I understand, this is one of the major problems.
>
> Lars
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Colorsync-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden