Google| Subject | Re: Lenses and sharpening |
| From | nospam |
| Date | 09/20/2014 05:51 (09/19/2014 23:51) |
| Message-ID | <190920142351460562%nospam@nospam.invalid> |
| Client | |
| Newsgroups | rec.photo.digital |
| Follows | Eric Stevens |
| Followups | Eric Stevens (1h & 8m) Savageduck (1h & 26m) > nospam Sandman (7h & 7m) |
In article <s0qp1adosbs2srb293smuem1f5cnml763b@4ax.com>, Eric Stevens <eric.stevens@sum.co.nz>wrote:
why would you be sending a highly reduced jpeg?SandmanEric Stevens
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 would send my best file to the printer, not a highly reduced JPG.
questions like this mean you don't understand how it works.Eric StevensSandmanSandmanEric Stevens
The *only* point Lightroom loads the original file and applies the rendering chain in RAM is when you're viewing an image in 100% zoom.
Or when you export the image.
Depends on how you export it. If you export it as a low-res highly compressed JPG, it can use the preview file. Chances are that it doesn't, but it certainly could, since the preview file *is* the current pixel data of the image.
So what happens when you want a high quality TIFF of the same size as the original file? Do you expand by resampling your low-res highly compressed JPG?
it *always* uses the original data. the cached previews are a speed optimization for the user interface.
09/13/2014-
