-
1. Re: Does rendering previews larger than max native resolution benifit you.
Lee Jay Jan 12, 2013 6:54 AM (in response to help!!!!!!!!!!)Previews are for library not develop.
-
2. Re: Does rendering previews larger than max native resolution benifit you.
thedigitaldog Jan 12, 2013 1:21 PM (in response to help!!!!!!!!!!)help1111111111111111 wrote: Does that extra resolution translate to greater detail when working that close?
Yes! But it has to be rendered at some point and depending on where you're viewing this (which module) it might have to happen twice. The setting you refer to is one. Then there's the Develop module which is where you want to do the precise work (the preview here is most accurate).
-
3. Re: Does rendering previews larger than max native resolution benifit you.
help!!!!!!!!!! Jan 12, 2013 1:38 PM (in response to Lee Jay)Ah thank you! I thought the preview was the temporary redering you get until the photograph is fully rendered in the develop module.
-
4. Re: Does rendering previews larger than max native resolution benifit you.
help!!!!!!!!!! Jan 12, 2013 1:41 PM (in response to thedigitaldog)I rarely look at things in the library. I generally scroll through thumbnails at the bottom of the develop module, because most of the time, I'm going to work on a file. I just don't know which until I look at them. So the rendering size is to speed up loading of many files to view in the library then!
-
5. Re: Does rendering previews larger than max native resolution benifit you.
help!!!!!!!!!! Jan 12, 2013 1:43 PM (in response to thedigitaldog)To be perfectly clear, This image preview resolution setting has no impact on the image I'm working on, while in the develop module.
-
6. Re: Does rendering previews larger than max native resolution benifit you.
areohbee Jan 12, 2013 2:19 PM (in response to help!!!!!!!!!!)You may want to re-think your workflow.
Image sequencing in Develop module is sloooooooowww... - no way around it (other than using EditInLightroom plugin, which reduces resolution, temporarily, in favor of develop module speed, but even then it's slow compared to Library module). note: last 4 images developed are cached in ram, those are fast to get at, but the rest: slooooooooowww...
Image sequencing in Library module is faaaaaaaaaast - if you have up-to-date previews, otherwise it's slooooooowww too.
So the trick is to make sure library previews are up-to-date, then sequence images in the library module - when you hit the image(s) you want to edit, press 'd', or another develop module keyboard shortcut... - then, upon edit completion, return to library module, via 'e' or 'g', or some other preferred method, for more sequencing.
Bottom-line: switching between library & develop module ad-infinitum is a fact of Lightroom life, if you are one of those who can't "do everything there is to do in one module before switching to the other" (I'm one too), and you want to use Lightroom most efficiently.
Maybe one day, Adobe will integrate the lib & dev modules and/or enhance Lightroom to better cache image viewing data, until then... - good luck.
Rob



