![]() The first couple of AI features reviewed below are currently available for the desktop versions of Lightroom and Lightroom Classic. Luckily for me, there were no more surprises. I took each of those files along with their XMP sidecars and imported them into Lightroom directly. “Sir, you can use Denoise on Lightroom Classic directly,” he told me when I tried to explain what I was trying to do. The support rep clearly stated that there was no way of forcing the raw file to the cloud, even if ample space was left in your Adobe plan. Suddenly, I had 52 smart previews sitting in Lightroom that I couldn’t work on. Any edits you apply are done on this preview, not the raw file itself. All it does is push a “smart preview” of the file for you to view on any device. It turns out that Lightroom Classic does not sync the entire raw file to the cloud. 45 minutes later, after a long call with Adobe’s support team, I learned something new. One by one, each file in the collection that I tried to apply Denoise on gave me this error. Scrolling down to the Denoise button, I found no indication that I was about to hit a roadblock. So I then filtered the raw files in the collection that I had just synced and found a handful of high-noise files to work on. Yes, there were some jpegs in the collection, which by now I realized I couldn’t use Denoise on. ![]() Problem 2īy now, the cloud sync of the collection had been done. This brings me to the second problem (unrelated to the latest update but significant, nevertheless). Countless jpegs from my catalog need this tool right now. I need that AI power to work on jpegs more than anything right now. With some clever manipulation of its existing noise reduction sliders, it’s not complex to reduce noise in raw files already. I do think that Adobe could have waited to release Denoise after it added jpeg compatibility. Why would Adobe cripple its latest AI tool in this manner? It’s so much easier to reduce noise in raw files that have oodles more data in them than jpegs. “That’s not very useful,” I thought to myself, realizing that most of us with noisy images would probably realize that most of them are jpegs. I clicked on it as I prayed for Adobe to add sensor spot removal under its AI-enabled tools soon. ![]() “Reduce noise with AI,” read the caption below it. There it was, a sparkly new button that promised to make grainy color noise a worry of the part. As the album hadn’t yet synced here, I just picked one of the images already on the app and scrolled down to the Detail panel. Not quite… Problem 1Īfter adding over 60 images to the collection and syncing it to my Lightroom cloud on my Mac Mini, I opened up Lightroom on my Macbook. All I needed to do was to sync those images into a collection on Lightroom Classic and then access that collection on Lightroom. So when the opportunity to test out the new Denoise tool on Lightroom arose, I knew I had tons of underexposed, noisy images to use for this review. But as Capture One still hasn’t given any indication of bringing out a smartphone app, Adobe Lightroom (not the Classic version) has been my go-to editing software when I’m out and about. Until last year it was my primary post-processing tool until I began using Capture One a lot more. I’ve got about 13 years of photos in my Adobe Lightroom Classic catalog. But First, A Lesson I Learned The Hard Way It’s not just noise reduction that’s been AI-enabled photographers will find the recent update to reduce their editing time significantly when working on portraits. At least Adobe has realized the need to integrate more AI features immediately and has done so in its latest update of Lightroom. We've also tested the file in several other photo-editing programs like Photoshop and Lightroom Classic and none had any issues opening up the file.Adobe and Capture One were left behind with software like Topaz DeNoise, On1 NoNoise, and DXO PureRAW, making great strides with clean, effective, and realistic-looking noise reduction. If you reach out to them, I'd recommend you tell them that Capture One 2021 doesn't have this issue. I'd recommend you reach out to them and ask them. ![]() I don't know if this can be some issue with v2022 reading the metadata but Capture One Support should be able to determine that. It's only Capture One 2022 having this issue. Interestingly, Capture One 2021 has no issues opening up the same DNG and it doesn't open up black in there. We've tested the DNG processed from DeNoise AI out of the ORF image in both Capture One 2022 & Capture One 2021. After several tests we run, it seems like the conflict is on Capture One side. I contacted Topaz Labs and after a few days and a few back and forth emails this is what they told me: "Hi Andres, ![]() I use capture one as my main raw editor, I am sending the image to Denoise AI but when I get it back to capture one it is just an under exposed black image. I am having problems when I use capture one and Topaz Denoise. ![]()
0 Comments
Leave a Reply. |