prestigevur.blogg.se

If we had additional information, we would be happy to share it.

But, Adobe appears to be the company that needs to provide some light on how to prevent this from happening. Since this is not happening to all customers, we believe that this is related to a configuration setting. Either by updating their code in Lightroom, or providing Lightroom configuration information to their customers. The issue needs to be resolved by Adobe in some way. The other customers who have experienced this problem have contacted Adobe, but to our knowledge, Adobe has not replied back to them. However, because we do not have access to the Lightroom code, we have not been able to determine the root cause of the issue. We have tried to identify why this is happening. Lightroom is in total control of the import process from all third-party programs, including PhotoLab. When PhotoLab exports a file to another program, in this case Lightroom, PhotoLab only makes a call to the operating system to activate Lightroom to accept the file transferred to it. This is a very rare issue that we have encountered with only a small number of customers using DxO PhotoLab with Adobe Lightroom. Thank you.ĭXO says the problem is at Lightroom - here is there response: Thank you for writing. For example, when I use something in Nik, it goes back to LR and I see it as one of my library images - what am I doing wrong and how to do I fix this so it automatically is part of my visible library images after I send back from PhotoLab 4. They get back into the LR folder but I must to an import of the image in the Library module in order to see the noise reduced dng file. Lightroom and do noise reduction and then save to send back to LR.

I wrote DXO the following: I send images to DXO from.