adding the processed image also to the LR collection from which DxO PL had been called (if so) stacking the processed image 'above' the source image (and not vice-versa) I didn't like this from the beginning, so I removed this part, along with some other 'enhancements' like Unlike PureRaw, PhotoLab comes with uncompiled Lua code for the export/import plugins, so you can easily spot function(context)ĭxoCollection = catalog:createCollectionSet('DxO PhotoLab', nil, true) PhotoLab shows the same behavior imported files are being imported under a collection set 'DxO PhotoLab', with an individual collection for every export to DXO / import to LR. This statement by DxO is definitely nonsense.

This is entirely controlled by Lightroom.

Under normal circumstances, the processed file is displayed with the original file in the Lightroom database.įirst, there is no code for setting in PureRAW that would cause Lightroom to place its processed photos into a collection. For these instances, we have been advising the affected customers to please contact Adobe support directly to find out how to change this import behavior. First, there is no code for setting in PureRAW that would cause Lightroom to place its processed photos into a collection. This does not happen on all systems, but some specific systems are affected this way. We have seen a few reports like yours on how files processed in DxO PureRAW are imported into the Adobe Lightroom database. No newbie.Īfter contacting DXO this was their response FYI the OP, me, has been using Lightroom from Version 1.0.

Here in lies the probably or at least one of them. However, Lightroom Classic ignores this file and instead opens the Collections file in a new window. Secondly, the file is also imported to the Original folder and put into a DXO folder. First of all the DXO plug-in does import the file to a Collections titled DXO.

Dxo pure