Yahoo Groups archive

Digital BW, The Print

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

Message

Re: [Digital BW] Protection of Prints

2006-03-20 by Carl Schofield

I'm also embarking on a non-traditional exhibit to shake up the  
conservatives in my community and conduct an experiment at the same  
time.  I'm hanging an exhibit next month of 17x22 inch B&W and false  
color infrared prints made on both Hahnemuhle Photo Rag Satin and BC  
Chromata Canvas.  The prints will be bare naked in Danish  
posterhanger "frames".  The prints will be up for 2 months (if they  
survive that long) in a local cafe venue for artists.  The prints  
will not be offered for sale because they were made using Nanochrome  
inks, but they are beautiful when displayed in this manner without  
glazing, even if they do not last.  Temporal art - sort of like sand  
castles on the beach.

Carl

On Mar 19, 2006, at 4:12 PM, Tina Manley wrote:

> Digital B&W -
>
> I'm participating in a show that has the potential to be
> controversial.  The museum is concerned about protecting the prints
> and is proposing that rather than use custom, high quality inkjet
> prints (made with the Epson 4800 on fine art paper) which would cost
> about $75 for each 17x22 print, that we go with Costco prints which
> cost $9.90 for a 17x22 and could be easily replaced if defaced or
> damaged.  There is enough money in the grant to pay for one custom
> inkjet print of each photos but not enough to replace them and
> there's not enough money to pay to have them framed behind glass.  I
> definitely want to go with the inkjet prints to show some of the
> diehard, darkroom-only, fanatics how beautiful inkjet prints can
> be.  I've seen them side by side with the Costco prints and there is
> no comparison.  Can anybody come up with an argument for the museum
> or a cheap solution to the protection problem?
>
> TIA -
>
> Tina
>
> Tina Manley, ASMP
> http://www.tinamanley.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.