On Jan 7, 2009, at 4:00 PM, aussieshepsrock wrote:
> Original Poster here.. > > This jpeg vs tiff question is pretty important to me. My personal > experience with jpegs is that the inherent nature of how the > compression it uses works, very little quantities of data loss equate > with the Functional Loss of the image. My limited knowledge of the > 'nature' of TIFF is that (to some extent) it is more resistant to > losing the entire image if data describing specific pixels is lost or > compromised. Does anyone know if this is correct? It depends, greatly. if you lose data out of the files, both are foo. Data integrity is crucial. If the tiff utilizes internal compression, your data is foo. If it does not, you can reconstruct some of the image. When we speak of jpegs as 'lossy' and tiffs as 'lossless' we mean that the process of creating the file from the original image data does or does not throw away data, but this is during the creation of the file. Loss of data AFTER the file is created is always bad. This is why we're advocating multiple copies of the files on different media as a storage strategy. You (or rather someone with the requisite skills and tools) CAN take two messed-up copies of the same file and often make one good one out of the two... -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed Low End Mac's G3-5 List, a group for those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs. The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to g3-5-list@googlegroups.com To unsubscribe from this group, send email to g3-5-list-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/g3-5-list?hl=en Low End Mac RSS feed at feed://lowendmac.com/feed.xml -~----------~----~----~----~------~----~------~--~---
