LRC aplicando ajuste sozinho

Forum|Forum|4 months ago
January 16, 2026
2 replies
125 views

Está acontecendo algo muito chato já faz um tempo, toda vez que eu salvo uma foto no PS que ela volta para o LRC como PSD o LRC aplica um ajuste nela, se eu não ficar atento eu envio fotos ruins para os meus clientes. Daí, após editar todas as fotos eu tenho que sair excluindo esse ajuste que foi colocado no PSD que voltou do PS para o LRC, um verdadeiro atraso para o meu fluxo de trabalho, como resolver isso?

Versão do LRC 15.1 e do PS 27.2.0

macOS

A

AxelMatt

Community Expert

When the 'link' between Lightroom Classic and Photoshop has issues, the first step is to try this:

Use the Adobe Creative Cloud Application to uninstall Photoshop. When asked, keep preferences! After this reinstall Photoshop again.

If this doesn't help the nest step is to reinstall both apps Lightroom and Photoshop. Please follow the steps below:

Open the Adobe Creative Cloud Desktop Client and uninstall both Photoshop and Lightroom Classic. When asked, keep preferences!
Install Photoshop first and then Lightroom Classic. The right order is very important here!

If this doesn't help try the reinstallation with removing the preferences also.

My System: Intel i7-8700K - 64GB RAM - NVidia Geforce RTX 3060 - Windows 11 Pro 25H2 -- LR-Classic 15 - Photoshop 27 - Nik Collection 9 - PureRAW 6 - Topaz Photo AI

James Jacó FotografiaAuthor

Participant

Good afternoon, thank you for your help. This has been done several times by me and Adobe support, including remote support. We were on hold with Adobe practically all day yesterday, and it didn't solve the problem... Initially, it would seem "easy" to delete the erroneously applied adjustment on the PSD file, but it's counterproductive. A delay, if replicated across thousands of files from an event for example, having to check and delete each PSD file that returns to the LRC, would require checking and deleting it from each one. Adobe said they would get back to me on Monday; hopefully, it will be resolved... I think it's something at the programming and program level, and the developers will have to correct it via an update. If anyone has experienced this and knows a solution, I would be very happy if you could share it with me. Thank you again.