Cropping in LR3?

Hey everyone - I have a question pertaining to cropping in LR3. When I crop a photo, can I choose to crop it to a size I'd like to print like Picasa does? I've been exporting to a folder on my desktop and then cropping in Picasa and would like to eliminate this second step.
thanks in advance

wow -thanks very much for the quick reply.
ok, I'll try to keep this simple - I've done the following
specified jpeg as format
checked "resize to fit" using width x height
first phot is w = 10, H =8 , second photo is w = 6, h =4
chose inch under drop down
dont enlarge box is Not checked off - *wondering if this is whats going on??*
resolution is set at 240 pixels per inch
When comparing the two photos they look nearly identical, though the file sizes and pixel counts vary drastically.
I dont mind that the image doesnt look much different, I just dont want to get drasitcly different photos back from the print shop because I'm missing a step here
thanks again

Similar Messages

Unrestricted Crop in LR3?

How do I perform an unrestricted (freehand) crop in LR3?
I see crop presets for various aspect ratios, for original ratio, or for a custom ratio that would be entered before performing the crop. I need to be able to do an unrestricted crop like those offered in PhShop CS, PSE, etc.

Simply unlock the preset (click on the padlock icon). That puts you into what you're terming "freehand" mode. You may then drag the crop frame (independently) from any corner or side.
Phil

When I crop in LR3 and move into PSE, the crop ratio changes.

I like LR's crop tool better than PSE, so I use that to crop before I move into PSE for further editing. I don't know if this would make a difference, but I do save the LR copy as a jpeg first cause I'm not always ready to finish editing it at that point (I know, not what everybody else does but it works for me). I crop in LR using 15x11, but when I open it in PSE it is only 13x9 (roughly). Any idea why the size would change? Should I not crop until I'm done editing, then go back into LR for the final cropping? Any help will be much appreciated! Thanks!

I understand how that would work, but I don't understand why it does it even AFTER I save the LR file as a cropped jpeg? If I save a crop in LR, shouldn't it save at the size I crop it to? I'm mainly referring to photos that I save first as a jpeg and export to my folders from LR, THEN open in PSE.

Changing pixel aspect ratio during cropping (LR3.2)

When I crop sometimes the pixel aspect ratio changes here. I.e. the pic get stretched in horizontal or vertical way/or compressed. Any body seeing this also? After some time it does change to normal, but it makes cropping rather difficult when in a hurry.

I'm not sure I understand your problem, but I think what bothers you is the technique that has been in place in LR2 already for switching between landscape and potrait format of the crop, which in LR3 can be acomplished by the X keyboard shortcut.
Moving your mouse horizontally or vertically on a locked aspect ratio, the format will change from portrait to landscape or vice versa. To enlarge or diminish the size of the crop, you have to move the mouse diagonally.
Beat Gossweiler
Switzerland

Iterate over selected images, read/change crop settings in LR3?

Since there is a new SDK I thought I ask again for this version:
I'd like to write a Lightroom script which iterates through all selected images, read and change the crop settings of (nearly) every image.
Is this possible to achieve in lua using the LR3 SDK? Or is it still not possible to read and write development settings?
Kind regards,
Sam

You can read individual develop settings but only apply presets. That's better than nothing, but allowing us to write develop settings would have opened up a whole new world of possibilities - I think it scared them...
A possible work around: read settings, create a temp preset, write changed settings to the temp preset, then apply it.
NoYeah?
Rob

Still no option to include crop in User Preset in LR3...

Can anyone explain to me why the developers of Lightroom insist on excluding the option of saving crop ratios along with the other adjustments in the User Presets?
I see that new adjustments such as lens correction are now included as options in LR3 User Presets, so why has crop ratio not been added?
I am a professional photographer, shooting mostly interiors and still lifes with the camera tethered to my computer.
I switched from C1 Pro to Lightroom 2 due to unresoved software issues with C1 Pro and for the most part have been happy with switch, using the Auto Import feature to shoot directly into Lightroom and applying a User Preset automatically on the import.
However, I have been frustrated by the inability of Lightroom to automatically apply a crop to an incoming image - frequently I am required to shoot for a specific layout and on many shoots art directors or clients are looking at new versions of images as they come on screen and to have to manually apply a crop before they can view an accurate composition is irritating for all.
I realise that it is now possible with LR3 to shoot tethered 'natively' into Lightroom 3, which solves the issue of automatically applying a crop to an image on import by selecting 'same as previous' under Develop Settings. However, I am unable to use the 'native' tethered option as, although I normally shoot with a 5D II which is supported, when mirror-lockup is enabled, the Lightroom tethered control panel will not fire the camera shutter (this is similar to C1 Pro). Therefore, I need to be able to use the Canon Eos Utility to fire the camera, coupled with the Auto Import of Lightroom when using mirror-lockup, which means being unable to apply a crop on import.
Adding the option to save a crop ratio with a User Preset would have two significant benefits in my opinion:
1. It would mean that a crop could be applied automatically on import when shooting tethered and not wanting to use LR3's native tethering interface.
2. Users of cameras not supported by LR3's tethering would be able to apply a crop automatically on import.
The other solution would be for the developers to include the 'same as previous' option for those using the Auto Import feature.
I really do hope that the option to save a crop ratio as part of a User Preset in Lightroom is included sooner rather than later, as I feel that it is a glaring omission in what is otherwise a very solid application.
Any views would be appreciated.
Regards
Liam

Thanks for suggestion Gary.
Using Live-view on 5D II does keep the mirror in the lock-up position and therefore you could use this technique with LR's tethering controls. However, for me this is not a solution for a few reasons: Live-view shooting drains the battery; extended use of Live-view can have a negative effect on sensor noise due to heat; sometimes it is very useful to be able to use the EOS Utility to control camera settings e.g. changing length of exposure for blending purposes without the need to touch the camera at all.
Liam

LR3 - Canon 7D ISO 3200 vs. lower ISOs - Crop Tool

Is anyone noticing significant crop tool response time differences between low ISO 7D Raw files and 3200 (or higher) ISO files in LR3? On the lower ISO files, the crop tool is just about immediate, yet with the 3200 ISO files, things are very much slower.. Angle tool, move (hand tool), etc. all take on very slow responses.
Thanks..
Jay S.

"Is it the crop tool? Maybe it's the effect of noise reduction...
Try turning off the Detail panel and see if there's any performance difference now."
Dorin.. The Detail panel is having a definite impace on the speed.. 1600 or 3200, turning off detail made a huge difference in crop ability. Hate the thought of having to turn off detail while working on leveling, etc. Haven't tried other things like spot, etc. to see if there is an impact there. For a given ISO, I like to apply as a preset to the whole batch before working on the images - just as a generic starting point. I went back to LR 2.7 and do not see any difference with detail on or off with regard to crop tool.
Thanks. Looks like you hit the "bug" if it is one. I've no idea why that seperate catalog is like an order of magnitude slower though.
Thanks again..
Jay S.

LR3 crop is lost in CS5

When I crop an image in LR3 to an 8x10 and then Photo>Edit In> CS5 (import a copy with LR3 adjustments) it comes in at 9.5 x 11.75 ? I am in the Develop Mod, I use the crop overlay with custom crop. I export at a resolution of 300. What am I doing wrong ?

8x10 is just the aspect ratio, not the physical size. These are not inches.
You're doing nothing wrong. Just go on with your work.

Rotate Crop Aspect Ratio Help LR3

I know that i am missing something totally easy here...but none the less I cant figure it out. How do I use the crop aspect change short cut key (x) without flagging my photos?
I have made sure that I am in crop mode. When I hit the x key it flags the photo to discard.
Thanks for your help!

Thank you Hal!

Bug in Print Module, LR3.6, custom package

Hi everybody,
After two days of unequal fight with Print Module bug I hope I finally pinned it down.
Hope it saves someone time
I have my photos usually cropped in DSLR format (2:3)
Printing I use often two popular formats 13x18cm and 15x21cm that are close to 5:7 (first one is 5x7in)
Initially I was using virtual copies and had them cropped to 5:7 format.
However this makes a little mess in my workflow and it's time consuming.
What I found was Custom Package in Print Module.
Having cell with target size I drag desired photo into the cell and using cmd-key drag this foto to have proper look as the width target format is smaller. So far so good, but ...
From time to time printed photo looked totally different from what I saw on-screen.
First of all there are couple threads about that problem. I visited them but they remain unanswered
http://forums.adobe.com/message/3344521
http://forums.adobe.com/message/3278739
http://forums.adobe.com/thread/697107
http://forums.adobe.com/message/3885690
There are visual samples there of what happens.
Photos in JPG file that was created from LR look differently than in LR. Photos in file are bigger or/and wrong positioned within the cell
What I managed to find is:
Everything goes fine until photo is rotated by 'Rotate to Fit' function. It happens in my case only with photos that have the same orientation that template.
Example:
Template is set on A4 borderless format set to portait (Page Setup... button).
Two cells 14,85cm height x 21cm width (A5 format). First one over second and both in landcape position.
When I drag photo cropped in Landscape orientation such a photo is rendered properly.
When I drag photo cropped in Portrait orientation it's atutomatically rotated 90 degrees (couterclockwise) by "Rotate to Fit option" and that is when **** happens.
Final print (to file or printer) shows that user dragging is omitted in render. What's more if "Photo border" is set to on, photo in this cell is not reduced. Instead of this (as far as I can see) photo border just crop some part of picture.
If I switch orientation of the A4 page from portrait to lansdcape, magically photos that are cropped in portrait orientation start to render good (they are not rotated now) while those in landscape start to render wrong.
This looks 99% as software bug.
I'm using LR3.6 on mac osx 10.6.8
I'd like someone to follow it and to check if the same happens on different Mac or Windows.
Cheers
Robert

Confirmed in LR 5.3, OS X 10.9.1.
Screen display is fine, user repositioning is ignored when printing if page is in landscape mode and the image is rotated 90° (Rotate to Fit on). A4, Epson printer. Bug also appears in PDFs generated via the "Printer…" button. I didn't check JPEG export.

Lightroom 4 custom crop boundary area display

We post hundreds of sports photos at a time. We set a custom crop 7.5x10 which most closely enables all our supported print aspect ratios (4x6, 5x7, 8x10, etc.). We have to be careful that the important photo elements are NOT in the boundary area inside the crop. I mean we need to keep space inside our standard crop so that regardless of which print size you pick that the trim (either top/bottom or sides depending on the print) will not cut of important photo elements. It would be very helpful if we could have Lightroom 4 display this boundary area with some type of shading. That way when we do the crop we can see if an important photo element is in the boundary area, and then we can increase the crop. Our objective is as tight a crop as appropriate while preserving the boundary area. A visual cue would be most helpful with this work.
I'd appreciate suggestions about how to accomplish this if it is already possible or have Adobe engineers add the visual cue for a configurable boundary area inside the crop.

I understand what you are getting at. I went into PS and created a series of shape layers at the specified ratios and then centered them. I then expanded each proportionally so that there long side was 10 inches. On a portrait oriented photo there is a portion on the left and right that cropped on a 5x7 or 4x6. I tinted the shapes and then masked out the center area. I then save this as a .png file with the intent of using it as a watermark. This worked but is an after the fact confirmation.
While in the crop tool you can press the "O" key and rotate through different crop guides. The last one is a grid. (works the same in LR3) When I had the crop aspect ratio set to 7.5 x 10 (which LR4 simplfied to 3x4) this shows for me as a 12 wide by 16 long grid. Coincidentally, the crop danger zone appears to be very close to exactly one grid in width.
I don't know if this is a "close enough" solution for you.
**** I'm glad I didn't hit send before going back and looking at LR4 again. This works on a full size image with a maximum size crop. But if you starting shrinking the crop the grid size changes. Now if Adobe could maintain the grid so it ALWAYS shows in say 10 percent increments, then your danger zone would always be the left most and right most 10 percent.

How do I permanently save edits I make in LR3?

I am new to this software. I have an existing collection of over 40,000 images. I am an amateur photographer making images for
my own amusement, and I also document objects that are brought to me for restoration. Both purposes are very important to me.
I have been using Picasa to manage my photos for several years. While it is limited, it is very elegant and easy to use. It also does not change the original file until a request is made for a permanent change, at which point a backup original is made. Once saved, the picasa edit can be viewed by any other viewer, software or browser I am aware of.
I am liking all the manipulations that are possible with LR3. I am concerned that there seems to be no way to save an edited file so that it can be viewed using other (non adobe) software. I want to be able to upload images to my website, and to be able to share with my customers, friends, family etc. I do not want to be locked in to Flickr . I am very concerned that I might spend huge amounts of time learning LR3 then even huger amounts of time editing my images with it, only to find at some point down the road that I will be locked in and unable to see my work using another software/viewer/browser. I.E. what if I were to convert to a Mac and decide to use Aperture 3 instead? What if somebody else comes up with software I prefer and wish to change? Am I always going to be bound up with LR to see my edited work? What if Adobe decides to no longer support LR3 and replaces it with a product that I find unacceptable, unaffordale or incomprehensible? (all three scenarios have happened to me in the past). Will I have to rework thousands of images years from now? I am very confused about this, and would much rather drop the software now before I get in too deep. I absolutely do not want to be commited to having to use anybody's software forever.
I see the line "Web Photo Gallery created by Adobe Lightroom." and it terrifies me. I may have used a Pentax camera, and Adobe software, but the images were created by me, and I wish to retain total control over my work.
JG

I quite understand and greatly value the non invasive features that preserve the original data.
I also appreciate basics, from which I can learn and extrapolate.
I edited and exported a dng file, to a jpeg format, it went from 9mb to 865kb
I edited and exported a 9.6mb jpg which became a 1.5 mg jpg.
I did a separate edit (major crop) and small adjustements using Picasa, and saved a copy. Both jpg.
The original was 11.4 mb, and the copy 5.2 mb.Used the same file to do an edit using the camera mfg
software, and the file went from 11.4 to 983kb
I may be missing something very obvious or I may be overly paranoid.
Most of the time, once I am done with an edit, I do not wish to revisit.
I am concerned about what happens to 90% or so of the data. I remain
unclear about the integrity of the "exported"/ "saved" edit in the event that original file/data is lost, or separated from
the LR coding instructions,
or if LR becomes unsupported or abandoned.
Being able to reference conservation treatment data 10 or 15 years down the road can be critical.
Memory is cheap. If the answer is multiple back ups for original data, metadata, and pertinent software, then
that is an answer. If it means the editied image is forever and permanently linked to LR, and without LR,
the original file must be re-edited to similar result, that is also an answer. If the loss of information results in image degradation
analagous to photographing a magazine print of an original transparency, or trying to work with data from a thumbnail image,
that is also an answer. Whichever if any is the most accurate, defines my approach to how I might use this software. A little like archival quality printing versus drug store snapshot prints. Time spent editing is orders of magnitude greater that time spent capturing the image. Protecting that investment of time is what I am ultimately interested in.

LR3 "Extra Processing in Develop" Performance Problem

I have been investigating a specific LR3 performance problem. It may explain a small subset of the problems people have reported in the "Why is LR3 So Slow?" thread. I'm starting this thread to focus on this particular problem. I hope others will confirm/refute/refine my findings.
The Problem
In Develop, when I make an adjustment, normally the following happens: The CPU usage (as shown in Activity Monitor's bar graph) jumps to between 50 and 75% for all four cores, the updated image appears, and the CPU usage settles back down. This all happens in less than half a second. Note: this is with the image at the Fit size. However, sometimes I instead get the following after an adjustment: the CPU usage jumps to 50 to 75% for all four cores and the updated image appears as usual, however, instead of settling back down, the CPU usage jumps up to 90 to 100% for all cores and stays there for 3 to 5 seconds before settling down. Thus it appears that LR is doing some kind of "extra processing" since a lot of computation is happening AFTER the updated image has already appeared. I will refer to this problem as "EP". Obviously, when you are getting EP, editing in Develop becomes very balky.
Dependency on ratio between image size and displayed size
It appears that EP only happens when the displayed size of the image (in Fit zoom level and perhaps also Fill zoom level) is above a certain percentage of the actual image size (as currently cropped). Evidence: When editing full 21MP 5D2 images, I don't experience EP. If I crop the 5D2 image fairly significantly, then I can get EP. When editing 10MP images from my Canon S90, I usually get EP for landscape orientation pictures but not for portrait orientation pictures (since in Fit mode, landscape images display at a higher zoom level than portrait images). If I am getting EP, I can eliminate it by sufficiently reducing the size that LR is displaying the image by resizing the LR window smaller, opening additional panels (I normally edit with only the right panel open), displaying the toolbar, etc. It appears that EP is enabled when the displayed image is about 50% or larger w.r.t. the actual image (as currently cropped). For example, EP becomes enabled when a 3648 pixel wide S90 image is displayed at least 17 and 7/8 inches wide on my 100 ppi monitor (i.e. about 1787 pixels).
Dependency on HOW an adjustment is invoked
Even when the displayed image size is large enough w.r.t. the actual image size to enable EP, whether you get it on a given adjustment depends on how you invoke it:
- If you CLICK (i.e. press the mouse button down and quickly release it) on the track of one of the sliders (a technique I use often to make big jumps), EP will happen.
- If you press the mouse button down on a slider handle, drag it to a new position, and quickly release the mouse button), EP will happen
- If you press the mouse button down on a slider handle, drag it to a new position, but continue to hold the mouse button down until the displayed image is updated, EP does NOT happen (either before or after you then release the mouse button).
- If you highlight the numeric field at the end of a slider and use the arrow keys (possibly along with Shift) to increment or decrement the value, EP does NOT happen.
- EP will happen if you resize the LR window such that the displayed image size is above the threshold. (In fact, I determined the threshold by making a series of window width increases until I saw EP indicated by the CPU bar graphs.)
- EP can happen with local adjustment brush applications, but as with the sliders, it depends on HOW you perform the brush stroke. Single click and drags with immediate mouse release cause EP, drags with delayed mouse button release don't.
- Clicking an earlier History state causes EP
- More exploration could be done. For example, I haven't looked at Graduated Filter and Spot Removal adjustments.
My theory of what's happening
With LR2, my understanding is that in Develop mode when the displayed image is below 1:1 zoom level, after an adjustment is invoked, LR calculates the new version of the image to display using a fast, simplified algorithm that doesn't include the more computationally intensive adjustments like Sharpening and Noise Reduction (and perhaps works on a lower rez version of the image with multiple sensels binned together?). It appears that in conditions described above, LR3 calculates the initial, fast image update and then goes on to do the full update of the image, including the computationally intensive adjustments. Evidence: setting Sharpening Amount and Luminance and Color Noise Reduction to zero eliminates EP (or reduces the amount of time it takes to be barely noticeable). I'm not sure whether the displayed image is updated with the results of the extra processing. I think the answer is Yes since when I tried an adjustment of changing Sharpening Amount from 0 to 90, the initial update of the displayed image showed sharpening but after the EP, the displayed image was updated again to show somewhat different sharpening. Perhaps Adobe felt that it would be useful to see the more accurate version of the image when it is at or above 50% zoom. Maybe the UI is supposed to cancel the EP if you start to make another adjustment before it has completed but the canceling doesn't happen unless you invoke the adjustment in one of the ways described above that doesn't cause EP.
Misc
- EP doesn't seem to happen for Process 2003
- As others have mentioned, I'm surprised that LR (both version 2 and 3) in 64bit mode doesn't use more available RAM. I don't think I've seen LR go above 4GB of virtual memory or above 3GB "Real Memory" (as reported by Activity Monitor) even though I have several GB free.
- It should be obvious from the above that if you experience EP, there are workarounds: reduce the size of the displayed image (e.g. by window resizing), invoke adjustments in ways that don't cause EP, turn off Sharpening and Noise Reduction until the end of editing an image.
System specs
First generation Intel Mac Pro with two dual-core CPUs at 2.66 Ghz
OS 10.5.8
21GB RAM
ACR cache on volume striped across 3 internal SATA drives
LR catalog and RAWs on an internal SATA drive
30" HP LP3065 monitor (2560 pixels wide)
NVIDIA GeForce 7300 GT

I'm impressed by your thorough analysis.
Clearly, the programmers haven't figured out the best way to do intelligent caching and/or parallel rendering at a reduced size yet.
In my experience reducing the settings in the "Details" panel doesn't help.
What really bugs me is that the lag (or increasing lack of interactiveness) depends on the number of adjustments one has made.
This shouldn't be the case. If a cache is produced then every further adjustment should only cost the effort for that latest adjustment and not include adjustments before it. There are things that stand in the way of straightforward edit applications:
If you work below 1:1 preview, adjustments have to be shown in a reduced form. If you don't have a way to faithfully mimic the adjustments on the reduced size, you have to do them on the original image and then scale down. That's expensive.
To the best of my knowledge LR uses a fixed image pipeline. Hence, independently of the order in which you apply edits, they are always performed in the same fixed order. Say all spot removal operations are done first. If you have a lot of adjustment brush edits and then add a spot removal operation, it means that all the adjustment brush operations have to be replayed each time you do a little adjustment on your spot removal edit.
I believe what you are seeing is mostly related to 1.
I also believe that the way LR currently handles a moderate number of edits is unacceptable and incompatible with the notion that it is usable in a commercial setting for more than trivial edits. I suspect there is something else going on. If everyone saw the deterioration in performance after a number of edits that I see, I don't think LR would be as accepted as it is. Having said that, I've read that the problem of repeated applications of the adjustment brush slowing LR down has existed for a long time. I truly hope that this doesn't mean we'll have to live for it for the foreseeable future.
There are two ways I can see how 2. should be addressed:
combine the effects of a set of operations into one bitmap operation. Instead of replaying all adjustment brush strokes one after the other (speedwise it feels like this is happening), compute a single bitmap operation that combines all effects.
give up the idea that there is an image pipeline with a fixed execution order.
Some might argue that the second point is at odds with the whole idea of parametric editing, but I dispute that. Either edit operations are commutable in which case the order is immaterial, or they are not. If they are not, the user applies the edits in a way as he/she sees fit and will thus compensate for any effect of a changed ordering.
N.B., currently the doctrine of "fixed ordering of edit applications" results in the effect that even if you convert an image into B&W all your adjustment brush edits that applied colour tints will still show through. Reasoning: The user should be able to locally tint a B&W image. I agree with the latter but this could be achieved by only applying those tinting brush strokes that were created after the B&W conversion. All the ones that happened before should only be used to obtain the correct luminance values for the B&W conversion but obviously they shouldn't cause tinted areas.
The above example demonstrates to me that users naturally expect operations to occurr in the order they have been introduced, not in a fixed predefined order. If that principle were followed, I see no reason why the speed of a single edit should depend on the number of edits that were done to the image before.
I hope the programmers can (and the management wants to) address the performance issues. While I find LR usable for pretty modest edits, in no way the performance on my system approaches that would I would expect from an industrial strenght application.
P.S.: Your message reminded me of the following: When I experience serious lag with LR showing the strokes I make with an adjustment brush, it helps to pause a moment after the first click before one starts moving. This allows LR to catch up and then one can see the effect of the application pretty much interactively. Otherwise, there is terrible lag and the feedback where you have brushed an effect comes way too late.

Can't edit LR3 image in CS5 32bit

Hi, I recently got a new PC and now can't open images in CS5 32bit from LR3. I used to launch CS% then right mouse click image and "Edit in Adobe Photoshop CS5" but now CS5 launches but no image appears and i get an error message saying The Lightroom catalog named.... cannot be opeened because another appliation already has it opened Quit the other copy of LR before trying to launch" - but there nothing else open.
Another message I get is:
If I don't open CS5 32 bit first and just ight mouse click image and "Edit in Adobe Photoshop CS5" the image opens normally in 64bit CS5 but I can't apply my Nik filters from the 64 bit version. Have tried uninstalling and reinstalling LR3 and CS5 without fixing the problem.
My CS5 System info:
Adobe Photoshop Version: 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch]) x32
Operating System: Windows 7 64-bit
Version: 6.1
System architecture: Intel CPU Family:6, Model:10, Stepping:7 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2
Physical processor count: 8
Processor speed: 0 MHz
Built-in memory: 8160 MB
Free memory: 5431 MB
Memory available to Photoshop: 3255 MB
Memory used by Photoshop: 70 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Normal
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: False.
OpenGL Crash File: Not Detected.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GTX 550 Ti/PCI/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 1050, right: 1680
Video Card Number: 1
Video Card: NVIDIA GeForce GTX 550 Ti
Driver Version: 8.17.12.7533
Driver Date: 20110520000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode: 1680 x 1050 x 4294967296 colors
Video Card Caption: NVIDIA GeForce GTX 550 Ti
Video Card Memory: 1024 MB
Application folder: C:\Program Files (x86)\Adobe\Adobe Photoshop CS5\
Temporary file path: C:\Users\Chris\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
C:\, 1.82T, 1.14T free
E:\, 1.82T, 1.23T free
Primary Plug-ins folder: C:\Program Files (x86)\Adobe\Adobe Photoshop CS5\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2010/10/04-23:36:11   64.441628   64.441628
   adbeape.dll   Adobe APE 2010/02/23-12:40:58   61.421986   61.421986
   AdobeLinguistic.dll   Adobe Linguisitc Library   5.0.0
   AdobeOwl.dll   Adobe Owl 2010/06/03-13:43:23   3.0.93   61.433187
   AdobeOwlCanvas.dll   Adobe Owl Canvas   3.0.68   61.2954
   AdobePDFL.dll   PDFL 2010/12/13-23:37:10   64.341419   64.341419
   AdobePIP.dll   Adobe Product Improvement Program   5.0.0.2021
   AdobeXMP.dll   Adobe XMP Core   5.0   61.134777
   AdobeXMPFiles.dll   Adobe XMP Files   5.0   61.134777
   AdobeXMPScript.dll   Adobe XMP Script   5.0   61.134777
   adobe_caps.dll   Adobe CAPS   3,0,116,0
   adobe_OOBE_Launcher.dll   Adobe OOBE Launcher   1.0.0.64 (BuildVersion: 1.0; BuildDate: Mon Jan 26 2010 21:49:00)   1.000000
   AFlame.dll   AFlame 2010/02/23-17:27:33   61.421976   61.421976
   AFlamingo.dll   AFlamingo 2010/02/23-17:27:33   61.421978   61.421978
   AGM.dll   AGM 2010/10/04-23:36:11   64.441628   64.441628
   ahclient.dll    AdobeHelp Dynamic Link Library   1,5,0,30
   aif_core.dll   AIF   2.0   53.422628
   aif_ogl.dll   AIF   2.0   53.422628
   amtlib.dll   AMTLib   3.0.0.64 (BuildVersion: 3.0; BuildDate: Mon Jan 26 2010 21:49:00)   1.000000
   amtservices.dll   AMTServices   3.0.0.64 (BuildVersion: 3.0; BuildDate: Mon Jan 26 2010 21:49:00)   1.000000
   ARE.dll   ARE 2010/10/04-23:36:11   64.441628   64.441628
   asneu.dll    AsnEndUser Dynamic Link Library   1, 7, 0, 1
   AXE8SharedExpat.dll   AXE8SharedExpat 2010/02/23-17:27:33   61.421978   61.421978
   AXEDOMCore.dll   AXEDOMCore 2010/02/23-17:27:33   61.421978   61.421978
   Bib.dll   BIB 2010/10/04-23:36:11   64.441628   64.441628
   BIBUtils.dll   BIBUtils 2010/10/04-23:36:11   64.441628   64.441628
   boost_threads.dll   DVA Product   5.0.0
   cg.dll   NVIDIA Cg Runtime   2.0.0015
   cgGL.dll   NVIDIA Cg Runtime   2.0.0015
   CoolType.dll   CoolType 2010/10/04-23:36:11   64.441628   64.441628
   data_flow.dll   AIF   2.0   53.422628
   dvaadameve.dll   DVA Product   5.0.0
   dvacore.dll   DVA Product   5.0.0
   dvaui.dll   DVA Product   5.0.0
   ExtendScript.dll   ExtendScript 2010/10/19-10:22:12   61.445301   61.445301
   FileInfo.dll   Adobe XMP FileInfo   5.0   61.134777
   icucnv36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896
   icudt36.dll   International Components for Unicode 2009/06/17-13:21:03    Build gtlib_main.9896
   image_flow.dll   AIF   2.0   53.422628
   image_runtime.dll   AIF   2.0   53.422628
   JP2KLib.dll   JP2KLib 2010/12/13-23:37:10   64.181312   64.181312
   libeay32.dll   The OpenSSL Toolkit   0.9.8g
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2, 0, 1, 11
   MPS.dll   MPS 2010/12/13-23:37:10   64.450375   64.450375
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.6161
   msvcp71.dll   Microsoft® Visual Studio .NET   7.10.3077.0
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.6161
   msvcr71.dll   Microsoft® Visual Studio .NET   7.10.3052.4
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.6161
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS5   CS5
   Plugin.dll   Adobe Photoshop CS5   CS5
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (32 bit)   2.0.0.746
   PSArt.dll   Adobe Photoshop CS5   CS5
   PSViews.dll   Adobe Photoshop CS5   CS5
   SCCore.dll   ScCore 2010/10/19-10:22:12   61.445301   61.445301
   shfolder.dll   Microsoft(R) Windows (R) 2000 Operating System   5.50.4027.300
   ssleay32.dll   The OpenSSL Toolkit   0.9.8g
   tbb.dll   Threading Building Blocks   2, 1, 2009, 0201
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   1.0.0.68 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   1.0.0.68
   WRServices.dll   WRServices Thursday January 21 2010 12:13:3   Build 0.11423   0.11423
   wu3d.dll   U3D Writer   9.3.0.113
Installed plug-ins:
   3D Studio 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Accented Edges 12.0
   ADM 3.11x01
   Angled Strokes 12.0
   Average 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   BackgroundFilter NO VERSION
   BackgroundFilter NO VERSION
   Bas Relief 12.0
   BMP 12.0.2
   Camera Raw 6.4.1
   Chalk & Charcoal 12.0
   Charcoal 12.0
   Chrome 12.0
   Cineon 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Clouds 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Collada 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Color Efex Pro 3.0 Complete 3.0.0.4175M
   Color Efex Pro 3.0 Complete 3.0.0.4175M
   Color Halftone 12.0.2
   Colored Pencil 12.0
   CompuServe GIF 12.0.2
   Conté Crayon 12.0
   Craquelure 12.0
   Crop and Straighten Photos 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Crop and Straighten Photos Filter 12.0.2
   Crosshatch 12.0
   Crystallize 12.0.2
   Cutout 12.0
   Dark Strokes 12.0
   De-Interlace 12.0.2
   Dfine 2.0 NO VERSION
   Dfine 2.0 NO VERSION
   Dicom 12.0
   Difference Clouds 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Diffuse Glow 12.0
   DIGITAL GEM Airbrush Professional v2.1.0 2.1.0
   DIGITAL GEM Airbrush Professional v2.1.0 2.1.0
   DIGITAL GEM Professional v2.1.0 2.1.0
   Displace 12.0.2
   Dry Brush 12.0
   Eazel Acquire 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Embed Watermark 4.0
   Entropy 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Extrude 12.0.2
   FastCore Routines 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Fibers 12.0.2
   Film Grain 12.0
   Filter Gallery 12.0
   FineStructuresFilter NO VERSION
   FineStructuresFilter NO VERSION
   Fresco 12.0
   Glass 12.0
   Glowing Edges 12.0
   Google Earth 4 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Grain 12.0
   Graphic Pen 12.0
   Halftone Pattern 12.0
   HDRMergeUI 12.0
   HotPixelsFilter NO VERSION
   HotPixelsFilter NO VERSION
   IFF Format 12.0.2
   Ink Outlines 12.0
   JPEG 2000 2.0
   Kurtosis 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Lens Blur 12.0
   Lens Correction 12.0.2
   Lens Flare 12.0.2
   Lighting Effects 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Liquify 12.0.1
   Matlab Operation 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Maximum 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Mean 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Measurement Core 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Median 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Mezzotint 12.0.2
   Minimum 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   MMXCore Routines 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Mosaic Tiles 12.0
   Multiprocessor Support 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Neon Glow 12.0
   Nik Selective Tool 2.0.2.4304
   Nik Selective Tool 2.0.2.4304
   Note Paper 12.0
   NTSC Colors 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Ocean Ripple 12.0
   OpenEXR 12.0.2
   Paint Daubs 12.0
   Palette Knife 12.0
   Patchwork 12.0
   Paths to Illustrator 12.0.2
   PCX 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Photocopy 12.0
   Photoshop 3D Engine 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Picture Package Filter 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Pinch 12.0.2
   Pixar 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Plaster 12.0
   Plastic Wrap 12.0
   PNG 12.0.2
   Pointillize 12.0.2
   Polar Coordinates 12.0.2
   Portable Bit Map 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Poster Edges 12.0
   Radial Blur 12.0.2
   Radiance 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Range 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Read Watermark 4.0
   Reticulation 12.0
   Ripple 12.0.2
   Rough Pastels 12.0
   Save for Web & Devices 12.0
   ScriptingSupport 12.0.4
   Send Video Preview to Device 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   ShadowsFilter NO VERSION
   ShadowsFilter NO VERSION
   Sharpener Pro 3.0: (1) RAW Presharpener 3.0.0.4304
   Sharpener Pro 3.0: (1) RAW Presharpener 3.0.0.4304
   Sharpener Pro 3.0: (2) Output Sharpener 3.0.0.4304
   Sharpener Pro 3.0: (2) Output Sharpener 3.0.0.4304
   Shear 12.0.2
   Silver Efex Pro 3.0.0.751
   Silver Efex Pro 3.0.0.751
   Skewness 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   SkinFilter NO VERSION
   SkinFilter NO VERSION
   SkyFilter NO VERSION
   SkyFilter NO VERSION
   Smart Blur 12.0.2
   Smudge Stick 12.0
   Solarize 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Spatter 12.0
   Spherize 12.0.2
   Sponge 12.0
   Sprayed Strokes 12.0
   Stained Glass 12.0
   Stamp 12.0
   Standard Deviation 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   StrongNoiseFilter NO VERSION
   StrongNoiseFilter NO VERSION
   Sumi-e 12.0
   Summation 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Targa 12.0.2
   Texturizer 12.0
   Tiles 12.0.2
   Torn Edges 12.0
   Twirl 12.0.2
   U3D 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Underpainting 12.0
   Vanishing Point 12.0
   Variance 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Variations 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Video Preview 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Viveza 1.0.3.4269
   Viveza 1.0.3.4269
   Water Paper 12.0
   Watercolor 12.0
   Wave 12.0.2
   Wavefront|OBJ 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   WIA Support 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   Wind 12.0.2
   Wireless Bitmap 12.0.4 (12.0.4x20110407 [20110407.r.1265 2011/04/07:02:00:00 cutoff; r branch])
   ZigZag 12.0.2
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
   Access CS Live
   CS Review
   CS News and Resources
Installed TWAIN devices: NONE

Try removing the prefernces files first for LR and if that doesn't help then for PS.

Crop live-preview on 2nd monitor

isn't working anymore in LR4.2. In LR3 this was a very useful feature and I want it back - do I miss something or was the live-crop-preview removed from LR4?

Yep - when the navigator is on it does!
Nevertheless this is a workaround that shouldn't be neccesary using a pro-software.
Hope this will be fixed in the near furure ...

Cropping in LR3?

Similar Messages

Maybe you are looking for