Google| Subject | Re: Lenses and sharpening |
| From | Whisky-dave |
| Date | 09/19/2014 18:08 (09/19/2014 09:08) |
| Message-ID | <d191232f-51f0-42e7-b628-05c21809004b@googlegroups.com> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Sandman |
| Followups | nospam (42m) Sandman (2h & 50m) |
On Friday, 19 September 2014 15:35:39 UTC+1, Sandman wrote:
Sandman
In article <bc792678-99f5-4416-8002-0d75afbeadf2@googlegroups.com>, Whisky-dave wrote:
So what is the point of a preview file, you've not explained that.Whisky-daveSandman
Do you happen to know whether or not this preview file is a copy of the original file but 'rendered' at 72DPI rather than the final copy which is mostly likely to be 300+ DPI for printing ? A little like doing a preview of soemthing you want to scan.
DPI is irrelevant in this context.
I used preview files in the 90s with lightwave. I had rending projetcs that lasted most of the day, you could set the preview to a particular resoulotion the higher the res the longer it took. if yo wanted a rought idea of what something loked like you'd use low res and you couls see teh image in minutes but a full render would take hours.
Above you've said nothing .Whisky-daveSandman
And would this preview file be differnt (differnt DPI) if you were using a retina or 4K/8K screen.
You don't know how DPI works. The *screen* is of a certain DPI, not the image. Everything shown on a screen is shown in a specific DPI. This has nothing to do with the preview file.
So what purpose does the preview file have, or why create a preview file ?
For an image file, "dpi" is just a value that has nothing to do with the actual image data.again saying very little, or is it that you don't understand ? Are you saying that if you pixilate or use filers on a 1Mb image and a 1Gb image the time to process this will be the same.
09/13/2014-
