Yahoo Groups archive

Datacolor User to User Support Group.

Index last updated: 2026-04-28 23:18 UTC

Message

Re: 1A higher L* than 1B, what to do..?

2007-12-23 by John Vitollo

--- In colorvision_group@yahoogroups.com, "John Vitollo" <jvlist@...> wrote:
>
> --- In colorvision_group@yahoogroups.com, "oisteinthomassen" <oisteinthomassen@> 
> wrote:
> >
> > Silk (baryta) and Innova Fiba Gloss, the 1A patch comes out brighter 
> > (L=6,9) than the 1B patch (L=5,8). 
> 
> That's a very common symptom when there is too much ink being laid down on the 
paper. 
> What media setting are you using?  Have you used the "Print Quality Check" with 
different 
> media type to determine the best media type? This should be your first step.

Also...

Here's a test a did a while ago to find the best media setting:

Try exploring media settings to open shadows...

I recently tested to find the "best" media setting for William Turner paper on my Epson 
4800.

Epson's black usually comes in hard and fast, less so with the newest printers, and I 
wanted to find the media setting that has smoothest black ramp from 100% to 90%.

I printed a ten patch gray ramp from 100% to 90% with five media settings.

My Excel results are below for William Turner on the Epson 4800:

http://homepage.mac.com/johnvito/WilliamTurnerMediaSettings.png

From 100% to 90% only two media settings show fairly smooth linear density loss albeit 
stepped at times. While the other three actually have spiked increases in density - called 
reversals - on some patches. For example Epson's Enhanced media setting has the same 
density at the following patches: 100%, 99% and 97%. The 98% patch has a lower density 
than 97% patch and another reversal at 94%.

My media setting choice for William Turner was UltraSmooth as it has the most smoothest 
linear path. The custom paper profile will have less heavy lifting to do once the "best 
media type" is found.

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.