Lightroom 5.2 crop overlay issues and catalog issues on windows 7

  • 1
  • Problem
  • Updated 5 years ago
I have lightroom 5.2, upgraded from lightroom 4.4 running on win 7. three problems I have.

1) Crop overlay guild not in correct orintaion when using the aspic ratio. for landscape, it shows portrait, for portrait it shows landscape. Using X does not fix the problem.

2) I worked on a few images, going from lightroom to CS6. Shutdown both lightroom and CS6 for the night. Came back next morning and the TIFF files that were created, were no longer in the catalog, but in the file folder. had to go and place them back into the catlog category.

3) My machine has 16meg ram and 2meg nivia card. Redering is still slow with lightroom being the only program running. Lots of flickering screens.

I would like to know if these are known problems, and fix is in the works or not. If you need more information, please let me know.
Photo of Dennis Smith

Dennis Smith

  • 4 Posts
  • 0 Reply Likes
  • sad as I was looking forward to these options

Posted 5 years ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1373 Posts
  • 335 Reply Likes
#1 Use the [Shift][ O ] Key to reorient the Crop Overlay.
#2 Never seen that happen Mac or PC
#3 Not experiencing slowness or flickering screens
Photo of Dennis Smith

Dennis Smith

  • 4 Posts
  • 0 Reply Likes
Ok, thanks, the shift O worked.

For #2, PC. It has happened twice, but I would have to say it is intermittent. I worked on other images and it did not happen. So, it is a puzzle.

#3, the rendering is a bit slow. Like I use the adjustment brush for burning/dodging. I actually use the adjustment brush a lot. When masking, it is slow and flickers. the clone tool, it also flickers if there are a lot of spotting done.

I decked out this machine so I can use it with LR/CS6 and plugin's without worrying about memory. I can add more, but, it shouldn't be constrained as it is a new machine, and I keep it pretty clear of trash.

I know LR5 is still pretty new, but it seems 5.2 is acting like the beta. I thought waiting for release 2 would have fixed these things. But, I totally forgot about shift O, so, maybe it's me. LOL