There is also another bug with cropping (I don't know if it's a independend bug):
When you crop a landscape area out of a portrait image and copy paste the cropping (Ctrl+Shift+C/+V) to another image the target picture often gets cropped falsely orientated (in the above example you may get a portrtait cropped area)
Same problem here since upgrading to LR5. Very frustrating -- it will even happen to images I've edited long before if I happen to scroll through them as I work on other images in the same project!
The images randomly change crop position when I navigate away and navigate back- it seems to happen most often on rotated crops.
The only way I've been able to work around this is by immediately exporting the photos that I am having cropping issues with. This significantly slows down my work flow. Does anyone know if this will be addressed in an upcoming update? The 5.2 update didn't seem to help, and I no longer have an old version I can go back to for the time being!
Had this exact problem today. An portrait image cropped to landscape. Every time you navigated to it in the film strip - it would revert to portrait again. i.e. it would perform it's own automated crop and put that in history. A program with a mind of it's own - not good.
Same problem as others have noted. Crop the image, navigate away - come back via the film strip and the image reverts to the previous crop state. Cmd+Z brings it back to how it should be - however, as soon as you navigate away and come back again - same thing happens. It's stuck in a loop.
Only happened with one image for me so far. Only temp solution was to save the image as a PSD in PS and then keep the final version as a PSD. Really annoying though.
I'm having this issue as well. For me it seems to be limited to JPG files and not my CR2 files. Very irritating when browsing back and forth in Develop module.
Anyone know if this has this been reported as an official bug? Tracking #? Seems like a long time to have this type of bug still unresolved.
Josh,
Yes, I'm using LR5.2. Weird thing is that usually the first time I go back and forth it is correct, however bug would usually start after 2nd time of cycling back and forth.
Funny thing, is I am not seeing the bug on the same photos this afternoon. Restarted program, however no system restart. Must be buggy under certain conditions...
The problem still exists in LR 5.6 on a Mac 10.7.5...
And it starts somewhat out of the blue - it worked fine for all photos I did between the time I once reported this failure in another thread and 5 p.m. this afternoon, when suddenly after a couple of crops and going to the next photo with "the mouse" (more precisely with the pen of a Tablet) it stopped working.
Tricks tried so far with no luck:
- Hard drive check and repair (repair despite the fact that no errors where found)
- Re-formatting of the drive (after backup of course) and putting it all up again on the now completely Mac Journaled formatted drive (before only the partition I used was formatted as Mac Journaled, but the main partition was formatted as some DOS FAT system)
- Restart of LR
Hope a system reboot will do the trick this time...
Nope, system reboot did not change a thing...
But there is a workaround it seems:
1) Crop the photo
2) Do NOT move to the next photo
3) Go into Settings -> Copy Settings
4) Go to the next photo
-- crop will be messed up now
5) Go back to previous photo
6) Use Settings -> Paste Settings
and go on as usual (at least for me the next crop after this photo was working as usual).
Did you try out the workaround that I described right above your post? (You might only have to Copy the Settings after clicking Done in the Crop-View) - Just trying to find out if that would work on later editions of MacOS too :)
I have been trying to reproduce this problem. Back in the 5.2 days, I could reproduce it but now, it is working as expected. I used your steps but I don't get any crop behavior that I don't expect. Can you post a screen shot of the crop and then the following image that has the "crop messed up"?
In the latest release what I observe is almost a "flashing" between edit sates, where all edits vanish and then reappear (including crop) randomly, almost as if the edits are saved but LR isn't consistently bringing up the edited preview and is instead building a new one from the original, unedited image. I'm not sure if this is the same behavior the above users are experiencing, but I thought I'd share the new experience and see what others say.
For refernce, I always create 1:1 previews on import in order to work on new image sets.
The reproduction of this one really is tricky, as it seems the error occurs at point X when fixed with my little workaround it does not re-occur for a while sometimes a day sometimes longer. But I had some left that I hadn't re-fixed, they are uploaded to my website here http://www.lilleulven.com/LRTrouble/n... (this gallery is only accessible with this link) and I put some titles to them that should describe what happens when. Feel free to contact me if my descriptions are confusing or if you need more information.
Both my files and the catalogue I am using are stored on the same external hard drive. And I guess by now I can rule out that it has anything to do with file-writing permissions, as for me the problem for one photo can be fixed by just copying the settings right after cropping it.
You need to use my steps to fix the wrong behavior not to produce it 🙂 Wished I had found a way to force the system to go wrong, but it comes like lighting out of nowhere... and a couple of cropped photos and copied settings later it disappears as if it had not been there, before turning up again later (later has so far been earliest the next day for me).
I hope you'll be able to reproduce it and will update this post (or add a new one) if I can figure out how to "turn the wrong behavior on".
I might have something... if my post from yesterday evening (Nov. 3rd 2014) starting "The problem still exists in LR 5.6 on a Mac 10.7.5... " is from around 21:48:59 CET, possibly about 15 minutes or even half an hour later ... than I think I know what is going on internally as I can find a message from Lightroom in my console stating "03.11.14 21:48:54,472 Adobe Photoshop Lightroom 5: Command not found: commitOperation:" unfortunately it does not say where this commit is not found.
I also have these messages with every start of Lightroom:
03.11.14 20:46:48,991 Adobe Photoshop Lightroom 5: Cannot add package named WFCoreTests
Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFCoreTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/WFCoreTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFCoreTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFCoreTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFCoreTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFCoreTests.agtoolkit
!! Did you remember to add a copy frameworks step to your project?
03.11.14 20:46:49,030 Adobe Photoshop Lightroom 5: Cannot add package named WFSQLiteTests
Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFSQLiteTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/WFSQLiteTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFSQLiteTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFSQLiteTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFSQLiteTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFSQLiteTests.agtoolkit
!! Did you remember to add a copy frameworks step to your project?
03.11.14 20:46:49,031 Adobe Photoshop Lightroom 5: Cannot add package named WFWebTests
Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFWebTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/WFWebTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFWebTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFWebTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFWebTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFWebTests.agtoolkit
!! Did you remember to add a copy frameworks step to your project?
03.11.14 20:46:49,031 Adobe Photoshop Lightroom 5: Cannot add package named WFOzClientTests
Looked in /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFOzClientTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/WFOzClientTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFOzClientTests.framework, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/Frameworks/WFOzClientTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/WFOzClientTests.agtoolkit, /Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/WFOzClientTests.agtoolkit
!! Did you remember to add a copy frameworks step to your project?
03.11.14 20:49:40,998 Adobe Photoshop Lightroom 5: readTokenFromKeychain failed with status -25300 and error The specified item could not be found in the keychain.
I have no clue if that is in any way related. Next time I see the cropping error occur I will check the console if there is anything reported that might help.
28
Replies
AdChoices