Blurry Photos After Editing bug - STILL not fixed!

Hi there,

I may have found a work around.

To recap, and in a few words:

After editing photos on MacBook Air and saving them, they look blurry.

Also, these same photos would not load to the cloud automatically.

"Unknown error" would appear when trying to move photos to a text, or onto another screen.

Here's how I fixed this problem:

I noticed that the photos I had edited and cropped, did not have this "blurryness" problem.

So, I decided to try cropping one of my blurry photos ever so slightly, to see it that would solve the problem, and voila!!

It worked.

Maybe this will help you too.

Take care!

For that setting you need a professional level app and that points me squarely at Lightroom Classic. I know it's subscription but the $120 you'll pay per year will be not far off the cut of keeping any other app up to date on yearly upgrades, plus you get Photoshop on both the desktop and mobile, as well Lightroom on the web, along with online space and a website maker. There simply isn't any other tool out there that represents such good value.

If you're worried about what happens should you stop paying the sub? Well Photoshop won't save and you'll lose the additional apps on the web and mobile. However, in Lightroom itself what you'll lose is the map and the edit tools only. YOu'll still be able to manage all your photos in the app, and even news ones. There is no data loss.

A sidecar file is essential a partner file for the original photo, so you export Myshot123.cr2 (or whatever) and the app creates another file that relates to it, called Myshot123.xml, and this contains the additional metadata. Serious photo apps check for the existence of a sidecar on import, and the data is imported along with the image.

Best of luck.

Hello, I ran into the same problem the other day with RAW photos uploaded to my MacBook. After editing and backing out, the photo would appear blurry and I wasn't able to export (in my case airdrop). Eventually I found a workaround, I went to the photo and right clicked to copy edits. I then reverted the picture back to the original, and then re-pasted the edits. You may or may not have to mess around with when you're re-pasting the edits, so for example, doing it while you're in the edit screen or when looking at the picture just as is when you are previewing (bad explantion but you get the idea). This did the trick for me, I was able to back out, the picture retained its resolution, and it was able to be exported. Pretty simple workaround so hopefully this works for some of you!

Hi. Just a follow up as I'm unsure what sort of success others may be experiencing. This annoying bug appears to have disappeared in Sonoma on my 14" MacBook Pro running Photos Version 9.0 (608.2.113). I've done some quick testing and haven't had any blurry photos after edit. Also returning to edited photos which were impacted by this bug which now look fine. Let's hope this is the last we'll see of this issue. Best to give credit where credit is due. Thanks to the Photos group at Apple for fixing this.

Michael

Hi David, I've been experiencing this same issue and done some deeper trouble-shooting, collecting my findings in a new thread.

Ventura generates corrupt preview files o… - Apple Community

I wanted you to know it's not just your Canon RAW images but seemingly any RAW image from any camera. And it's not just that the image will appear 'blurry' in Photos - the blurriness is a sign that the preview is corrupt and cannot be exported, shared, or edited in another application.

And it's not machine or architecture-specific, I've replicated the issue on a 2017 iMac Pro (intel) and 2022 Mac Studio (M1 Max).

There are alternatives to both LRC and Capture1. LRC is pretty much the industry standard and while it is a subscription app, you get quite a ot for that sub, including Photoshop, so as a value proposition it is worth checking out. I quite agree about the modal interface but you get used to it. It has far exceeded Aperture these days, and the recent changes to masking and noise reduction alone make it worth considering. CaptureOne is a lot more expensive and is trying to phase out its perpetual licence over time, so beware of that. LightroomCC is very good for sharing across devices, and close in feel to Photos, but it's sharing potential is greater - again as it should be as you're paying for it.

As a DAM or asset manager, Mylio is extremely good and is closer in feel to Photos/iPhoto than the other two. Also comparable as an editor/processor, and you can easily share to external editors and so on. It's very good at sharing across devices. For a pure DAM then PhotoSupreme is very good, not overly expensive for what it is and works extremely well with other apps like say, DXO Photolab. This app is an excellent processor but a poor DAM. Also worth looking at are apps like OnOne Photo Raw or Exposure 7.

As you're dealing with Raws then keywords can be exported as a sidecar file, which can be read by any serious photo manager.

After that:

27k isn't a large library. The real question is what exactly your requirements and your budget. What features of Photos do you like, need and what ones are not important to you. How much do you want to spend?

How can Apple expect pro users to take them seriously

I don't think Apple see themselves as offering software for pro users. If they did they'd never have walked away from Aperture. What pro user uses a give-away app for their work? Serious hobbyists and pro users are using serious software, like Lightroom Classic, CaptureOne, On1, DXO and so on.

Hardware is a different story, and all the high end pro apps run on Macs, and run very well on them.

None of this makes the issue any more acceptable, but the pace of adding raw support alone will confirm where serious photography sits on their priority list. Great hardware but Photos is an app optimised for the family snapper, probably with an iPhone, who wants as much of the work automated for him/her as possible.

Also, as ever, you're not talking to Apple here. Use the feedback mechanism for that.

As posted elsewhere on this thread, there may be a flicker of hope with the release of Sonoma sometime this fall; I sincerely hope this is the case. I was wondering, since the affected photos appear to be random, could it be the result of a particular edit? At first I thought it is only when I attempt to add some sharpening, and nothing else, but now I'm not so sure. Has anyone tried this? Indeed, it is very annoying.

Michael

14" M2 MacBook Pro

Ventura 13.5