Yahoo Groups archive

Digital BW, The Print

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

Message

RE: [Digital BW] EAM turns yellow!

2003-08-31 by Martin Wesley

> -----Original Message-----
> From: Mark Hahn [mailto:markhahn2000@yahoo.com] 
> Sent: Saturday, August 30, 2003 11:56 AM
> To: DigitalBlackandWhiteThePrint@yahoogroups.com
> Subject: [Digital BW] EAM turns yellow!
> 
> 
> was headed out the door with a portfolio of quadtone prints (all in 
> plastic sleaves).  then I noticed that the edge at the open end of 
> the sleave on all the prints had turned yellow!  also, a number of 
> prints that had been stacked up for a few weeks all had gone yellow!  
> This crap is certainly not archival.  What is the next step for 
> archival quality and the same printing results?  I am getting worried 
> about the prints that I have already sold (with my claims of archival 
> quality etc.).
> 
Mark,

Sorry to hear about your problem. That is a really terrible thing to have
happen to you.

What kind of sleeves were the prints in? Type of plastic that is. Awhile
back there was an issue with the reaction of Somerset Velvet and the release
agents used in some plastic sleeves.

While the optical brighteners will fade an slightly yellow with time it
should take a long exposure to UV light. Had prints been stored with the
open end of the sleeves toward a strong light source?

I am curious as to why this happened to you. I don't use EAM or EEM for
finished prints preferring Photo Rag and German Etching but I do use a lot
of it for proofing and work prints. After 2.5 years I have not experienced
anything like you describe. I wonder if it a paper batch related problem or
something in your particular environment. In any case a change in paper
would seem to be in order.

Martin Wesley
http://www.carolyn.cc/Guests/MartinWesley/pages/MW_01.html
http://www.borderless-photos.de/guests.html

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.