Hi Mike, everybody…

 

A couple of observations re “on the fly” derivatives from a techie perspective:

1) I would expect JPEG derivatives, particular if at substantially lower resolution, to be very much smaller than the master TIF, even with TIF compression. Makes me wonder about the exact nature of the storage space limitations you mention.

2) Generating and a derivative on-the-fly implies loading and processing the (very) bulky original file.

My instinct is that the I/O and processing burden of doing this is a high price to pay for the small proportion of storage space likely to be saved.

 

Interesting idea tho …maybe a compromise could work well. Have a few strategically sized derivatives ready made for 90% of anticipated needs, and have an on-the-fly facility to generate more specialised versions, avoiding the need to store a derivative for every conceivable purpose.

 

I suspect that’s the line you’re already thinking along.

 

David Marsh

 

          

-----Original Message-----
From: Mike Rippy [mailto:mri...@ima-art.org]
Sent:
Friday, January 06, 2006 6:25 AM
To: mcn-l@mcn.edu
Subject: Re: MCN-L Digitization procedures

 

Oh, by the way.  Our plan here for our collection photography is to store the raw file, create a master tif file (that has been corrected for dust, color, etc.) and from that make various jpg derivitives (as needed).  However, do to storage space limitations, we are considering using a new system that uses an application to generate derivatives on "the fly" to be delivered to our users.  Saving the cost of storing each derivative file

 

===========================================
David Marsh
System Administrator
H.R. MacMillan Space Centre
1100 Chestnut Street, Vancouver, BC V6J 3J9
E dma...@hrmacmillanspacecentre.com
T (604) 738 7827 ext. 255
C (604) 813 9667
===========================================  

---
You are currently subscribed to mcn_mcn-l as: rlancefi...@mail.wesleyan.edu
To unsubscribe send a blank email to leave-mcn_mcn-l-12800...@listserver.americaneagle.com

Reply via email to