Survey view in Library module is unfair

Whenever I'm using survey view in the Library module to select a few photos, and I'm having photos of both landscape and portrait orientation, either one of them is displayed considerably smaller than the other.
I think it would be nice if both orientations were displayed the same size, like in grid view, because when I select from a collection of photos, I slightly tend to favor photos that are bigger.
Marc

True.

Similar Messages

  • Images in loupe view of library module of LR4 are not always focusing. Why?

    Have just upgraded my whole system to get LR4 to work at an acceptable speed- including 16gb ram, 1TB hard disc. When importing RAW images are copying them to DNG and doing 1:1 prewiew at that time. After finishing working in the develop module when I try to look at the images in loupe view in library module many of the images remain unfocused- If i export as jpeg to hard disc they are fine.I need to be able to view ,rate and select images in LR

    Sound like this bug Mark? http://feedback.photoshop.com/photoshop_family/topics/lightroom_4_3_bug_pixelized_image_pr eview

  • Email Photo option Greyed out in Loupe View in Library Module on Mac in Lightroom 5.7.1

    In Lightroom 5.7.1 on Mac OX X Yosemite, when in the Library module, in Grid View the option to Email photo is available; however, when in the Loupe View, the Email Photo menu option is greyed out.  I have seen this question posted on the web and there are no answers anywhere.  Please address this issue as soon as possible since this appears to bug.

    Hey Scott,
    After expermienting extensively (well relatively speaking), I found that hardware wise, there needs to be a AC3 decoder on the end where the audio is being sent. And without that chip there the AC3 option won't work weather or not you can get it showing. Our interfaces don't have this AC3 option so theoretically speaking we would have to create/purchase an AC3 to Analogue converter, and take the outs to our monitors/inputs of our interfaces. There seems to be no easy hardware or software work around, because even if the software workaround were to get the AC3 option available it seems that it sends the AC3 option out over the SPDIF/ADAT connection meaning the software didn't really convert it it just made it possible to send the signal. So I didn't have any luck. In the end it seems you need a AC3 decoder/DA converter to 5.1 out which they sell but not at a reasonable price. Hope I was of "informative" assistance, if not any actual help towards solving the problem.
    -Walter

  • Different view to develop and library module

    Hello everyone, I have a big problem during my workflow, or when working images from the development at the end of the work as the images are like me and very sharp. But when I see in the library module are not sharp and the blacks are very mordibi. Below I post the link to see for yourself.
    MODULE DEVELOPMENT:
    MODULE LIBRARY:
    The problem is that when I export my image is identical to the form LIBRARY and not that beautiful clear form DEVELOPMENT. So I find myself not export images with crisp blacks and dishes.
    I already tried to delete the cache, but does not change anything, and I use 1:1 previews, you have no idea how to fix my problem?

    twenty_one wrote:
    Ah, now I see the rightside of that screenshot, with, as you say, sharpening 150 and NR 0. That's a combo it would never even occur to me to use, not in a hundred years...
    Anyway, I tried this with an ISO 1250 shot, but couldn't see any differences anywhere. But maybe you need to go higher.
    I've learned to never take anything for granted when reviewing LR forum posts. An ISO 1250 shot is probably too low with most DSLR cameras to see this issue. On my 5D MKII I could really only see the "lightening" between Develop and Library views with ISO 6400 raw images. It may also show up at lower ISO settings with images that are heavily underexposed (i.e. LR Exposure +1 and greater), and with smaller sensor cameras (1.6 crop, P&S).
    Gianlu24, keep in mind that Adobe increased the Sharpening amount from '100' in LR3 to '150' in LR4 when using a high 'Masking' setting. For most normal images and Masking settings you should use a Sharpening amount below '100.' There are two basic types–Capture and Output sharpening, each adjusted using separate controls. In addition you can apply both Global and Local Capture Sharpening in LR. These three articles by Laura Shoe may be helpful:
    http://laurashoe.com/2011/08/21/sharpening-in-lightroom-part-one-overview-and-capture-shar pening/
    http://laurashoe.com/2011/09/27/creative-sharpening-in-lightroom-sharpen-eyes/
    http://laurashoe.com/2012/07/11/sharpening-in-lightroom-part-three-output-sharpening/

  • Slight Color and Quality Shift when viewing RAW files for first time in Library Module.

    Hello,
    I have been shooting RAW for a while and have notice that after I import the images and then start to view them in the Library Module I will see a slight color and quality shift - almost looks like a white balance shift but not quite.   I was thinking that perhaps there was some automatic preset being applied but I don't have any presets at all.
    I am shooting with a Canon 1DX as well as 7D.  I have not checked to see if I get this situation with the 7D, but I know for sure that I get it with the 1DX.
    Today I was reviewing some images in Bridge and decided to open one of them in Camera RAW.   At that time I discovered that the camera's Image Style Settings were available, Faithful, Standard, Portrait, etc.  I noticed that the images did not have one of the camera styles applied to them but rather the Adobe Standard Style. At that point from within RAW I selected one of the camera's styles and bingo thats the kind of shift I am seeing when I first view an image in LR4 Library.
    So as far as I can tell the RAW images are getting the Adobe Standard style applied in LR.   I have no idea if this is a default behavior of if I have done something to cause it.  I'm also thinking that perhaps LR does not necessarily apply the Camera's Styles automatically even though the particular style has been set in the camera -- perhaps is not imported as part of the metadata during the import and thus defaults to the Adobe Standard.
    I guess what I need to know is a few things and I hope someone can educate this newbie! 
    1. Should I expect LR4 to apply the Style as set from the camera automatically or not at all?
    2. Can I prevent LR from applying the Adobe Standard Style and apply no style?
    3. Can I cause LR to apply the Style as set in the camera for the particular image to be appied automatically upon import?
    Thank you for any guidenace you can offer.  Of course if you need additional information or clarification please let me know.
    Scott

    That sort of describes it and may be exactly what is happening.  I have a shoot tonight and will pay closer attention to the process and behavior when I import.
    It is the full image that I see the shift on though.  Its not that the thumbnail and the full size image look different.  It the full size image looking one way and then shifting in front of my eyes.   
    What is frustrating is that I typically find that the image before the shift is better than what appears after the shift, so I find myself always chasing to get back to where it was and because its gone I'm chasing an invisible ideal, so to speak.   Ahhh...isnt that the life of a photographer though!
    It seems like its the last step in the render process -- if I could just figure out what it is and stop it I could finally figure out if I really care or not.  Its just so quick its tough to tell if indeed the first appearance is better.
    I'll feedback some more information when I get a better handle on this.
    Thanks for the reference.

  • Develop settings not showing up in library module view of image

    Hi there
    A quick question about an issue I have not seen before.  Imported a raw image .cr2 file from a Canon S95.  Opened develop module and applied clarity, vibrance and sauration adjustements.  Clicked back to Library module and the adjustments have not been made.  Clicked back to Develop and they are there.  Have tried closing LR5 and reopening - the image adjustments are still visibile in Develop, but not in Library.  Any thoughts?  Is this a software issue or a hardware issue (have just upgraded from LR4).  Thanks in advance.

    Hi Lee - I'll keep LR running for a while to see what happens.  I did notice that when I did the import of the image, the thumbnails of the images from the SD card were not immediately rendered.  it was possible to see the images by clicking on each one.  When I had previewed each image individually, the thumbnails were visible.  I suppose its possible that my hardware is running very slowly as welll.
    Thanks
    Chris

  • Wrong aspect ratio in Survey view

    I selected 3 photos and went to the Survey view. Of these photos, 2 were full frame, and 1 was cropped so it has a wider aspect ratio than the full-frame pictures. Survey view showed all 3 the same size, so the cropped one was stretched vertically and looked horrible. What's up with that?
    ...Lightroom 1.1 on Mac OS X.

    Thanks for the suggestion. That's a good tip to keep in my back pocket.
    I don't think this is what happened here though -- the preview image looks correct at all other views in Library mode (grid thumbnail, loupe view, and compare view are all correct; it's only screwed up in survey view). No amount of switching between views, or invoking Library->Preview->Render (1:1 or standard or telling it to discard and rerender) fixes the one in survey.
    It also turns out this is reproducible on demand, if I go from survey view on an uncropped photo straight to develop, crop, and return to survey: if I select 3 images, hit N to enter survey mode, click one of the images, hit R to go to Develop and enter crop mode, crop the image, hit E to return to Library, hit N to go back to Survey... the photo I just cropped has the wrong aspect ratio.
    If I quit Lightroom and reinvoke it, that corrects the bogus shape of the image in Survey view. I haven't yet found any other way to correct the shape.
    As an added bonus, if I go back and forth between Survey and Crop (using R from the Survey page), Lightroom will pretty quicly get in a state where it's stuck in Library and any attempt to go to Develop will say "unable to switch modules", and I have to quit and restart Lr before I can use Develop.

  • New problem rating image in Survey View when multiple selected - help!

    When we are in Survey View, normally we can have multiple images selected and when we use any star rating it rates only one image (the best), but midway through an editing session it just started rating all images selected at once.  I know that this is the standard way that ratings operate in Library (Grid View), but never before has Survey View (N) done this. We rebooted and optimized the catalog, but nothing has helped.  Please let me know if you have any fixed or thoughts as to what the problem would be.

    You are welcome Kevin.
    Another thing I find helpful when rating or labeling, is to engage the Caps Lock.  When a rating or label is applied by hitting a number, LR automatically advances to the next image in the filmstrip.  This works in all modules.

  • Survey View and Reordering Slideshow Images

    I'm sure you all know this one but I searched the forum to learn how to rearrange Slideshow images and the only answer was "...you just drag them around." That didn't seem to work for me. I went to Library Module, selected my Folder, selected Survey View (the choices down toward the bottom where one finds the various view options). In Survey View, one can move the images around into your personal order. Go back to Thumbnail view and images are where you want them -- so is your Slideshow. Please forgive me for injecting this when you probably know this but I didn't (and maybe someone else out there doesn't know this)

    No Such thing as a limited version. Only dif is a serial number. Press 'T' for Toolbar and one of the Icons on it is for Survey Mode. Keyboard Shortcut 'N'.
    Only thing Limited here is the amount of reading you've done in this fourm.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • Photos in Develop module look different when switching to library module

    Hello everyone this is my first post on adobe.  I ran into a problem today for the first time using lightroom 5.  I recently purchased lightroom 5 about 2 weeks ago and have been in love using it.  I have ran into 0 problems until today.  I uploaded some new photos and was going through them under the develop module editing the photos and what not.  When I am done editing I usually go to the library module and export them.
    Today I tried to do that exact thing and ran into this issue:  the colors in the photo are changing ever so slightly when I switch to the library module and are not exporting exactly as I edited them in the develop module. 
    I have tried changing the contrast/clarity to see if it would remain when switching and it does.  But for some reason the yellow on the flower in the picture becomes less vibrant when seen/exported from library module.  It is very frustrating because I spend alot of time editing the photo in a develop module and every transfers but the colors it seems.  It becomes more dull and less vibrant.
    It is not the photo itself.  I think it is something wrong with my lightroom?  I uninstalled and reinstalled and the same issue keeps happening.

    Just to clarify. When you compare the exported image to the original inside LR do they look the same when viewed together in the Library module, and how about when both are viewed in the Develop module? Are you using a wide gamut monitor and do you also use a hardware monitor calibrator? All of these things affect how images looks in LR and some are fixable, but others are not as Web Weaver posted.
    There is also another issue that can cause the Library module view and exported images to look different than they do in the Develop module:
    http://feedback.photoshop.com/photoshop_family/topics/afm8rbh6tnc31
    The solution is to view the image at 1:1 (100%) view size. You can also use more conservative Sharpening settings (i.e. lower) and more aggressive Luminance Noise Reduction settings (i.e. higher), which will significantly decrease the view difference.

  • Photos in Library module and after export look different than in Development module

    Hello,
    I experience a problem.
    After I update photos in the Development module, the updates seem not to be shown in the Library module. And when I subsequently export to Flickr, Flickr is also showing the original photo, not the adapted one.
    I noticed this the first time after making Blacks a bit deeper, causing a sunflower to become a deeper yellow. I thought that my adaptations were not applied in the Library module. After I checked with cranking down the Saturation all the way back (to almost black-and-white), that adaptation WAS applied in the Library view. So it had to be something else, causing the same color difference between the Library and Development modules.
    When I switch from the Library module to the Development module, I see a slight delay in applying my changes, but they are applied. Before they are applied, I can see that the original photo is shown and that looks the same as in the Library module and on Flickr.
    The photostrip on the bottom of the Lightroom screen also shows the original photos only, unless I go to the development module and select a photo (adaptations are applied in the photostrip after I select the photo, not before).
    After I played a bit more in the Development module, I found something strange in the Camera Calibration menu of the Development module. The Adobe Profile (my default) caused an obvious color difference between the Library (less saturated) and the Development (more saturated) modules. The Camera Standard profile also showed a (very) slight difference, but I was unable to notice the differences using the other profiles.
    So I was thinking (but it's only a guess), that the profiles are not applied in the Library view and on export, but they are in the Development module?
    I use Lightroom 5.6, Camera RAW 8.6.
    Please help me, as this is very annoying. I currently cannot export my photos to Flickr or anywhere else, unless I overcompensate before exporting. And I really don't want to do that. My Lightroom photo is my perfect photo, and I want to keep it that way...
    Many thanks in advance for any help,
    Peter

    Hi ssprengel,
    Thanks for your reply. Let me react to each possibility you mention and provide some extra information.
    - "Check your Export / File Settings / Image Format and make sure they are set to JPG not Original". Done that, it's not on Original, but on jpg. This would not explain why I see the difference in the Library and Development modules, by the way. But better to know for sure.
    - "...the most likely thing that is wrong is your color-management on your computer is not working properly". It is a PC with Windows 7. I have been using Lightroom for maybe 6 years and I never had this problem before. The last time I changed my setup is more than a year ago and this problem only started to happen a short while ago (after the update to Lightroom 5.6? I'm not sure, but that's the only thing that has changed lately). I use a Spider to create a custom profile that is correct for my setup and do a regular update on the profile.
    - "what brand and model of monitor do you have?" I have an EIZO FlexScan S2411W and use that for a long time as well. I chose this brand of monitors for its good color reproduction and I have been happy with it for years now.
    What I am not getting is why would all this show a difference between the Library and Development module? The only difference is the Lightroom software that is switching from one module to another, and that should deliver the same photo. I'm also stating in my first post that the differences are very noticeable using the Adobe Standard Camera Profile in the Development module. I have a feeling that the profile is part of the problem.

  • How to extract data from generic view and function module

    hi experts,
    can anybody give me the steps to extract data from generic view and  functon modules.
    thanks and regards
    venkat

    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
    https://websmp103.sap-ag.de/~sapidb/011000358700007535452002
    Hope it Helps
    Chetan
    @CP..

  • Specific Problem with Library Module 1:1 Preview Loading

    Hi everyone.  I've spent hours searching Google & forums for specific tips to try but I've found nothing that solved my problem.  I have a very specific problem loading 1:1 previews in Lightroom 3.3 while zoomed to 1:1.
    When I initially import a shoot (usually 3000 to 6000 images), I always render 1:1 previews during import.  My understanding is that this activity writes full-sized previews to the "Previews" folder, but I also have observed that .DAT files are created in the "Camera Raw Cache" folder.  I have my Lightroom Previews folder and my Adobe Camera Raw Cache folder on the **same** solid-state hard disk, which is dedicated to Lightroom.
    When I browse these newly-imported images in the Library module in Loupe view at 1:1 zoom, it's very zippy and fast to switch between images.  The images load without any message at a lower resolution, and then "snap" to full resolution after 0.25 to 0.5 seconds. No "Loading" message appears.
    However, once the previews have "sat around for a while", even if they are still supposedly available in the Previews folder, loading the image at 1:1 in Loupe as described takes 3-5 seconds.  Shortly after going to an image, the message "Loading..." is displayed (it doesn't say where from), and 3-5 seconds later, the full res image appears.
    This has nothing to do with changes to image settings requiring re-rendering of the preview.  These are images that I've imported but haven't browsed in a while.  I know that the previews are valid, because I can go to "Library > Previews > Render 1:1 Previews", and the task will complete within 20 or 30 seconds without re-rendering any photos after examining them and apparently finding that there are still valid 1:1 previews for all 4000 of them.  After doing this "re-render," the slow loading behavior is the same as before, because the re-render process always completes without actually updating the previews that it found are already there and presumably decided were still valid.  Discarding previews by "Library > Previews > Discard 1:1 Previews" and then trying to re-render them also does nothing, because LR3 apparently doesn't immediately delete the discarded previews, so they are picked back up again As-Is by the re-rendering process.
    If I had to guess at the reason for this behavior based on the symptoms, I would say that it seems like Lightroom is forcing itself to re-render 1:1 previews upon browsing to images that are older than a certain age (very possibly the same "30 days" after which the 1:1 previews are supposed to be discarded).
    Now, I've also observed that deleting the DAT files in the Camera Raw Cache folder has no adverse impact on load speed (which is what I would have expected to see if LR3 was looking for and loading images from this cache instead of the Previews folder).
    What this means to me is that once the image previews reach this "outdated" state, I can't get fast 1:1 browsing performance in Loupe with any reliable procedure other than manually deleting [in Windows Explorer] the entire Preview folder and then re-rendering the 1:1 previews for this shoot.  This is of course terribly inconvenient when there are recent previews that I want to save.
    Note:  I do not have any slowness under any circumstance when browsing at "Zoom to Fit".  This is only a problem when I'm browsing at 1:1 zoom (like when I'm comparing sharpness between a set of photos).
    Note:  For images with the slow behavior described, once the image has been loaded once at 1:1 zoom, it's henceforth snappy again when returning to the image (as if Lightroom was once again accepting the Preview file as valid).
    So, here's a summary:
    Previews (X:\Lightroom Catalog Previews\) and Camera Raw Cache (X:\Lightroom Cache\) are on same, dedicated, fast drive
    1:1 previews from recently-imported files load full-res at 1:1 zoom in less than 1/2 second.
    Older 1:1 previews take 3-5 seconds to load full-res at 1:1 zoom, even though the previews are supposedly being loaded from still-valid 1:1 previews in the Previews folder.
    I'm really tired, so i hope this makes sense.  I don't see how this could be a hardware problem, because I get good performance with recently-imported images.  I'm running LR3.3 on Win 7 Pro x64 with 8 GB of RAM and a 2.4 GHz Intel Core2 Quad CPU.  Never had LR3 beta installed - upgraded to 3.0 from the last 2.X version.  After upgrading, in response to this exact issue, I deleted my entire previews folder and rebuilt, but I continue to have the exact same problem on every shoot that I import.  It's most noticeable on the large shoots, because I end up having to browse at 1:1 zoom to compare a set of similar images.
    Only workaround I've found:  in Windows Explorer, manually delete the Previews folder.  Return to Lightroom and rebuild 1:1 previews.  This forces the previews to be rebuilt for all images.
    Another possible workaround I am going to experiment with: setting the Previews to "Do Not Discard", in case the defualt "Discard after 30 days" that I've used is causing or contributing to the problem.  If Lightroom is actually discarding the images after 30 days but forgetting that it had discarded them when asked to re-render 1:1's, maybe setting to "Do not discard" will bandage that problem by never discarding them to begin with.
    All right, I'm falling asleep at the keyboard.  I'm afraid to add more details as they may become incoherent.  Hope to hear some good news, as fixing this problem would make my LR3 experience so much more pleasant.
    Can anyone assist with this problem?
    - Tyson

    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    The behaviour after previews have been around for a while (i.e. previews for unedited images) is not normal. There have been a few other reports of similar behaviour, but no real clues as to why it happens.
    Yes - this is my problem.  Previews should still be valid, and "Library > Previews > Render 1:1 Previews" says the images are still valid, but then Loupe rebuilds them anyways.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    If everything was working correctly, the setting for discard shouldn't have any effect on whether the previews go stale or not. ...
    My understanding is that if everything were working as intended, the "setting for discard" that I was referring to (Edit > Catalog Settings > File Handling > "Automatically Discard 1:1 Previews") should be the sole determinant of whether 1:1 previews must be rebuilt for images with unmodified settings.
    For example, if I import an image and render a 1:1 preview, and if I set the "Auto Discard 1:1" setting to "30 Days", and if I make no changes to the image's settings, then I would expect that the image should render quickly (under 1/2 second) at 1:1 zoom in Loupe view for the next 30 days.  On the 31st day, I would expect the image to take longer to load as a new 1:1 preview was rendered and stored, and then I would expect this new preview to be retained for another 30 days.
    I would furthermore expect that the 30-day counter would be reset every time the image was re-rendered (i.e. if I go into Develop and change something).
    To a certain extent, this is functioning correctly on my system.  When I go to one of these "problem images" that inexplicably load slowly, returning to them subsequently is quick.  I think my problem is just, as Rob suggested, that some part of Lightroom's "brain" has wacky ideas about whether an up-to-date 1:1 preview exists or not.
    If I choose to "Never" automatically discard 1:1 previews (which is what I just switched to), then I should "Never" see unmodified images taking 3-5 seconds to "Load" at 1:1 zoom in Loupe.
    Since I just nuked my Previews folder again last night and re-rendered 1:1's overnight for a 3000 image shoot, it might be a while before I start encountering this bug again.  I will certainly post any further related experiences here and will keep checking for anyone who has further insight.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    ...we know that Lr3.4 RC fixed the manual discard bug, so, if I were you I would focus any further tests on Lr3.4RC.
    Thanks for pointing this out.  I will upgrade to 3.4RC - at least then I will be able to force a rebuild of previews from one shoot without having to manually delete the previews for my entire catalog.  I'll no longer have to throw out all the food in the refrigerator just because something smells funny.
    function(){return A.apply(null,[this].concat($A(arguments)))}
    Ian Lyons wrote:
    The DAT files are created at the same time as Library previews. However, they are only used in Develop module.
    Yes, I definitely agree with this (although, the Cache is probably also used while rendering new previews after "Quick Develop" changes in the Library module....).  I posted my observations to this effect just in case someone else wondered the same thing I did.  It is clear that the DAT files get written every time a preview is rendered for RAW file.  Rob, now that I'm thinking with a clearer mind, I think the only thing these Cached files are used for is if you "return" to recently rendered settings in Develop or Quick Develop - then, that particular combination of settings yields a match in the cache, and LR loads the image from the Cache into Previews and onto the screen.  It is logical that the cache wouldn't help us when going to new settings, because the new settings would create a partially or completely different rendering than any other combination of settings.  Adobe may be going to more advanced levels of "reusability" than this, but I'm sure this is the general state of things.
    You may want to open back up write access to that Cache folder...
    Thanks, Rob & Ian!
    So, my question, or bug report, still remains for now - why am I biting into a bag of chips marked "Fresh" and finding them Stale?  And why does it say "Paper Jam" when there is no paper jam?

  • Lightroom 3 not creating folders in Library module

    Normally a folder corresponding to the directory I imported my images from is added to the FOLDERS bar in the LIBRARY module.
    I didn't realize until today, when I tried to go back to some older photos, that since the beginning of August LR has not been creating a folder with each import. The only way to navigate to those photos is using CATALOG -> ALL PHOTOGRAPHS.
    I tried adding a folder with the "+" but that just tries to import photos that are already in my catalog.
    Is there a setting that changed? Is this a bug?
    Thanks,
    -Andy

    Ah, well, that makes sense.  If you are "adding" them, then the images themselves are merely being referenced, and LR will not create new folders for them, but use the folders you already have them in.  So in order for them to be in the correct format, you'd have to have them in the correct location you want them referenced as.
    If you do, indeed have them in the proper format as you listed, then your most likely problem is you are selecting only the bottom layer, i.e, the final month folder for import.
      If you want the entire import path to show up, I believe you have to select the top level one, and use "include subdirectores" to let it find them below that.
    This will, of course, scan all of your other folders under there, and most likely identify lots and lots of duplicates, which it will then ignore.  But it will take a bit longer for the software to relalize it already has them and uncheck the ones it thinks it knows about.
    From my point of view, doing something similar, I use "move" instead to get it right without having to scan all the potential duplicates.  It doesn't take much more time if the images are on the same disk already.  Moving between disks adds time, but on the same disk it doesn't (effectively, anyway).  It also means that the images get put into the date/format under my top level project automatically, I don't have to create the original structure to begin with. I just load them all into one directory on the same disk, hit import, select the top level project they go into, and let it organize by date.  It displays on the large import window what directories it will be creating and how many images will go in each one.
    Anyway, I think that should give you the right ideas!
    Cheers!

  • Develop module & library module aren't matching

    When I am editing, my photos look how I want them to in the develop module, but when I switch over to the library they look different. Some photos it doesn't apply the clarity, highlights, noise reduction, or sharpening. I haven't had this problem up until a month or two ago. It used to be the same between the two modules and I no problems editing. Now it's a pain to edit because I have to switch to the Library to see what the image is really looking like, go back to develop to try and change it, but cant end up getting it to look how I want. Images look the same zoomed in, but not in normal view. I am on Windows, Lightroom 3.6. I have tried reupdating the software, downloading an older version. also updated my video driver, and nothing helped. trying to avoid reinstalling all of lightroom because I do not want to lose any previewly modified images.
    first one is the view from develop. you can tell its a lot more noisey.
    second picture is from the library. it's a lot more smooth.
    so basically my images aren't being shown correctly. I have looked through a lot of discussions on here and no one seems to have an answer...please help me! editing should be fun, not frustrating.

    Rivosyke wrote:
    Thanks for the response. This appears to be more the issue with image that is exported is using the algorithm for the library module as opposed to the changes made using the develop module. The histograms are different when switching between the two modules (Library/Develop) for the same image.
    Camera: D7100
    Image Type: RAW
    ISO: 3200
    Bingo! You're using an ISO 3200 image with fairly high sharpening settings, which is going to increase noise in the image. If you view the image at 1:1 in the Develop module the noise should very visible. The Develop module and Library module 1:1 previews should both show the noise and look very close to each other. The reason why less than 1:1 Zoom previews (i.e. Fit, Fill, 1:4) and histograms look different is explained in my reply #29 under this heading MORE THAN YOU PROBABLY NEED TO KNOW (For Techno Geeks & Nerds Only). The Export module uses the same Bicubic algorithm as the Library module, which is why the Library module's preview is more accurate than the Develop module. Virtually all image editors (not just LR) use the same Bicubic resizing algorithms and will produce the same discrepancy when compared to LR's Develop module preview.
    Fortunately there is a very easy solution to this issue. Unfortunately many people prefer to complain, say it is a LR "bug," and don't listen further to suggestions on "fixing" the issue. If you fall into the latter camp don't bother reading further! Sorry if this sounds crass and cynical, but I can only provide advice. Whether you believe me and try it is your decision! It works for me using five different camera models with both raw and JPEG image files.
    High ISO and/or High Sharpening Preview Discrepancy Fix
    1) Set Develop module to 1:1 Zoom View.
    2) a. Adjust Sharpening panel settings for desired look.
        b. With noisy images it's best to keep the Detail setting no higher than 35.
        c. Try using the Masking slider to reduce noise in even toned areas.
    3) Increase Detail panel Color setting until the color noise is barely visible.
    4) If there is still some residual color noise try increasing the Color detail setting to ~80.
    4) Increase the Detail panel Luminance setting until noise is barely visible or gone.
    5) If the image has lost significant sharpness try increasing the Luminance Detail setting to ~80.
    6) If necessary go back to steps # 2-5 and make small adjustments to the Sharpening and NR settings.
    Now compare the Develop and Library previews at Fit view or better yet at 1:8, 1:4, or 1:3. They should look very close to each other with the Develop preview very slightly sharper. Full-size and reduced size Exports should look very close to what you see in the Develop module. When Resizing images don't forget to add Export Output Sharpening. When images are Resized the Output Sharpening setting has more influence on image sharpness than the LR Develop Sharpening settings. For most images the Screen Standard setting should produce crisp images. If you want more try the High setting. I generally find the Screen Low setting produces the most natural look. YMMV dependent on lens performance, camera shake, focus issues, or simply poor lighting (cloudy, foggy, etc.).

Maybe you are looking for