Pixelated previews LR4

Any way to correct pixelated previews in LR4 imports of raw images from Canon 5DM2 and 3 (or better yet prevent them)  Had no similar problem with LR3.  Seems others have same difficulty.  Thanks

jonbenner48 wrote:
zoom    ratio 1:8. 
No. Your zoom ratio is 4:1 according to the slider in the lower right corner - which means that each image pixel forms a 4x4 pixel block on screen. In that case, the image should look pixelated.
And please note that this is in the import dialogue where you only see the embedded thumbnail. So it is the low resolution thumbnail you see at 4x pixel magnification.

Similar Messages

  • Understanding pixel preview

    hello people.
    im trying to understand the whole pixel preview thing in illustrator, as I do make websites and I usually use photoshop because i find the slicing faster and easier.
    also things on the web are usually pixels so i feel photoshop is more accurate, and what I see is what ill get.
    so... here are my questions.
    being that illustrator is vector -when i zoom in on a vector in illustrator its crisp and clean.
    im guessing thats because each time I zoom in, illustrator is redrawing my vector at  a higher scale. as opposed to a raster image which when i zoom in, is NOT getting redrawn and looks pixelated because it IS made of pixels.
    is this right?
    when i export something in illustrator to png or jpeg i have to make sure its the right exact size because it will be pixelated otherwise.
    then there is anti-aliasing. if its not exactly aligned to the pixel grid it looks smudged.
    so is pixel preview there to help see what it would look like when it is rastered?

    Eric Greenfield wrote:
     ...being that illustrator is vector -when i zoom in on a vector in illustrator its crisp and clean.
    im guessing thats because each time I zoom in, illustrator is redrawing my vector at  a higher scale...
    Each time you zoom in in a vector art Illustrator is redrawing it (rasterizing it for on screen display) at the size of your monitor's pixels, meaning one pixel of the rasterized vector will fit in one of your monitor's pixels. In Photoshop this is possible only at 100% zoom. When you choose Pixel Preview, Illustrator behaves the same as Photoshop when rasterizing the vector objects for onscreen display.

  • Strange lines in pixel-preview mode

    Hi! I have a problem.
    When I'm drawing something with two windows (one is usual other in pixel preview) I have some strange white lines in pixel preview window. How can I solve it?
    Hope picture will clarify my question.
    Link to full size picture: https://dl.dropbox.com/u/33643074/white-lines.png

    There are no white lines in output icon. These lines are not objects, they are just bugs of Illustrator. When I zoom out and immediately zoom in window with pixel preview - white lines dissapear. But when I change something in usual window (moving any object or rotate) these lines appear again (only in pixel-preview window)!
    My file:
    https://dl.dropbox.com/u/33643074/icon.ai

  • Pixel Preview doesn't match exported PNG

    I use Illustrator CS4 for icon design, so Pixel Preview is a pretty important feature for me. Unfortunately, I just found out (the hard way) that Pixel Preview isn't accurate - it doesn't show you exactly what you'll get when you export a PNG via Save for Web and Devices.
    Here's an example from my current project that shows the problem (enlarged 4x):
    A screen snap from AI with Pixel Preview off:
    A screen snap from AI with Pixel Preview on:
    The exported PNG file:
    Look at the center of the second image: See that dark gray line bleeding from the light gray circle into the black area? Now look at the third image: The line isn't there.
    (Please don't fixate on this one example. Since I noticed the problem, I've found inconsistencies all over the place. This one was just the easiest to see.)
    If I can't count on the absolute, pixel-for-pixel accuracy of Pixel Preview, then this feature becomes worse than useless in my work, because it actually misleads me into making small tweaks that make the final output look worse.
    If anyone knows of a workaround (or a setting that turns on "accurate mode"), I'd love to hear about it.

    I can't state this definitively, but the inconsistency seems to happen with gradient fills. (The light gray semicircle in the example in my original post has a gradient fill with a pretty abrupt transition from light to dark.) Maybe the issue is specific to gradients?

  • Bad pixel preview with bitmaps

    Hi,
    Is there a way to overcome the bad pixel preview me and my colleagues have in Illustrator CS5 when using bitmaps?
    In CS4 we never had such a problem, now there is for bitmaps almost no difference between the overprint preview and the pixel preview.
    In other words - noisy (like in the Photoshop noise filter)!
    That is a real problem because we use bitmaps a lot for fabric prints and T-shirts.
    Please advice

    For the same reason as the guys on this topic are complaining....
    http://forums.adobe.com/message/2786211#2786211
    There is allmost no difference now  between the overprint preview and the pixel preview when we talk about bitmaps...
    Please dont answer the same things as in the linked topic. Let me know if there will be a fix or not. That's all I want to know.
    In meanwhile I'll continue working on cs4 - because a that nice preview is crucial for our work!
    Kind regards,
    Klaas

  • Photos with TS-E 24 II pixelated in LR4

    Today I realized that photos made with my Canon 5DMkII & TS-E 24 II are very pixelated in LR4.2, not only on the screen (also in develop mode), but also in the jpg-outputs. Using DPP does not show this issue, so it looks like a problem with ACR, esp. the new ones - with 2003 it was quite ok, but with 2010 it got bad, and with 2012 even worse.
    Anybody else experienced this?
    LR 4.2 process 2013:
    LR 4.2 process 2003:
    converted using Canon DPP:
    Sharpening is not the point, even with no sharpening at all the pixels are still visible.

    Thanks a lot for your checks and fast response!
    I'm using an Eizo CG243W with hardware calibration - there is no sharpening option that I am aware of, and the tests on the site you linked look perfect. I am very sure that the screen is not the issue. Beside this, I have the same effect on another PC (an you also see it on your screen).
    I had also the UV-filter in mind, for these test shots I used the TS-E 24 II both with and without the filter - no difference at all.
    I am shooting with RAW + jpg, and the jpg files look nearly identical. I'd say there are a tiny bit more halos next to the branches on the TS-E 24 II shots, but really nothing to complain about.
    To me it seems (still) pretty clearly to be an Adobe issue. Here another example, same shots - shown 2:1 to make it just clearer. Looks at this mess, this is really not useable... it looks just like LR stops before the very last step to demosaic the photo completely - not only the branches, check the diagonal lines of the house!
    (btw: the "insert image" button of the upload functionality here does not always work...?)
    And here the same again with the EF 17-40 to compare:
    The comparison you made might be a bit better, but honestly it looks still not acceptable to me.
    Now, can it be the lens? Doubtful, as the in-camera jpgs are fine... of course I could give the lens (with the camera) to Canon for check, but I do not want to waste my money for nothing...

  • Pixelated preview - Help!!!

    I'm using color with a variety of codecs. With every one of them, the preview is pixelated. I'm using a second monitor (23" Apple HD Display) for my preview monitor). I don't notice the pixelation when I render out SD footage, BUT when I render out DVCPRO HD footage it is still there (even converted the footage to Apples Pro Res first to see if that helps-it didn't).
    I would be happy if I could just see the image without pixelation in parked mode (while grading) and be able to render out HD footage without the pixelation.
    I have changed the Proxy settings - that didn't help either.
    Anyone?

    Once you have your footage back into FCP Under your sequence settings make sure to choose upper field on the interlaced settings even if you are viewing progressive footage see if that helps, in my many hours experience using Color the preview is poor (slightly pixelated)as it doesn't handle footage properly (in my personal experience) possibly due to it been sourced from dvcpro hd given it only seems to display one field on a normal monitor regardless of settings in Color or whether or not it was progressive dvcpro hd footage to start with.
    Iverbrain

  • Green/Pixelated Preview Window

    Hello,
    I am on a Windows 7 machine running Premiere Pro CS5. In my projects, I am using footage from a Canon HG20 camera (AVCHD mts format video). When the timeline is not playing, or when playing and it encounters an effect, I get this problem in the preview window (but not in the exported sequence video):
    Does anyone have any suggestions on how to fix this? Is anyone else having this problem?
    Thanks in advance,
    Jordan

    I have the Intel® G35 Express Chipset. I did actually manage to find older drivers on the Intel website, but every latest driver it had was a version 15.x.x.x.x whereas when I click "Update Driver" in the explorer window of the chip, the version says 8.x.x.x.x. I tried downloading the 15.x but I'm still having the problem in Premiere. Could all of this have to do with running Windows 7 on an originally Vista machine? Still though, the drivers on the website for both 7 and Vista say 15.x and such.
    Do you think a reinstall of Premiere would solve it? I haven't tried it yet just because it takes an incredible amount of time.

  • Standard VS 1 to 1 Previews - and 1400, 1600, 2800 pixels for Preview

    Have LR 3.4.1 on XP
    Need conceptual guidance on what to best choose for previews.
    I have 600 raw images in a photoshoot.
    I want to import them and then be able to see them in Library
    Problem is:  When I go to look at an image...it takes 10-12 seconds for it to come into focus for me.  It says loading.
    I tried to do standard previews...then I thought id try 1 to 1 previews...but both are still slow.
    Then I saw in preferences where I can do 1000, 1440, 1680 or 2800 pixel previews?  What do I pick?
    I want to examine my images full size pretty quick without having to wait, wait, and wait for my focus to come in.
    I thought that taking the time up front to render them 1 to 1 would be a big help.
    Now heres the biggie...dont automatically grab this as an easy answer...im using an external  western digital 1TB USB drive to store my images on.
    The catalogue is on MY 10,000rpm fast C: drive (are the previews there?  or can I make them go there with the catalogue?)
    Can someone conceptually help me to understand which way to import and set up preview settings so I get nice fast views of my images without waiting for 12 seconds...or having to put all my shoots on my C: drive.  I want to store all my files on an external drive. its a 20mb sec speed drive.
    Thanks
    Suzzie

    There are various places in the application where previews come up so its necessary to understand the role. You have options for the Standard Size previews as you have discovered. They are used to view the images in the modules based somewhat on the size of your display and how large they would thus appear ‘zoomed out’ (not 1:1, we’ll come to that in a moment). If all you want is standard-sized then choose a size equal to or just slightly less than your screen size. Lightroom will build the smaller versions at the same time. These previews  are used for the thumbnail, 1:2, 1:3 and 1:4 zoom levels. These previews are known as the "preview pyramid" by Adobe due to the group of preview sizes built. I run my 30” display at 2560x1600 so I have my preferences set for 2048.
    Now in Develop, when you want to view at 1:1 (or greater), LR has to build a different, high quality preview, that takes some time. I suspect this is the delay you are referring to. But these previews are different from the previews used above. The previews once built actually populate the ACR cache so you may want to look at the preferences here and decide if you want to store more of these pre-previews if I can make up a term, so that when you revisit Develop, the previews load much faster.
    Of course, you can decide upon import what to do in terms of building the previews. You can pay me now or pay me later. If you want to build the 1:1 on import and walk away, while you edit those images later, everything will be much faster. As you delete images, you are deleting (eventually) preview data you didn’t have to build but then its usually easier to see what images to throw away when you can clearly see them. That’s why I take the speed hit on import, take a coffee break then come back and edit without having to wait too long for the previews to load (its still not instantanious but its much, much faster to build the big previews first).

  • LR4 RC2 is slooooow on importing files

    I have just upgraded to LR 4 RC2 and found that it took two hours!! to import NEF files from my Lexar 400X 8Gb CF UDMA card....I did several trials and it seems that the problem appears when I set some keywords before starting the import procedure. When I put no keywords at all, Import  runs as fast as with the previous version of LR4...is this a bug or it just happens to me?
    Agustin

    add me to the list.
    i have also speed problems with the import in LR4 RC2.
    even when i only import jpg files it´s much slower then past versions.
    with past versions i could immediately view the imported images even when other images were still imported.
    with RC2 i often only see a pixelated preview for 15-20 seconds and the message "reading data" (well i see the german translation of that message    ).
    today i often thought LR froze but then it was "only a hickup".
    problem is the hickup happens very often. 
    i tried to import the same files (from the same SDHC card) with LR v3.6 and it was much faster and smoother experience.
    i also noticed this issue with RC1, but today it was really annoying.
    ps: i don´t add keywords on import but i do add coypright infos into the metadata fields during import.
    my system specs:
    win7 64 bit
    intel i7 2600k
    geforce 460 GTX
    16 GB ram
    240 GB vertex 3 SSD (for LR catalog and previews)

  • Why is the Lightroom preview folder so big, even after purging the 1:1 previews?

    1:1 or full-size previews take up a large amount of HD space, often many 10's of GB's. This is why building them on demand is an alternative to building them up front, and why you have options for auto or manually purging them. That said, it may not always be possible to delete 1:1 previews - more later. 
    Standard-sized previews are based on the pixel size option you chose in Catalog Settings. You have 4 choices: 1024, 1440, 1680 and 2048. If all you want is standard-sized then choose a size equal to or greater than your screen size. Lr also builds smaller versions at the same time. These are used for the thumbnail, 1:2, 1:3 and 1:4 zoom levels. Adobe call this the "preview pyramid". 
    1:1 previews will not be deleted unless your chosen standard-sized preview is less than half the size of the full-sized preview. For example, you have images with pixel dimensions of 3072 by 2048 pixels (6MP camera such as Canon 10D) and have selected 1680 pixels for standard-sized previews. Since a 1680 pixel preview is more than half the size of the original the full-sized preview will be kept, even after using the purge 1:1 preview command. Had you chosen 1440 pixel for standard-sized previews then the full-sized would have been purged (i.e. 3072/2=1536, which is greater than 1440). Now take the example of a larger camera, say a 8MP camera such as the Canon 1DMKII with an image size of 3504 by 2336 pixels. With the standard-sized set at 1680 pixels the full-size will again be purged (i.e. 3504/2=1752 pixels, which is greater than 1680 pixels). 
    Another thing worth mentioning - Lightroom will usually delay purging previews for deleted images until after the application has been closed and reopened, even then it might take a few minutes to clear the purged previews. The idea here is to ensure the previews don't get deleted whilst there's still a chance that they may be needed (e.g. you removed images by mistake then use Undo command to reinstate them). 
    Hopefully above explains why Lightroom doesn't behave as you expect. If it makes your head spin, think how much mine spun when writing it.

    The chance of an answer is inversely proportional to the length of the posting. ;)
    You do not indicate what your preview setting was while you accumulated a 12Gb preview folder. Nor do you indicate how many images are in your catalog.
    Given your screen size of 1280 (laptp?) I would set the preview size to 1440 since this is still far less than half of your D3 images.
    Cropping - I'll safely guess - has no effect on your preview size choices.
    I confess that preview sizing and purging is confusing. I avoid the confusion by shouting "more disk, mama".

  • Illustrator document comes in pixelated, before even placing in a comp

    I'm stumped on this one, folks:
    I created this graphic in illustrator, made up of a pattern of wavy lines. Looks clean and normal in Illustrator, zoomed in at 400%:
    However, when imported into After Effects, pulling it up in the footage panel, it looks pixelated at 100% magnification:
    (Closer view):
    I've tried a number of possible solutions I've seen suggested here and on Creative Cow:
    Made sure that the "document raster effects setting" in illustrator is turned way up (currently at 800 ppi)
    Turned on anti-alias under "document raster effects setting" in illustrator (makes no difference whether this is on or off)
    Made sure that pixel aspect correction isn't enabled in AE
    Played with "interpret footage" settings in AE
    Tried changing save options in illustrator -- create PDF compatible file/Use compression... neither make a difference
    I'm all out of ideas. Is it possible that the illustrator file is TOO COMPLEX for AE to rasterize correctly? It is a very large document, necessary to make it work within my AE comp. (Here it is at 25% zoom in AE for reference):
    Any ideas? Note that this is before I even put it into a comp, so "rasterize continuously" is not the source of the problem. Any help would be appreciated!

    I can tell from your original post that there is a basic misunderstanding of how vectors are rasterized and interpreted in any video application including Motion, Final Cut, Premiere Pro, Avid... and After Effects.
    "I've tried a number of possible solutions I've seen suggested here and on Creative Cow:
    Made sure that the "document raster effects setting" in illustrator is turned way up (currently at 800 ppi)
    Turned on anti-alias under "document raster effects setting" in illustrator (makes no difference whether this is on or off)
    Made sure that pixel aspect correction isn't enabled in AE
    Played with "interpret footage" settings in AE
    Tried changing save options in illustrator -- create PDF compatible file/Use compression... neither make a difference
    I'm all out of ideas. Is it possible that the illustrator file is TOO COMPLEX for AE to handle correctly? "
    Let's start with point 1... Document Raster settings in Illustrator set to 800PPI...
         Well, there are no inches in video so the PPI will only effect raster effects and raster effects will not continuously rasterize because they are interpreted as pixels. For video work 72 is plenty, 800 will not gain you anything unless you have completely setup your Illustrator project incorrectly for video.
    Document Raster effects settings in Illustrator make no difference as I do not see any raster effects in your sample. Raster effects are things like Drop Shadow. It looks like you just have a bunch of wavy lines. If you have a rastor effect applied you do not have a vector image any more.
    Too complex is also a misunderstanding of how AE handles vector images. Your paths, though numerous, are simple... no chance the number of paths is causing the problem. So what is?
    The lines are too thin... Simple as that. You must be concerned with the stroke width in your illustrator files. It looks like the stroke is set to 1 point. That means 1 pixel. One pixel lines MUST be exactly lined up with the pixel grid to rasterize properly. There's no way around that limitation. NONE. Change your document settings in Illustrator to pixels instead of points and you'll see what I mean. Your lines don't look ailiased or blocky to me, they look like 1 piel width lines not following the pixel grid perfectly. The behavior is completely normal.
    Here's how you should set up an Illustrator file for video work.
    In illustrator, document setup should be in pixels not points, or inches or anything else.
    Artboard size should be set to be big enough to include every element you wish to include in an AE comp. IOW, if you want to push in in AE to 1/4 of your illustration then the artboard should be 4X the size of the comp.
    Strokes must be at least 2 pixels wide. This will guarantee that when your illustration is viewed at 100% scale AE will have a chance of antialiasing any curved lines. 1 pixel wide curved or diagonal lines cannot be rastorized into a smooth line.
    If you plan to scale down your image then you must compensate in your design so that the lines will scale down without problems. This thicker strokes. Scale to 50% and your stroke needs to be 4 pixels or 4 points to work well.
    You should have snap to pixels on, do pixel previews in Illustrator, and accurately position your vector lines precisely in Illustrator to minimize problems.
    Inside AE you should select your AI layers in the project panel and then go to Interpret Footage, More Options, and set antaliasing to more accurate.
    I hope this helps you.
    The wavy line pattern is going to cause all kinds of moray and interference problems when you move it across the screen because of the changes in aliasing as the lines move across the pixel grid and are interpreted as pixels. This is also a guaranteed problem with the design. It can be mitigated by fattening up the stroke and by using an expression to make sure all movement is exactly on an even pixel.
    You still have to worry about retinal retention, stroboscopic effects due to frame rate and pixel motion, and moray patterns caused by the human eye and brain combination. Read this article from this forum's FAQ for more information on that. Our brains don't like to look at moving repetitive patterns. Try slowly moving your eyes across the red checkered table cloth the next time you eat in an Italian restaurant and you'll see what I mean.

  • My vector drawings in illustrator cs3 look pixelated plz see screenshot

    **** Notice the side of the girls hair its very serrated and somewhat blurry as well look down at her arm at the very bottom
    I am using a mac os x version 10.5.8 and have been using Illustrator cs3 that I purchased for about 2 years and its never had this problem till now. I've just recently noticed a few days back that my vector drawings created in illustrator are looking serrated on the edges of my drawing, and this jagged serrated line goes all along the sides of the vector image and doesn't seem to go away when I zoom in or out......
    And from what I know vector drawings created in illustrator can be resized and never pixelate but i don't know why its doing this.
    I've searched online for all the possible remedies but nothing seems to get rid of that serrated line which makes my images look fuzzy on the sides.
    I've made sure that I'm in preview and not pixel preview but that didn't work.
    I went to my illustrator preferences to make sure that anti-aliasing is checked but that didn't seem to fix it either.
    I went under the effects menu and clicked on Document Raster Effect Settings and changed that to 300ppi but that didn't do it either.
    And also when I take my vector drawing from illustrator into photoshop, the serrated lines become more evident. I don't know what to do. The strange thing is that when i print the images out from my printer, the serrated edges don't show up.
    But here's the thing: when I open up my past work that I created in illustrator when I wasn't having this problem, for some reason they are also now showing up with that serrated line on the edges, its really weird!!!!!
    I've tried everything except for reinstalling the software, but just wanted to know if someone could help me before I tried this step or knew of something that might have gone wrong.
    I also downloaded illustrator trial version cs5 today, and its doing the same thing as my illustrator cs3!!!!
    Plz help!!!

    I was experiencing the exact same thing in Illustrator CS5. There was a pixelated edge on a vector drawing that was showing up. At first I assumed it was an anti aliasing setting or pixel preview or document raster settings as you did. Then because all else failed I was about to assume it was a screen artifact or bug of some kind.
    However, the upon further analysis I found the solution-and it was right under my nose. I had applied an effect to the vector object (an outer glow) and–because I was going to scale it down drastically from the size I had originally drawn it at –I had gone to the object menu and expanded the appearance of the object which caused my outer glow effect to become a rasterized shape underneath my original object.
    To remedy this: I simply zoomed in on the pixlelated object, selected it, ungrouped it, selected the top vector object path, nudged it to the right–REVEALING THE RASTERIZED SHAPE BENEATH!
    So I would reccomend you try two things:
    First select the view menu and choose "Outline" (command or control Y), then look to see if you have any solid "blocks" -this could indicate a rasterizing of some sort has taken place underneath your vector objects. To get back to regular display just choose "overprint from the view menu.
    Secondly, you could select the vector object that appears pixelated and then check in the "Appearance Panel" to see if an effect (such as a drop shadow or outer glow) has been applied ,possibly inadvertently. Because just the applying of an effect will cause a "pixelated, jaggy edge" when viewed at high zoom percentages, or indeed any resolution for that matter.
    Hope this helps-

  • Illustrator CS4 - when I save for web my vectors are pixelated. Help!

    I recently updated to CS4 (I know, I'm still behind the times) but ever since when I 'save for web' my vectors appear pixelated. It seems worse when I want a transparent background. My images are for web and this just won't do. 
    I've read a lot on this and can't seem to fix my problem, but here is what I have tried: Anti-Alias is checked, view > pixel preview, view > overprint preview, object > rasterize, and probably a few other things. If anyone can help me with this issue it would be GREATLY appreciated!! I've attached an image so you can see what I'm talking about. I created this schematic in Illustrator CS4 and saved for web with a transparent background and, as you can see, it appears pixelated everywhere.

    I'm not sure what you're looking for but here is my save for web options. Let me know if you're looking for something else. And thank you for trying to help!!

  • Previews questions from link - "preview folder so big, even after purging the 1:1"

    Can someone clear this up a bit?
    My LR 2.1 preview folder is at 12gb, and I want to get that under control. After reading all of the threads here about previews it seems one of the best choices is just delete the folder and then let LR 2.1 rebuild it. But before I do that I want to set my preview options correctly. The info below (found in another thread) is good, but confusing at the same time.
    1) "You have 4 choices: 1024, 1440, 1680 and 2048. If all you want is standard-sized then choose a size equal to or slightly less than your screen size" Is this based on the long edge of your screen size? long edge meaning 1280.
    2) "Now take the example of a larger camera, say a 8MP camera such as the Canon 1DMKII with an image size of 3504 by 2336 pixels. With the standard-sized set at 1680 pixels the full-size will again be purged (i.e. 3504/2=1752 pixels, which is greater than 1680 pixels)". This formula looks to be saying the long edge, correct?
    Am I understanding this correctly? This looks to be saying;
    A) standard previews uses your screen size.
    B) 1:1 previews uses images pixel sizes?
    C) you only have one setting to control previews for standard and 1:1? (that being the "You have 4 choices: 1024, 1440, 1680 and 2048")
    This is interesting because in my case my screen size in 1280, but most all my Nikon D3 images are 42xx. So if I want to keep my previews folder clean and growth controlled, I should basically set my previews option to the lowest 1024? And one more interesting tid bit, how does a cropped image play into the 4 choices? Say I crop a 42xx image to oh say 2024, then my 1:1 for that image will never be purged? I'm probably missing something here, and it wouldnt be the first time.
    Why is the Lightroom preview folder so big, even after purging the 1:1 previews?
    Ian Lyons - 05:18am Aug 18, 2008 Pacific
    1:1 or full-size previews take up a large amount of HD space, often many 10's of GB's. This is why building them on demand is an alternative to building them up front, and why you have options for auto or manually purging them. That said, it may not always be possible to delete 1:1 previews - more later.
    Standard-sized previews are based on the pixel size option you chose in Catalog Settings. You have 4 choices: 1024, 1440, 1680 and 2048. If all you want is standard-sized then choose a size equal to or slightly less than your screen size. Lr also builds smaller versions at the same time. These are used for the thumbnail, 1:2, 1:3 and 1:4 zoom levels. Adobe call this the "preview pyramid".
    1:1 previews will not be deleted unless your chosen standard-sized preview is less than half the size of the full-sized preview. For example, you have images with pixel dimensions of 3072 by 2048 pixels (6MP camera such as Canon 10D) and have selected 1680 pixels for standard-sized previews. Since a 1680 pixel preview is more than half the size of the original the full-sized preview will be kept, even after using the purge 1:1 preview command. Had you chosen 1440 pixel for standard-sized previews then the full-sized would have been purged (i.e. 3072/2=1536, which is greater than 1440). Now take the example of a larger camera, say a 8MP camera such as the Canon 1DMKII with an image size of 3504 by 2336 pixels. With the standard-sized set at 1680 pixels the full-size will again be purged (i.e. 3504/2=1752 pixels, which is greater than 1680 pixels).
    thanks,
    Donnie

    The chance of an answer is inversely proportional to the length of the posting. ;)
    You do not indicate what your preview setting was while you accumulated a 12Gb preview folder. Nor do you indicate how many images are in your catalog.
    Given your screen size of 1280 (laptp?) I would set the preview size to 1440 since this is still far less than half of your D3 images.
    Cropping - I'll safely guess - has no effect on your preview size choices.
    I confess that preview sizing and purging is confusing. I avoid the confusion by shouting "more disk, mama".

Maybe you are looking for