Yahoo Groups archive

Digital BW, The Print

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

Message

[Digital BW] Re: Advanced dye for B&W - WorkForce 30

2011-02-08 by Unny

Hi Paul,
I have set up a Workforce 30 for Eboni MK (three dilutions and the K ink in the two black positions) and use it with PhotoGP (a freeware Gutenprint plug-in for Photoshop CS4). I linearize the curves by modifying the XML curve files associated with the C,M,Y positions. On the other hand I notice that there is an abnormal reduction in some of the ink levels, especially in the Cyan position (I use 2% dilution with the generic solvent according to your formulation - thanks!). I wonder if the ink is leaking out when not in use. Now that you mention the dye inks leaking, I should pay more attention to this!
Unny 

--- In DigitalBlackandWhiteThePrint@...m, "Paul" <roark.paul@...> wrote:
>
> The WorkForce 30 appears to be an inappropriate platform for the Noritsu-Epson dye ink approach.
> 
> In a several month, low usage setting the WorkForce 30 with the dye inks in it may have had the ink simply run through it. 
> 
> The dye inks are made for the 1.5 pl printers, and I have not seen any evidence of ink loss on the 1400.  Also, the R220 appeared to have none.  The R220 may have a smaller drop size than the Wf 30.  
> 
> If the picoliter drop size is a significant variable, there is a WF 40 model that may have a smaller drop size  -- the WF40.
> 
> The WorkForce printers I've used -- WF 30 and WF 1100 -- so far appear to be good "EZ" types of printers for matte printing with pigment ink.    
> See http://www.paulroark.com/BW-Info/C88-C13-5.pdf for a similar setup for the C88.  It may be that a standardized LK density for the midtone ink both works better and brings the "EZ" approach within a large, competitive market for LK density inks.
> 
> So, the WF 30 gets a Eboni/Carbon-6 18% (M & LK density) setup next.
> 
> Paul
> www.PaulRoark.com
>

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.