LZW is lossless compression for TIFF's that will cut the file size in about half if hard-drive space is an issue. Choose that option when you're saving an image. To reconstitute just open the file and re-save with Compression:None.
You can't get better definition out of an image by scanning at high res than is in the image to begin with. Considering your monitor can probably only see 96 dpi and regular home printers run in the range of 200-300 dpi, 1200 dpi is some other planet. What is band-width nowadays with a free Dropbox account? I don't hesitate for a second sending TIFF's over. The reason to link JPG's to Legacy instead of TIFF's is because Legacy will freeze if you try to do otherwise unless your TIFF's are very small. --- JL Beeken JLog - simple computer technology for genealogists http://www.jgen.ws/jlog/ On 8/23/2012 8:27 PM, Ian GARDENER wrote: > Tiff files were, and to some degree still are, the preferred format four HIGH > QUALITY images, but this is becoming less favoured with each revision of the > jpeg standard. The real problem with tiffs is that they are huge in > comparison to jpeg files and consequently have issues in that: > > *They take up a lot of space& hardware real estate. > > *They have much longer data transfer times. > > *They tie up internet bandwidth unnecessarily. > > *Most home pc's simply cannot process a really large high quality tiff, ie > try loading a 1200dpi tiff file and your computer will freeze. Note 1200dpi > is more for professional work but it demonstrates the point. > > They do still have their place in my opinion but you have to carefully > evaluate what that is. > > For me, I store all my images within legacy (other than pdf's) as jpg files. > However images that I rate as critical and/or irreplaceable, I keep a high > quality tiff image on a backup medium away from my home. An example would be > old family photographs that are only copies. If my house burns down I can > reproduce a true high quality image on photographic paper from the tiff file. > > Mine is but one opinion of many in the image standard debate :) > > > -----Original Message----- > From: Sentz [mailto:ro...@nycap.rr.com] > Sent: Thursday, 23 August 2012 8:52 AM > To: LegacyUserGroup@LegacyUsers.com > Subject: Re[2]: [LegacyUG] Source Writer and Clipboard > > Lots of nuances to the source writer. When I click on the event and then > click on the source citation in the event window, the citation does show up > on the list for alt. death and I did find it in the main citation list for > the record by scrolling down further. The document image was saved on my > computer as a .jpg file. I did as you suggested and saved the picture to the > event. Should we be saving the picture to > the event and the citation? > Geoff mentioned in his last webinar saving some things in a .tif file > as opposed to a .jpg. Does anyone recall the reasoning behind this? > Something about the difference in the documents, ie. Bible records vs. > other types of records. Why would one file type be better than the other? > > > ------ Original Message ------ > From: "Jenny M Benson"<ge...@cedarbank.me.uk> > To: LegacyUserGroup@legacyusers.com > Sent: 8/22/2012 7:26:11 AM > Subject: Re: [LegacyUG] Source Writer and Clipboard >> On 21/08/2012 23:45, Sentz wrote: >> >>> >>> One of the reasons I bought Legacy was because of the sourcewriter and >>> clipboard tools. I have been struggling with these tools for about a >>> year. I have rerun Geoff's start up Ultimate Guide on the topic and >>> watched his various webinars where he uses the source writer and >>> clipboard, including his most recent one, and have also read >>> documentation. I think I have the process down and then something goes > >>> haywire with the sourcewriter or the clipboard. I am not a novice >>> with data entry or relational data bases, so this is getting very >>> frustrating. What I end up doing is not doing anything in the database >>> for a while, take a breather and try again. >>> The latest problem....I was entering an alternate death event for my >>> great grandmother. I clicked on the tirangle and set up the master >>> source which went okay. Then I set up the detail including linking an >>> image of the page from the death index that I had downloaded and >>> cropped from Family Search. Everything looked okay and I clicked save >>> and then clicked the bar on the left on the window for the event >>> detail. Then saved the event. It's my understanding that a plus sign >>> should show on the line following the event. Am I correct? When I >>> check on the documentation link for the record, the death citation >>> information is not showing. Also, in the event window, the data field >>> labels were highlighted. Perhaps is this case it has to do with where >>> I have the document image stored. >>> I keep thinking that there must be some little step that I am not >>> doing correctly. Any advice would be welcome. >>> >> >> >> The + will be there if you have attached a picture to the Event, not if >> you have attached it to the Source. >> >> -- >> Jenny M Benson >> >> >> >> Legacy User Group guidelines: >> http://www.LegacyFamilyTree.com/Etiquette.asp >> Archived messages after Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp >> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >> our blog (http://news.LegacyFamilyTree.com). >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp >> >> >> >> >> > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on > our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.2197 / Virus Database: 2437/5220 - Release Date: 08/23/12 > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
