>... Hahnemuehle Photo Rag 308. >QTR ink separation page printed at 100%. >Eye One spectro. >100% densities read: >Eboni 1.71 >FSN-C 1.24 Lab a=-0.5 b=-0.2 >FSN-M .53 Lab a=0.3 b=-6.7 >FSN-Y .36 Lab a=0.2 b=-4.4 >FS-C 1.31 >FS-M .49 >FS-Y .36 >I've used FSN and FS on this machine before with no >problem. What seems wrong is: >The FSN-M and Y seem too blue (note high negative b >numbers) while the FSN-C is close to neutral. >The dark grays for both FSN and FS should be darker >(density around 1.5?). Also for both FSN and FS it >seems there should be more of a density difference >between the light grays and middle grays (M and Y). The blueness is probably the same issue that is plaguing the 3D inkset. I just received a new beta batch today for testing. The main problem I found is that the LK from the supplier is too light. MIS has been relying on the supplier for a standard LK. The light inks are the most affected because they use only the LK as the carbon input. The C and M are affected to a lesser extent because they also use PK. To get the too-light LK up to snuff, PK has to be added to it. Needless to say, doing this for every batch is time consuming. I don't know how far back the problem goes. It's possible I'll be able to come up with a correction procedure for existing inks, but no guarantees there. I'm not sure they have the information to know how far off the various back batches were. The closeness of the M and Y harks back to the Piezo days. All inksets I've been involved with since the UT2 have corrected this. If the FS-C has too low a Lab A for you, use the R2-N C or M (the same ink). That is what I now use in my 7500 instead of the FSN-C. MIS is in the middle on this one. The too-light LK is from the supplier. MIS is now going to have to QC every input and take corrective steps. I'm not sure how they can to that and not raise prices, but they say they will try. Paul www.PaulRoark.com
Message
RE: [Digital BW] Magenta cast on UTFSN prints...
2006-08-30 by Paul Roark
Attachments
- No local attachments were found for this message.