Weird Standard Preview Problem

I had posted elsewhere about a problem with the "standard previews". Basically they can be there at one point and "POOF" they are gone the next time I open a particular folder. (My settings were 1440 and Medium.) Even within a folder there can be some that show the preview fine and some show previews that look like a very small JPEG file (and badly compressed to boot).
It was suggested that generally closing LR and restarting it generally solves this problem - nope did not help.
Any suggestions - aside from deleting the files and importing them all over again?
Thanks,
Steve

Hi Hal,
Yes, I have tried Library//Render Standard Previews. It occassionally seems to be doing something. Even tried putting the particular DVD back in the drive, selected all the photos in that particular directory and then selected "render standard previews". Nada - nothing changed.
Even tried changing my preview settings (from 1440/Medium to 1600/High) and no difference.
Thanks
Steve
BTW - If there is some "rendering going on in the background", then Adobe should have explained that we need to leave the DVD/CDR/Source Disk in longer after the program indicated (by the progress bars at the top) that the importing/rendering is completed.

Similar Messages

  • Imported images w/standard previews problem

    I am just starting with LR and very impressed with the program.
    Most of my image files are stored on DVDs and CDRs, so I liked the idea of having the previews in LR so I could look for an image and then find the appropriate disk.
    My problem is I will insert a DVD, click on Import and check "render standard previews" and walk away. When I return, the job is completed and I take the DVD out of the drive. When I come back to LR many of the images (both the thumbnails and the rendered previews) are not there. All I see is a grey box.
    What am I doing wrong since I assume this is not the way the program is supposed to work?
    Thanks,
    Steve

    Geoff: Settings are 1440 and Medium Quality. It seems to occur more often if I do the rendering AFTER importing, instead of at the time of importing the pictures.
    Svlists: Yeah, generally that does solve the "grey box" problem, but not all the time or for all the missing images.

  • Weird video preview problem... frustrating!

    Hi, I wonder if anyone else has had this problem... ?
    I had a project that was working fine, but now I cannot watch a video preview by pressing enter or space. The timeline renders the preview then does nothing, just sits there. The play button in the program monitor changes to the stop symbol, just like it does when the video preview plays normally, but no video or audio is playing...
    Please help!
    TR

    Captured PAL HDV footage (1080i50)
    Premiere Pro v3.0
    Mac Pro Quad Core 3gb memory
    Mac OS X 10.4.11
    What else do you need to know?

  • LR5 import problem with rendering standard previews

    When I import from an SD card in LR5, the first phase of the import works fine, then the second phase is to "render standard previews" and the import process stalls at photo #3. If I double click on one of the photos, and then go back to the grid view, the importing continues fine. What is happening and how can this be overcome. Thanks,
    [email protected]

    I leave it until the bar at the top left of the screen which says 'rendering previews' has finished and disappeared, and I've also taken to using Task Manager to watch and wait until the cpu activity has reduced to zero. As you say, this can take some time.
    If I then scroll through the grid of imported images, I find some that still have three dots, and which slowly disappear one by one as they are rendered. That is very tedious, so I go back to select all, wait for the metadata to be collected as shown by the bar, select 'render standard previews' - a new bar appears saying 'scanning existing previews', and when that has finished it puts up the rendering previews and starts rendering the ones that still had three dots on them. It then eventually finishes and the bar closes, but with the last lot, I had to repeat this three times before it scanned existing previews and then stopped instead of starting the 'rendering previews' bar again. Each time it added some more previews, until they had eventually been done, and there were no images in the grid view with three dots (other than the brief flash of dots as I scroll normally).
    I've also got in the habit of clicking on 'all photographs' after opening LightRoom and waiting until Task Manager shows it has finished it's 'housekeeping', before starting any work. This seems to minimise 'Out of Memory' dialogs or 'Not Responding' situations.

  • Why doesn't LR let us use embedded/standard previews (at least optionally)?

    I bought LR but cannot commit to using it mainly because it is too slow importing and browsing previews but also because LR's previews are worse than the embedded previews in RAW images or JPGs as displayed by other standard programs like Photo Mechanic, Breeze Browser or ADCSee.
    I shoot Canon RAW (then convert the CR2s to DNG) and occasionally JPG (1DMkII) but I get hundreds of images from friends and family, mostly JPG, taken with many different cameras. The vast majority of these pictures look terrific in PM, BB or ACDSee, etc but they look significantly worse in LR. LR renders its own previews from RAW files instead of using the excellent embedded preview that's already there and LR also somehow changes the JPG preview so that it looks bland and off color in comparison to the same image viewed in PM, ACDC or BB on the same computer. I assume LR's color management or color space is what changes the previews (and thumbs) so they look different (bad) in LR than they look in other standard programs.
    Why can't we at least have the option of using embedded previews in LR and display them normally like PM, BB and ACDC. Then LR would be fast (like PM, BB and ACDC) importing and displaying previews and we would not have to fiddle with exposure or color adjustments to get decent previews. Yes, I can get LR to just about match (sometimes exceed) the image quality of other programs but only with massive fiddling with individual images (the camera calibration controls are not sufficient by themselves) and that is a massive pain in the butt.
    I, of course, have read many posts about color management. But I refuse to buy expensive color calibration tools and go through that expense and aggravation just to accommodate LR. My pictures already look great in PM, BB, ACDSee and web browsers and on other non-color managed computers. I think LR should be able to be operated in a standard manner so it is consistent with other standard software. The fact is that the vast majority of all amateur photographers, even pretty serious folks, do not hassle with color management because standard software displays very nice images already.
    Another point. Some folks like to use Canon or Nikon or other RAW converters instead of Adobe's (for all or some images). If they develop their RAWS in DPP or Capture NX, etc, then import the images into LR, LR renders its own previews which disregard the work done in the 3rd party converter. This is pretty annoying and virtually prevents such folks from using LR. Other programs that use the embedded previews display the adjustments made in 3rd party RAW converters very nicely.
    Regards
    Bill Wood

    Thanks for the replies. Sorry I could not respond sooner.
    Nobody addressed my question. Why is there no option in LR to use embedded previews in RAW files and why is there no option to display JPG previews in a standard color space, presumably sRGB, like other standard software - Photo Mechanic, Breeze Browser, ACDSee, etc, etc?
    LR's insistence on rendering previews from RAW files makes the program too slow and it forces users to diddle with settings to get previews that look normal - meaning match what 99% of the rest of the world sees on normal non-color managed computer screens. Folks who want rendered previews and non-standard color space (ProPhoto) and all the rest of us who just want standard previews by default should both be accommodated. Just give us the option to choose.
    I just downloaded IDImager, a competing database type DAM program, for a trial. It does give users the option to use embedded previews for fast import and display or it will render previews from RAW if you choose that option. So it can be done and an embedded preview choice makes the program much faster and easier for most people to use.
    Just a few comments about the replies:
    Lee Jay said LR doesn't use embedded previews because:
    "Correct...that's because it's a RAW converter and must display what you'd get from a RAW conversion."
    Well, with respect, I cannot agree. First, LR is not just a RAW converter, its much more. If it was that limited, I never would have bought it and neither would anybody else. I already have ACR in Photoshop. Second, it is not mandatory that LR render previews from RAWs. It could optionally use embedded previews if that option was offered. Why do some folks lobby for lack of flexibility? I bet even you naysayers would use embedded previews sometimes, like when you want speed to show pictures to your family, friends and don't need to fester over image adjustments.
    Lee Jay also said regarding the difference between my JPG previews in LR vs. other standard software:
    "That is likely the fault of your monitor profile, which LR uses and the other programs (probably) don't. It could also be caused by you having "automatically apply auto tone" set, or by applying a preset on import."
    No, it LR's fault, period. Every other program I have ever used displays my pictures just fine (Photo Mechanic, Breeze Browser, ADCSee, etc, etc, even Windows free Picture and Fax Viewer works fine. Yes, I can diddle with LR's settings and get nice previews but I don't want to diddle with every image. And it ain't my monitor profile - I can delete it or change it and the issue remains. LR makes different previews from standard software because it renders previews from RAW data and uses a non-standard color space. Camera calibration (or presets) is not a reasonable solution for everybody. I have several cameras, my kids have many different cameras, friends have different cameras and I get images from all these people - so I have a ton of very different images in different lighting and I am not about to setup numerous different calibrations or presets to see previews in LR when I get excellent previews from other standard software that uses embedded previews and produces great previews with no work whatsoever. All I am suggesting is the option to use embedded previews and a standard color space. Again I must ask why do some folks argue for lack of flexibility?
    John McWilliams said about LR's power:
    "The neat thing is you can make the image look just about anyway you want without loss of quality."
    I could not agree more - LR is a good program! But, I don't want to diddle with every image. Most of them are fine, in fact, terrific right out of the camera. I just want to see them faster and I want them to match what other people see on standard non-color managed computers. If PM, BB, ACDSee and others can do it, so can LR.
    David Edwards said:
    "The images that I want to see in the Library section are RAW images with all the adjustments I have made to them and certainly not the embedded JPGs. If I wanted to see those I would have shot JPG."
    This is fine and no doubt makes perfect sense for David's workflow. But, why advocate against an option to use embedded previews for those who would find that useful? I too shoot only RAW with my DSLR cameras because I want the best images and the ability to use all of LR's (or DPPs) conversion powers when appropriate. But, as I said above, the vast majority of my embedded previews are good enough right out of the camera as viewed in PM, BB or ACDSee so I don't need to make any adjustments. :) Only LR creates a problem my rendering less than desirable previews by default. I also want to note that embedded previews do, in fact, display all changes made in LR and I cannot tell any difference in quality on screen between embedded previews and rendered previews when I adjust the LR version to match the default embedded preview and compare them side-by-side in LR and PM, for example.
    David also asked:
    "Do you need a RAW converter or an application to display images?"
    Both. Preferably in the same program. LR is supposed to be an all-in-one solution. It certainly will be when it gets more mature, I hope. I am a amateur so my main need is to see my pictures. I like them and enjoy them but LR is too slow importing and displaying thumbs and previews in Library mode and its previews usually need adjustment. So right now I am forced to use PM, BB or ACDSee all of which are way faster importing and browsing images and they use embedded previews that are fine, even excellent, by default.
    I think Adobe is missing out on a significant number of potential users because LR does not provide the options I am requesting. I am certainly not the only person who wants faster importing and browsing and previews that look good by default. And, as I mentioned before, folks who use other RAW converters are also excluded since they cannot see the changes they make before importing images into LR because LR will not display embedded previews.
    Regards
    Bill Wood

  • Can you generate 40,000 standard previews?

    Is there anyone using LR 2 on Windows with a catalog greater than 40,000
    images who can delete all previews and then generate all 40,000 standard
    previews in a single step without encountering a performance problem?
    Best,
    Christopher

    I've rendered 70,000 images several times in LR, but have never succeeded in one run. It usually takes two or three runs to complete all of them. On my V64, it doesn't hang, it just goes into 'warp' mode and pretends to render them (according to the progress bar)in a fraction of the normal time. Re-running it shows tens of thousands still left unrendered. But after two or three runs, it gets there. Adobe knows of the problem on my V64 system, but filling in their bug report with details of your system might help them.
    Bob Frost.

  • CS4 Premiere Pro General file format & preview problems

    I was redirected here after posting my complaint on Twitter, so please excuse my forum manner.
    I've been using Adobe Premiere Pro (CS4) for about a year now, and I've been editing videos along with other packages with no problem. (Only problem being my slow processor). Up until last week Premiere Pro has been completely fine. But seeing I have a project deadline next month, I thought I would spend a day trying to kick-start the video editing.
    My source videos were originally photograph-frames animated in Flash CS4 into .MOV, decided to use the H.264 output codec. As I have finished exporting my needed videos, I imported them into Premiere Pro as usual, as I have in the past. But then I encountered the common problem that I have seen quite a few have also encountered with .MOV, or jsut general "no-preview" problem when the source video is fine.
    I then took a day to research online about Premiere Pro's compatability with .MOV, among other container and formats. Upon using softwares such as MediaInfo and GSpot, I found that there might have been a problem with missing Codecs within my Adobe package. I then tried to convert the .MOV into .MPG (mpeg2), hoping such standard codec would work with Premiere Pro as they they in the past. No result avail.
    I then turned to the uninstall route (retaining user info) and re-installing. The problem has NOT been fixed, what's more is that it crashes almost instantly after I try rendering the workplace. (Even post-rendering does not show the preview, but the files in the Adobe folder, does). Here's a screencap to my latest workplace, if it helps:
    [IMG]http://i86.photobucket.com/albums/k83/neo0031/AdobePreProcap.jpg[/IMG]
    Before the re-install, I believe I was running Premiere Pro CS4's latest update (4.2.x) something, now it is back to 4.0.0. But I don't think that is where the main problem is? I recently changed my locale from a certain language to Japanese to run a certain program. Would that be causing the problem(s)?
    Does anyone know a way that I can FIX this? Any help is appreciated and I thank you all in advance.
    I am using a Sony Vaio NS series laptop,
    a 2.0 GHz Intel Pentium Dual Core processor
    3GB RAM,
    intergrated graphics Intel Chipset Family Series 4( I think).
    Windows Vista Home Premium 32bit.
    I tried moving the Scratch disks from an external portable hard drive to the local hard drive, to no result.
    Again, any help is appreciated. I would appreciate direct advice rather than links. Thanks again.
    Neo.

    I have updated my CS4, Ppro to 4.2.1. The problem still remains. Would it have anything to do with my project setting? I don't have much knowledge to setting one up. The difference between the AVC projects and etc?
    EDIT : I took the problem to my lecturer, and he didn't do anything out of the ordinary, but his "magic touch" click on the preview panel (Main composition) has made the video show up! But even after render, it won't play. But scrubbing along frames is now fixed. Any idea what's causing the no-preview-playback?

  • Importing both smart previews and standard previews crashes

    I understood that Lightroom does not use smart previews as previews in most cases and still uses previews as before for working on. I normally import as standard previews because this improves speed whilst working on them. I have just ticked the smart preview box for a couple of files that I thought I might want to work on after transferring them to my externsl drive and it crashed when set with standard, OK with minimal, I am now wondering if in fact the smart previews are the previews it works on and that by setting it to standard as well it has confused the program and that is why it crashed, but then why have the option of both or is it simply a computer resources issue trying to create both standard and smart previews.

    Julian_M_R wrote:
    I am now wondering if in fact the smart previews are the previews it works on and that by setting it to standard as well it has confused the program and that is why it crashed...
    Regular previews are primarily for library module (e.g. you need them for loupe view).
    Smart previews are only for develop module and exporting (they provide image data in lieu of original (e.g. raw) file).
    There is no "conflict of interest".
    That said, I have no idea why it crashed unless maybe you ran out of disk space or something (?)
    If (because of some problem you are having) you want both but you have to pick one, pick smart previews. Regular previews can be created from smart previews, but not vice versa (yes: it will take time).
    Rob

  • Preview Problem: PDF file:Adobe livecycle designer ES 10.0

    Hallo.
    How do I fix  preview problem of a .pdf file that was created with Adobe livecycle designer es 10.0.  version 1.7 ( show on the properties of the file). The file opens normally. No preview in explorer preview pane and change to printing problem too. Need to preview the file before uploading it onto the internet. All updates done: Windows 7, Explorer 11, Java (Javascript enable) Adobe reader XI. and Adobe Reader XI Pro.(Trail version). When in Explorer and using open with:Default program: select software already in stalled on computer: Browse Adobe reader XI (Acrord32.exe: properties show version 11.0.06.70) This will show as Adobe reader 9.4 on the list of programs.

    If you purchased a prior license of Acrobat and have purchased an upgrade to Acrobat XI Pro then you are eligible for free LiveCycle Designer upgrade.
    See more information on: http://www.adobe.com/products/acrobatpro/faq.edu.html
    Visit the http://www.adobe.com/go/learn_acr_livecycle_upgrade_en to request an upgrade.

  • Standard Preview size/quality Lightroom 1.1. (how and what)

    I'm working on a Macbook pro, with hi-res 17" screen 1920x1200. In most manuals, tutorials etc. it says that you can "set the standard preview size fitting for your screen".
    I'm looking for some more background info on the standard preview, to decide which setting to use(if somebody has other criteria to keep in mind please do say so):
    1) What is the difference in size of files for the different combination of options (pixel/quality). Does somebody have a list.
    2) What is the actual difference in the quality options
    3) In which modules is the preview size used (also in development and slide show?)
    4) Are they also used to generate the thumbnails from? If so, does a higher standard preview size reduce the performance in library mode because it as to shrink bigger files for these thumbnails?
    5) what happens if I would use the smaller, let's say 1440 preview and then decide to view the picture full-size, in library or slide show
    6) What would be the size (in pixels) on the normal main window in lightroom on my 1920x1200 screen. if it is about 1440 (might take that one)
    Last question of course: What standard preview size / quality should I use on my 1920x1200 screen??
    Thanks in advance for all your thoughts!

    As to standard preview size and quality, try 1440 and 1680 and Med and High quality and see what you like best. You will probably choose 1680 size for your screen running at 1920x1200. That will let you run LR full screen where the image size will be close to the full size of your monitor. You can try 1440 too but I doubt that you will see any performance improvement. I have tried both sizes on my 1600x1200 monitor and I see no difference in quality or speed.
    Try both Med and High quality and see if you notice any difference in your preview quality or speed. High will make your preview folders bigger which might be a factor if you have limited hard drive space.
    Don't think preview size has anything to do with thumbs. Standard previews are separate from 1:1 previews so you can always zoom in and LR will generate a full size preview.
    In short feel free to experiment with various settings in LR. Good way to learn the program and you will know what works best on your particular computer.

  • Does anyone know why I get varying file sizes when I save a jpg (with same settings-None, 12, base "standard", preview checked) from PhotoshopCS5?

    I opened a .psd file (300 ppi, CMYK, .jpgs (1626px x 2130px), I saved it as a jpg (None, 12, base "standard", preview checked).
    I then closed the original .psd file.
    I repeated those steps on the same file and saved a series of 6 .jpgs.
    Of those 6 files, I received 2 large files (6.2MB) and 4 smaller (3.2MB) files.
    My coworkers who were having trouble opening some of my jpg images in Windows Photo Gallery on Vista OS were able to open the smaller files but not the larger ones.
    Do you have any idea why the same settings would give me different file sizes from CS5?
    Is there a way I can make it consistently keep the smaller more compatible version?

    How well a image data compresses depends on image content.   Image with High detail do not compress well image will little detail will compress well and the file size will be small. Compare a image of a blank white wall to a wall with a black and white checker board wall paper.  One is all white it white no other detail  to detail the other has squares that vary in size because of perspective angle and distance a lot of detail must be recorded.
    I do not know why they can not open some of your images. File size should not be an issue.   All your image decoded are the same size  Width number of Pixels Height numbers of pixels background layer only for these are jpeg files.

  • Standard Preview Size/Preview Quality

    This may be a silly question, but in Library mode, under Edit>Catalogue Settings>File Handling, you have options under Preview Cache for 'Standard Preview Size' (1024/1440/1680/2048/2880 pixels) and Preview Quality (High/Medium/Low)... but what do these settings actually do; I've tried changing them & not noticed and difference??

    Les_Cornwell wrote:
    Thanks again Rob
    You bet .
    Les_Cornwell wrote:
    I've tried all the different size options, namely 1024 through to 2880 & low/Medium/high and none make any obvious difference at all.
    So are previews only created as required when you view a picture in full screen mode or does LR create a preview for all your files?
    Every image you look at in Library module comes from the (library) previews, there are up to 8 possible jpegs:
    * a tiny thumbnail in root-pixels.db
    * up to 7 jpegs ranging from small to 1:1 in the "preview pyramid" (each smaller is half the dimensions of it's bigger sibling).
    Try this with a 10 photo test catalog:
    If you have a big monitor and set standard preview size to 1024, then (with Lr closed) delete all previews, then restart Lr and wait for all the "..." indicators to be extinguished (indicating standard previews have been built), then step from photo to photo in loupe view with all panels collapsed (loupe view "real-estate" maximized), you should see "loading" indicator, since it needs a bigger preview than you've got built. What it will do then is build 1:1 previews and all the smaller ones along with it, which is suboptimal from a performance point of view. If you try and zoom in to 1:1 after the "loading", there will be no additional loading, since 1:1 previews were already built.
    Then, repeat the test with preview size at max - no loading indicators, right? (when stepping in loupe view after standard previews have finished being built, I mean). Except now if you try to zoom in there will be "loading", since 1:1 preview were not required to display the loupe view, they will need to be built for the zoomed (1:1) view.
    The only difference between big enough and too big will be an ever-so-slightly greater lag when stepping in the loupe view and no 1:1 preview exists (when preview is too big I mean), since it's loading a bigger standard preview than is actually needed. Reminder: if preview is not big enough, there will be an ever-so-slightly bigger lag when stepping in loupe view too (e.g. vs. just big enough), since it's using the 1:1 preview instead of standard (which wasn't big enough). So, tester beware... (somewhat counter-intuitively, in some cases, it will be faster loading a preview when settings are, in general, too big, because it can get away with loading the next size down, which is an even better fit, e.g. if image is cropped just so - all of these little nuances make it especially tricky to test & evaluate, so consider doing initial tests using uniform-size uncropped images, to reduce the number of variables - it's confusing enough as it is ;-}).
    Note: as previously mentioned, there is considerable complexity (and bugs) in the preview system, and I may not have described it perfectly, so it wouldn't surprise me if your results were not exactly like that, but I just went and retested on my system, and what happened is exactly as I described above (win7/64), as I read it anyway...
    Regarding quality, you should see difference in some photos not others, but ONLY if it didn't resort to the 1:1 preview which may be higher quality than the standard and is independent of the standard quality setting. (I think somebody may have stated that you'd need to zoom in to see differences in standard preview quality settings, but that is wrong - the only way to see differences in standard preview quality settings is if you are in fact viewing standard previews, which you aren't when zoomed in to 1:1, and anyway it can be ellusive - see paragraphs above...).
    PS - If you want to compare jpeg quality of standard previews, one way is to export them using PreviewExporter. Again, it's tricky, since you need to assure you aren't exporting a scaled down version of the 1:1 instead of a true standard preview. After exporting you can compare outside Lightroom, so you don't have the "preview of a preview" issue going... I use Beyond Compare by Scooter Software for doing objective comparison of like-sized jpegs, but you can compare subjectively using any ol' viewer, e.g. as built into OS.
    Too much?
    UPDATE:
    Les_Cornwell wrote:
    does LR create a preview for all your files?
    No - they are created on an as-needed basis (thus the reason we hear many complaints about how stale or non-existent previews should be built in the background, to minimize "loading" in library module, e.g. after making dev changes to a large bunch), but note: standard previews may be considered "needed" when thumbnail is in view in grid or filmstrip (but not considered needed if thumbnail is off-screen, even if existing in filmstrip and/or grid).
    R
    Message was UPDATED by: Rob Cole

  • Standard Preview versus 1:1 preview

    I've always been curious about the differences between these two previews.
    Given the fact that Import can optionally generate a standard preview, why would I want a 1:1 preview? And if 1:1 is preferable should a standard preview not be performed during import opting instead to generate the 1:1 preview later?

    I've found that the import process works better if you have it render standard previews during import. It will only render 1:1 previews if you need them. For example, if you zoom in on an image to 1:1, it will generate the needed image for you to see and save it as a 1:1 preview. It will not just do this in the background for all images unless you've told it to render all images at 1:1.
    Lee Jay

  • RAM Preview Problems in After Effects CC

    AE CS 6 RAM Previews work, but two problems to report with AE CC on the same computer. Possibly two faces of the same problem.
    1. Having QuickTime Player open while doing a RAM preview makes the RAM preview stutter. I quit the player, and now the RAM preview plays back without dropping a frame, though Info palate shows "fps: 24 (realtime)", but the RAM preview playback is slow: ie, a tenor sounds like a baritone.
    2. A RAM preview that looked and sounded fine last night, is now playing back slowly (tenor sounds like a baritone), though Info Palate shows "fps: 24 (realtime)". I have no other applications open. The only thing that changed is that I quit AE, slept the computer, slept a little myself, and then launched AE. Trashing the cache files (manually), rebooting, relaunching and re-RAM-previewing creates a functional RAM preview, so I assume there is some problem with the cached files or the retrieval of them.
    Is anyone else getting either of these? If so, what is your system configuration?
    Also, I posted on another thread that Quicktime import/render works with AE CS6 on this computer, but AE CC can not import, play, or render QT reliably (without throwing error messages). Perhaps all of this is part of the same problem.
    Thoughts?
    Cheers,
    Benjamin
    CS 6 CC | Mac OS 10.8.4 | MacPro5,1 | 96 GB Ram | PROJECT & MEDIA drive: Mercury Accelsior > 500 MB/s read/write | CACHE drive: Mercury Accelsior > 500 MB/s read/write | Nvidia Quadro 4000 Mac | CUDA Driver: latest update | Wacom Intuos 5

    96 GB RAM is  accessible in 10.8.4 on my machine according to OWC. I'm working on a stereoscopic 4K project with large files and hundreds of layers. I regurlarly render with AE MP while working with huge files in PS, and am glad to see the % of RAM AE uses displayed in my render cue between 3 and 60%.
    I have 12 processors (24 with hyperthreading)
    I have reserved 10 for other applications leaving 14 for After Effects
    4 GB per x 14 = 56 GB for AE. leaving 40 GB for everything else
    I've played with what and how much I have allocated being sure to keep the CPU counts even, but this does not fix the RAM preview problems described above. Any other suggestions?
    Thanks,
    Benjamin

  • Stuck on "Rendering Standard Previews"

    After importing images, Lightroom (2.4) is getting stuck in the "Rendering Standard Previews" process.  I have been sitting here for over an hour while Lightroom is stuck at 6 of 117.  This happened on an earlier import as well, and I ended up canceling that process -- it was stuck on 1 of 6.
    Has anyone else seen this, and is there a fix?
    Thanks,
    Nick

    Actually, I seem to also be stuck on "Preparing File for Editing" as I try to process a photo in Photoshop.  Somehow the "process" process is getting stuck.
    Nick

Maybe you are looking for