Library Preview Rendering Slow

I'm sure I'm missing something here and am hoping someone can point me in the right direction. I just purchased lightroom 2.3 primarily as a workflow tool for the RAW photos I take at sports events. The first step in my process is to review all the photos and remove the ones with poor composition and ones that are out of focus so that I don't spend time cleaning them up before I do any cropping.
My problem is that the rendering of the preview thumbnails seems to take an inordinate amount of time before I can see the thumbnail in enough quality to make a decision on the focus quality. I opted to invest the time up front and generate 1:1 previews during the import process. I've got the thumbnails sized to display two thumbnails with the sidepanels hidden to use as much realestate as possible. However, when I move from thumbnail row to thumbnail row, at least one of the thumbnails is initially displayed in a blurry format and takes approximately 2 - 4 seconds to display in it's final state.
Considering I have 353 photos to review, I'm looking at sitting 17 minutes total just waiting on the final rendering of thumbnails to decide on whether they're in focus or not. This just doesn't seem right if I selected to pre-generate 1:1 previews. So I've got to have something set wrong somewhere. Any ideas or direction would be greatly appreciated!
Dale

Thanks all for your thoughts and ideas. It looks like I'll just have to live with the multiple pass slow rendering in Lightroom if I want to continue to use it. I ran a test with the same batch of photos in Capture One LE, the product I intended to replace with Lightroom. Once the folder and photos were imported into Capture One and thumbs rendered for the first time, moving from one large size representation of a photo to the next (there's no "library" module, it looks more like the LR Develop module and all work is done from there) took significantly less time than in Lightroom (less than 1 second).
Some other notes from the comments above:
- yes, I was using very large thumbnails to scan through the 300+ photos and filter out the bad ones and yes it requires me to do a lot more scrolling. Annoying, but necessary for me. One of the more difficult things for me to do is determine if a shot was in focus or not. This decision requires a large thumbnail for my old eyes ;-)
- I have 100Gb free on my catalog drive and 200Gb free on my data drive. I can't imagine Lightroom would require any more to render thumbnails and display photos in the develop module more quickly.
Thanks again everyone!

Similar Messages

  • Preview rendering Very Slow

    Hi,
    Can anyone help with Preview.app slow rendering issue for large PDF files, it is very slow after upgrading to lion. (AutoCAD drawings that are PDFed)
    Small PDF documents are fine.

    Hi Guys I work with a lot of pdf files with being a student at uni and not sure these tips might help. 
    Try an app called skim which is free it handles pdfs nicely and looks similar to the preview app. 
    Also if a pdf is slow to scroll try selecting all the pages goto file print.  Then on the bottom left hand side of the print window select pdf and then save as pdf.  I have found on some pdfs (usually the ones in black and white and look like a photo copy) using the the print save as pdf option has then allowed me to view a pdf fine in the preview app without any issues.  Hope this is useful.
    I suspect its to do with pixels per inch or dots per inch of the document.

  • Preview rendering question

    Hey all, Mike the newbie has more questions
    I imported about 6k images into lightroom and I'm working on organizing them within the collections but my question previews. As I scroll through the library there is a delay in seeing the images as they seem to render realtime.  This seems to impact me more when the library has larger images and I'm scrolling down more.
    I imported the images using the 1:1 previews, would going with standard preview produced a better performance result?
    How about none?  I read the FAQ but it really doesn't address whether the rendering is altered by choosing this the different preview options.
    My second question about previews is there any option to rebuild them, for instance say there is a speed bump with using the standard previews, can I delete the current ones and recreate/rebuild them somehow?

    I imported the images using the 1:1 previews, would going with standard preview produced a better performance result?
    How about none?
    That's strange. There might be some small performance penalty of having 1:1 previews over standard (since they are physically bigger), but it should be marginal. What is your machine specs?
    My guess is either the machine is too slow or your expectations are too high (Lightroom is not speed daemon). Are your sure the previews have actually be built?
    My second question about previews is there any option to rebuild them, for instance say there is a speed bump with using the standard previews, can I delete the current ones and recreate/rebuild them somehow?
    Yes, you can discard 1:1 previews and rebuilt standard. Use the Library>Previews menus.

  • Library Preview displays at lower resolution than Develop Preview

    I recently bought a Nikon D7100.
    I took some test shots and imported the images to Lightroom 4.4, then generated 1:1 previews for all the images.
    Previews zoomed to 1:1 in Library Mode are noticeably soft.  The image below is a screen shot of the Library preview:
    Moving to Develop View produces a higher-resolution 1:1 preview.  The image below is a screen shot of the Develop preview:
    Look at the bricks and window screens to see the difference.
    This difference occurs immediately after import (with a User Preset applied during import).  Once any Develop work is done, the Library preview updates and displays at full resolution.
    This problem makes doing initial editing/selection of images time consuming, because I can't determine the sharpness/quality of imported images until I've done some kind of Develop adjustment on each image.
    If anyone has a circumvention or solution to this problem I will appreciate receiving it.
    Thanks,
    Brett Rowett
    Sacramento CA

    BRSac wrote:
    I recently bought a Nikon D7100.
    I took some test shots and imported the images to Lightroom 4.4, then generated 1:1 previews for all the images.
    Previews zoomed to 1:1 in Library Mode are noticeably soft. 
    This difference occurs immediately after import (with a User Preset applied during import).  Once any Develop work is done, the Library preview updates and displays at full resolution.
    You said "then generated 1:1 previews for all the images," so I assume you manually selected Library> Previews> Render 1:1 Previews from inside the Libray module. Selecting 'Render Previews : 1:1' in the LR Import module under 'File Handling' will automatically render the previews on import.
    There are two possibilites why you are seeing low-res 1:1 Library previews:
    1) The Previews were still being created in the background after import, and you are trying to edit images that  do not yet have a 1:1 preview.
    2) You inadvertently cancelled the 1:1 preview rendering process by a) closing the progress bar in the upper lefthand, or b) closing LR before completion of 1:1 Preview Rendering.
    I would NOT reccomend discarding 1:1 Previews since that will create the very situation you are complaing about in this post. If you are low on hard drive free space then this recommendation would be helpful.

  • 6720c & MU-45 - music library is very slow

    Last time I checked MU-45 compatibility with my phone it was listed and I ordered the memory-card, but to my surprise the music library became painfully slow. In fact slower than my Qtek 8300 from '05 which had an ARM9E @ 200 mhz and Windows Mobile 5, but my five years newer phone with this memory card is rendered nearly useless.
    Entering the music library and select a group, wait about seven seconds, select album another seven seconds, select song... before with a 8 GB (class 6) card it was instantaneous and quite zippy. This Nokia/ SanDisk class 2 card benches about the same as my last card with a read speed of 14 MB/s.
    There is something terribly wrong with accessing the music library...
    My phone is up-to-date and all that, checked MU-45 compatibility list right now and 6720 Classic is no longer listed as before, if one Google -> 6720 AND "mu-45" and go to the fourth page, hit number eight and press the cached (4. sept. '10)  version of the Swedish page you'll see back then that it was listed (long winding road, but url was not accepted).
    So I wonder what this means, shall I wait for an update or return the card as it's no longer officially supported?

    I still reckon something else is wrong and I think that the file in question is stored on the phone itself and not on the memory card since music can be stored on the phone and memory card at the same time and still show in the library.  Once i had to do a hard reset of the phone because my Contacts library was corrupt, so corrupt libraries on Nokias is not so uncommon - I couldn't fix the corruption any other way.
    So I suggest a hard reset of the phone.  Hard reset will wipe all info on the phone so backup your data first.  Hard reset code is  *#7370#
    Sorry I can't give better advise.
    I don't think that the memory card should affect the speed of the Music Player application on the phone since the music player app stores a file describing the music library, and doesn't actually access the music on the card to show the files.  
    Just my opinion...

  • Ideal Preview rendering szize?

    I'm confused about the ideal preview rendering size. My monitor res is 1152x864. I rendered the previews at 1640 or whatever it is, and my 130 GB files collection produces an 18 GB library. This seems huge.
    Do I need the previews rendered at that size, given my monitor res? I thought the LR produces 1:1 previews when needes.
    Guidance please!
    Thanks!
    Reid

    So what about this idea?
    Why not make all those previews easily accessible from outside LR? They could be named the same as the images they refer to and be stored in a corresponding folder structure. Why that? To be able to use them in other applications without having to open LR and export jpegs first! I'll happily set aside enough disk space even for 1:1 jpeg renderings as previews. (Sounds exactly like what Aperture already does ;-)
    Alexander.
    Canon EOS 400D (aka. XTi) • 20" iMac Intel • 12" PowerBook G4 • OS X 10.4 • LR 1 • PSE 4

  • Premiere Pro 2014.1 rendering slower?

    Is anyone else finding rendering slower with 2014.1?  My hardware configuration (PC) used to render my sequences in about real time but now they're taking about 2X real time.  I've got the same NVIDIA GPU I had before, have updated the drivers and PP says it will use it but I see no activity on it now.  It's hard to compare because I can't go back to 2014.  I get the same time whether I queue the render to AME or do it totally within PP.  I'm tempted to go back to CC (pre-2014) and make some comparisons but haven't done it yet.

    I gather that by "render" you mean exporting to encode an output file, yes? With Premiere, we generally reserve the term "render" specifically in reference to rendering preview files for smoother playback within Premiere; for creating an output file, we use the terms export and encode. I'm not saying "render" is incorrect--I know that's the common parlance with other NLEs. Just calling it out to help avoid confusion hereabouts.
    As to the actual issue:
    what format & preset (or custom settings) are you using?
    Are you sure that all the export settings are the same as before? Any chance that before you were encoding VFR, One Pass but now it's Two Pass, for instance?
    When you say "PP says it will use [the GPU]," do you mean that in the Project Settings panel, Renderer is set to GPU?
    Exactly what graphics card do you have, and what driver version?
    Is this a project created in a prior version and converted to 8.1? If so, can you toss together a simple sequence in a fresh 8.1 project and see if encode times are longer than expected?
    If it's a new 8.1 project, are all the particulars of the sequence roughly the same: resolution of the source; sequence settings, including the Preview File Format/Codec; effects in use, ...?
    As to the fact that the GPU shows no activity, that may be expected. In case you're not aware, the GPU is not used for all encoding. See this thread for more info: Mercury, CUDA, and what it all means. Of course, if we're dealing with a pretty clean apples:apples comparison and you checked GPU usage while encoding in prior versions, then you know for sure whether 2014.1 brought a change.

  • Library - Previews - Render Standard-Sized Previews

    Is there a limitation to the number of images that Lightroom processes when you select to manually Render Standard-Sized Previews?
    I deleted my preview folders (Lightroom Catalog Previews.lrdata) because it was previously set to highest quality at highest resolution which was chewing up disk space needlessly (I changed the settings down but didn't know if Lightroom would re-render already existing standard previews).
    Lightroom re-created the folder when it re-started and I then selected all the images and selected Library -> Previews -> Render Standard-Sized Previews
    But this finished in awfully quick for 8000 images, so I ran it again, and it started to render more (different) images. And then I did it again, and it started to render more (different) images, and so on. I've done it enough times now that it has finally completed all of the images - but it seems like it only renders only a few hundred images at a time?
    Am I missing something - why doesn't it render all the images you have selected?
    I've observed this in both LR 1.0 and LR 1.1 on a Mac.

    The direct link seems like one of the things Ian Lyons might include with the stuff at the top of the UtoU main forum page along with the FAQ listing and other items.
    Don
    Don Ricklin, MacBook 1.83Ghz Duo 2 Core running 10.4.9 & Win XP, Pentax *ist D
    http://donricklin.blogspot.com/

  • Hi all.When pressed play and make some changes in loop (eg fade in fade out) are very slow to implement, and also the loops from the library are very slow to play, corrects the somewhat self so is the Logic??

    hi all.When pressed play and make some changes in loop (eg fade in fade out) are very slow to implement, and also the loops from the library are very slow to play, corrects the somewhat self so is the Logic??

    Hey there Logic Pro21,
    It sounds like you are seeing some odd performance issues with Logic Pro X. I recommend these troubleshooting steps specifically from the following article to help troubleshoot what is happening:
    Logic Pro X: Troubleshooting basics
    http://support.apple.com/kb/HT5859
    Verify that your computer meets the system requirements for Logic Pro X
    See Logic Pro X Technical Specifications.
    Test using the computer's built-in audio hardware
    If you use external audio hardware, try setting Logic Pro X to use the built-in audio hardware on your computer. Choose Logic Pro X > Preferences > Audio from the main menu and click the Devices tab. Choose the built in audio hardware from the Input Device and Output Device pop-up menus. If the issue is resolved using built-in audio, refer to the manufacturer of your audio interface.
    Start Logic with a different project template
    Sometimes project files can become damaged, causing unexpected behavior in Logic. If you use a template, damage to the template can cause unexpected results with any project subsequently created from it. To create a completely fresh project choose File > New from Template and select Empty Project in the template selector window. Test to see if the issue is resolved in the new project.
    Sometimes, issues with the data in a project can be repaired. Open an affected project and open the Project Information window with the Project Information key command. Click Reorganize Memory to attempt to repair the project. When you reorganize memory, the current project is checked for any signs of damage, structural problems, and unused blocks. If any unused blocks are found, you will be able to remove these, and repair the project. Project memory is also reorganized automatically after saving or opening a project.
    Delete the user preferences
    You can resolve many issues by restoring Logic Pro X back to its original settings. This will not impact your media files. To reset your Logic Pro X user preference settings to their original state, do the following:
    In the Finder, choose Go to Folder from the Go menu.
    Type ~/Library/Preferences in the "Go to the folder" field.
    Press the Go button.
    Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro X User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro X, then you may also wish to delete the com.apple.logic.pro.cs file from the preferences folder.
    If you have upgraded from an earlier version of Logic Pro, you should also remove~/Library/Preferences/Logic/com.apple.logic.pro.
    Restart the computer.
    Isolate an issue by using another user account
    For more information see Isolating an issue by using another user account.
    Reinstall Logic Pro X
    Another approach you might consider is reinstalling Logic Pro X. To do this effectively, you need to remove the application, then reinstall Logic Pro X. You don't have to remove everything that was installed with Logic Pro X. Follow the steps below to completely reinstall a fresh copy of Logic Pro X.
    In the Finder, choose Applications from the Go menu.
    Locate the Logic Pro X application and drag it to the trash.
    Open the Mac App Store
    Click the Purchases button in the Mac App Store toolbar.
    Sign in to the Mac App Store using the Apple ID you first used to purchase Logic Pro X.
    Look for Logic Pro X in the list of purchased applications in the App Store. If you don't see Logic Pro X in the list, make sure it's not hidden. See Mac App Store: Hiding and unhiding purchases for more information.
    Click Install to download and install Logic Pro X.
    Thank you for using Apple Support Communities.
    Cheers,
    Sterling

  • Map Builder Preview rendering errors

    I am having problems using Map Builder. I have wasted quite a bit of time trying to fix these problems assuming I was doing something wrong, or something was wrong with my data.
    Error 1: I create a map using 2 themes. One theme is a geometry theme of topo edge primitives. The other is a topology theme of features built from those primitives. The geometry theme is assigned a red line style. The topology(feature) theme is assigned a blue line style. the geometry theme is listed first, to draw first. I expect to see the red overdrawn by the blue. The preview show red lines. When viewed in Acquis Data Editor, this map displays as expected (blue lines) and when a feature is removed (disassociated from the topo primitive) the underlying primitive shows up as red. When I stop and restart Map Builder, the preview rendering is as expected, blue on top.
    Error 2: I create a map using 1 theme. This theme is a geometry theme of topo edge primitives. I assign node and edge styles. When I preview the map, the nodes (only one node per edge) are displayed at the center of the straight edges, at what appears to be mid-distance between the end points of the edges of the shaped edges (not on the edge), and in the center of rings created by edges that have the same start and end node. They look like they are attempting to be what ESRI calls label points. Again, when I view this map in Acquis Data Editor, the nodes show up on the ends of the edges where I usually tend to look for nodes to show up. Stopping and restarting Map Builder does not fix this rendering problem.
    Are these known bugs and when can I expect to use the preview button reliably?
    Alden

    For the red line style, L.EDGE, the xml def is:
    <?xml version="1.0" standalone="yes"?>
    <svg height="1in" width="1in">
    <desc/>
    <g class="line" style="fill:#FF33FF;stroke-width:1.0">
    <line class="base"/>
    </g>
    </svg>
    For the blue line style, L.FEATURESTYLE, the xml def is:
    <?xml version="1.0" standalone="yes"?>
    <svg height="1in" width="1in">
    <desc/>
    <g class="line" style="fill:#3366FF;stroke-width:1.0">
    <line class="base"/>
    </g>
    </svg>
    For the geometry (edge primitive) theme, TOPO_EDGE, the xml def is:
    <?xml version="1.0" standalone="yes"?>
    <styling_rules>
    <rule>
    <features style="C.FACE"> </features>
    </rule>
    <rule>
    <features style="M.NODE"> </features>
    </rule>
    <rule>
    <features style="L.EDGE"> </features>
    </rule>
    </styling_rules>
    For the topology(feature) theme, GLOBAL, the xml def is:
    <?xml version="1.0" standalone="yes"?>
    <styling_rules theme_type="topology" topology_name="MGF_TOPO">
    <rule>
    <features style="L.Featurestyle"> </features>
    </rule>
    </styling_rules>
    For the base map, TEST2, the xml def is:
    <?xml version="1.0" standalone="yes"?>
    <map_definition>
    <theme name="TOPO_EDGE"/>
    <theme name="GLOBAL"/>
    </map_definition>
    As I said earlier, this does display blue lines after a restart of MapBuilder but upon first creating this map and themes, the initial display is red lines.
    As to error 2: I understand now that Acquis probably does a specialty mapping of metatdata and uses the NODE$ table, applying the style definition for the edge theme (M.NODE) to display them.

  • Weird colours with QuickTime sources, broken preview renders & crash at exit (CS4)

    Hi erveryone,
    I have a strange problem in Premiere Pro CS4: Allmost all QuickTime MOV that I put in the timeline show weird, broken colours. At first I thought this was a problem with a specific codec, but I have now tried several codecs and pretty much every one shows up equally broken. The only codec that seems to work fine is the one that my Canon EOS 550D produces (1080p, H.264 I believe), but that one does not play smoothly (not that I would expect it to do on my machine). Strangely, H.264 in lower resolutions fails again. Other containers seem to be unaffected. Here is a screenshot of the effect:
    Also, my preview renders (when rendering the effecs on the timeline) are similarly broken. They behave a bit erratically. Sometimes they are just black, showing nothing and sometimes they show a still frame of one of the previously viewed videos. Colours are messed up in a similar way, so I suspect a connection. Here is the same clip from the screenshow above, preview-rendered:
    Also, upon exiting Premiere, it usually crashes. This is less of a problem, but still very weird behaviour.
    Any ideas how I could solve this?
    Infos about my system which might be of relevance:
    Adobe Premiere Pro CS4 (education version)
    Windows Vista 32bit (SP2, all current updates installed)
    4GB RAM
    Intel Core2 Duo
    ATI X1300 Pro  256MB (with newest available driver)
    QuickTime 7.6.6
    The system has been freshly installed (from factory image - hence the older OS) so no malware or anything similar should mess anything up. Only software installed except the Creative Suite is Google Chrome.
    On my laptop (Win7 64bit, Intel i5, no separate graphics card, same QT version) none of these problems appear.
    Greetings,
       Florian

    I think I found the solution. Some further digging revealed that I did not have as previously assumed the latest driver for my graphics card installed. I was mislead because the manufacturer (Dell) did provide some updates, but not all of them (none in the past two years to be exact). I grabbed the newest driver kit from the ATI website and installed it. Strangely, the installer produced several errors and I get another error message at startup, but I think only the control software was affected and not the driver itself.
    After some first tests, QuickTime movies behave as expected, the preview renders are working again and the crashes on exit are also gone. Yay!
    Strange how much trouble a driver which is otherwise working perfectly can cause.

  • Make the Library Preview Windows Larger?

    Is there any way to make the Library Preview Window larger? When I'm working at a high screen resolution, the previews are just too small to see.

    You can also turn on zoom in System Preferences/Universal Access, then use *cmd opt =* (that's holding down the command or apple key, the option key, and the = key) to enlarge, cmd opt - to shrink back down.
    Patrick

  • Photo library preview application to save photos

    What is, how do I use "iphoto library preview application to save photos?
    I made an error with my external hard drive while disconnectiong it.
    I cannot access the iphoto library on that drive.
    Can you help?
    Larry

    There is no iPhoto library preview program
    What exactly did you do? What exactly is the problem? What version of iPhoto do you have? Is OS X 10.4.10 the correct version of your OS as you report in your profile?
    Try Back up your iPhoto library, Depress and hold the option (alt) and command keys and launch iPhoto - rebuild your iPhoto database
    LN

  • My Preview is Slow :(

    Since the new update (Im not sure) of Adobe Muse ..... the Muse preview has slowed down ... even the browse (chrome) preview takes a very long time to load. Its definitly not my computer because i have a really powerfull machine. Can some one helpo me ???

    Hey ! Zak !
    Thanks for the reply !
    - Im currently running Adobe Muse 7.3  and the update was from 7.2 to 7.3.
    - Im using a Mac. All my machines are the top of the line models.
    - When i perview my site using Adobe Muse i get something like this  (http://192.168.2.10:33333/Preview/mysite/index.html)
    - Here is the businesscatalyst website.......ive just started working on it......so yea : http://onefoot01.businesscatalyst.com
    Since previewing within Muse was taking too long.... i started to publish my site and preview it as a website from businesscatalyst.com which was really really fast !
    For example...say...If you use the built in "Muse Preview" option the site or page takes a very long time to load fully.... i even tried putting only a blank canvas with a simple colourfill, this itself took a long time.
    Is there a way to fix this issue ????

  • AE CS5 Preview rendering

    When I render previews with the RAM preview button, I often get just a short sequence and then rendering stops automatically.
    Now I thought this is due to RAM shortage.
    Thing is, when I press the normal play button, I first get a realtime playback of the rendered part and then rendering is continued.
    When I try the RAM preview button again, it just renders the same short sequence.
    - Why can't the RAM preview button render more, while the the normal play button can?
    - Why do preview renders often disappear when I try to render some more with the RAM preview button?
    I find myself pressing the preview render button over and over, with very unpredictable outcome of what will happen: rendering extra material or deleting the existing preview and render another part. Is there any way to take control over what RAM preview does?

    Thanks, this helps in understanding a bit what happens.

Maybe you are looking for