Google| Subject | Re: Lenses and sharpening |
| From | Sandman |
| Date | 09/19/2014 16:35 (09/19/2014 16:35) |
| Message-ID | <slrnm1oga2.cnl.mr@irc.sandman.net> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Whisky-dave |
| Followups | Whisky-dave (1h & 32m) > Sandman |
In article <bc792678-99f5-4416-8002-0d75afbeadf2@googlegroups.com>, Whisky-dave wrote:
DPI is irrelevant in this context.SandmanWhisky-dave
That's what I just said. All adjustments you do are always done to the pixels of a preview file on disk. Exporting is not a paremeter. The original file is always left untouched.
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.
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.
For an image file, "dpi" is just a value that has nothing to do with the actual image data.
~s/final output/exported JPG/gSandmanWhisky-dave
The preview file is exactly like the would-be exported JPG file. It's the same. Nothing is different.
if it's not differnt in anyway from a final output then why preview comes to mind.
Since I've said no such thing...Whisky-daveEric StevensSandman
But it's not the same as the file you would - say - send to a printer.
It could be, sure. It's an ordinary JPG, and most printer drivers can handle them just fine. Again, you don't know what you're talking about.
I find this bit confusing if you're say the preview file is the same as the final export file, but perhaps that.s not what's meant.
-- Sandman[.net]
09/13/2014-
