Skip to main content
Adobe Photoshop Family

4 Messages

 • 

182 Points

Mon, May 7, 2012 11:43 AM

Implemented

8

Lightroom Classic: Raw Import Aspect Ratio Crop

Currently Lightroom uses the aspect ratio meta data in a raw file in a way which cannot be changed later on.It would be great, if Lightroom mapped the aspect ratio meta data, to the Crop tool in the Development section, so that the uncropped area of the sensor is available if needed.This has already been described in http://feedback.photoshop.com/photosh...

Responses

54 Messages

 • 

1.4K Points

9 years ago

For micro 4/3 cameras, would it be possible to provide a user preference for whether or not to respect the shooting aspect ratio on imported RAW files? I know this was changed due to user requests at some point in LR 3.x, but it seems to be one of those things that will never please all users, so perhaps a switch/preference is in order.

Specifically, I'm currently shooting with an Olympus E-M5, and find the EVF and LCD display most useful when shooting with a 3:2 ratio. I'm shooting RAW+JPEG, and it would be useful to have the full 4:3 frame available in some circumstances, so it would be great to have the full uncropped RAW file somehow available in LR4. I'm currently running an EXIFTool script before importing into LR, and it's working, but it's a bit cumbersome.

This reply was created from a merged topic originally titled
Can we have the full, uncropped RAW file from micro 4/3 cameras?.

Champion

 • 

677 Messages

 • 

8.7K Points

9 years ago

2 Messages

 • 

102 Points

8 years ago

I am using Lightroom with my Olympus XZ-1.
When I shoot in RAW (ORF) I like to select 3:2 aspect ratio in the camera because this way I see the 3:2 framing in the LCD when shooting.

The camera saves to file the full sensor data in 4:3 aspect ratio, along with the crop information to obtain the 3:2 aspect ratio image I have shot. In Olympus viewer it is possible to correct cropping if needed and the full sensor data is avaliable.

Lightroom does not treat the file as expected since the image is imported as a 3:2 image as shot, but the data around the 3:2 cropped area is not avaliable.
It should import ORF images as 4:3 images with a crop setting already applied, so that it could be modified.

This seems to happen with ORF files from all cameras as can be seen here:
http://www.flickr.com/groups/adobe_li...
http://forums.dpreview.com/forums/rea...
http://forums.dpreview.com/forums/rea...
http://e-p1.net/olympus-digital-pen-a...

This reply was created from a merged topic originally titled
Lightroom: Importing ORF files does not import all image area.

12 Messages

 • 

436 Points

8 years ago

Today I imported RAW images I shot on the Canon 5d3 with the camera set to Add Cropping Information set to 4:5 ratio. Crop lines are displayed on the camera LCD but you see the full frame outside of the crop when review files. Alarmingly, when I imported them to LR 4.1 RC, the images appeared cropped to 4:5. I though ok, I'll just go to the crop tool and I will see that a crop has been applied and I'll remove it. Unfortunately, there was no file beyond the crop lines, it could not be removed as far as I could tell. I called Canon and they told me to try Digital Photo Professional, a program that I never pay attention to. Sure enough, the images were intact when viewed there. There appears to be a bug when LR 4.1 RC encounters the crop tag on the raw file. I am running OS X 10.6.8 on a Mac Pro.

This reply was created from a merged topic originally titled
Lightroom4.1RC and Canon 5d Mark III Cropping Info/Ratio bug.

Champion

 • 

677 Messages

 • 

8.7K Points

8 years ago

For cameras that are supported starting with ACR 7.2 and LR4.2, one can set the Crop to "Original" to get back the in-camera cropped area.

For older cameras, there's the DNG Recover Edges plugin-in, which can be used to recover cropped area. The plug-in, as it's name implies, works only for DNG files, so one must convert a proprietary raw file before running.

11 Messages

 • 

204 Points

8 years ago

This is BS. Fix this now Adobe. You need to have your software able to deal with the full 4:3 image even when you're shooting in a cropped aspect ratio like square format!!!

Champion

 • 

1.4K Messages

 • 

24.5K Points

8 years ago

This was fixed months ago. What exactly isn't working for you?

12 Messages

 • 

436 Points

8 years ago

It was not for the Canon 5D Mark III I originally posted this about, nor do they intend to fix it.

Champion

 • 

1.4K Messages

 • 

24.5K Points

8 years ago

Perhaps you could give us some specifics then? Which camera? Which version of Lightroom?

Realize that just because a specific camera model doesn't match does not mean that your problem is not resultant from the same issue.

Have you tried the later versions of 4.x and used the DNG recovery tool where applicable?

946 Messages

 • 

13.8K Points

8 years ago

This was only "fixed" for cameras that came out after the fix. For cameras that came out before the fix, you can use the DNG Recover Edges plugin.

64 Messages

 • 

894 Points

8 years ago

The DNG Recover Edges is only a fix for people who use DNG.

A lot of us would never sacrifice future compatibility of our raw photos by converting them into DNG. (And I suppose that this group grew larger in the last few days.)

So it is still not fixed for us.

946 Messages

 • 

13.8K Points

And it isn't going to be. Like I said, it was only "fixed" for cameras released after the fix, and the DNG Recover Edges plugin is for the rest. If you are "the rest" I suggest you convert those images you need to "recover edges" from to DNG, while retaining the original raws as well, and in the future just shoot without any in-camera cropping.

64 Messages

 • 

894 Points

I know it isn't going to be fixed. You don't need to tell me that.

I just want to stop the misinformation. People keep claiming that it is fixed when it is not.

11 Messages

 • 

204 Points

8 years ago

I refuse to accept that Adobe will not fix this major problem. I will continue to complain about it and raise this issue until such time as it has been properly addressed. It's ridiculous that they have known about this for almost a year, and still have not fixed it! RIDICULOUS!

1 Message

 • 

60 Points

4 years ago

still not fixed in 3 years later :(

1 Message

 • 

60 Points

3 years ago

Still not fixed 5 years later...

6 Messages

 • 

134 Points

2 years ago

Still not fixed and now it's Oct. 2018. Come on Adobe, let's get this fixed.