Newbie - sidecars or catalog?

No, simply not. It depends much more on what DxO PL is allowing me to do. And I can’t say “PL lets me work the way I want to” because it is the app with the need of endless “workarounds”. If I’d want to write a list “which workflow is possible with PL?” and another list “which workflow is impossible with PL?”, the first one would be rather short. I’m fine with that as l don’t need an app with dozens of different workflows of which I might use one or two at best.

Also, some of these “many different ways” turn out to lead into more necessary workarounds as keywords and sidecarts are apparently not that standardized between the various involved (and needed) additional apps. It reminds me of a restaurant where each dish is cooked in a different kitchen, all of them super specialized. Just not talking to each other the same language. If a cook is used to that way, he or she will have “workarounds” for it. But once this person gets into a less specialized kitchen with cleverly arranged cooking furniture and tools, he or she will find the workflow more fluent, easier to handle and with much less things to think of and to care about.

Modules are great to choose from. As long as they work seamingless with each other (all apps work well with the same meta-information which can be added from each app). It’s not only that each involved app has it’s own ways to interact with the others. No, each also has different update intervals and after each update I’d need to check with all participants if my “old workflow” didn’t get a dam build in the way. If I’m earning my life as beta tester, great, lots of stuff to be tested. But if I want to find my images fast and hate the inflexible structures of concrete folder hierarchies, there simply is no workflow offered by DxO suiting my needs.

When I cleant some old directories around New Year, I found also PL 2 amongst them. Can’t recall when I tried that, but have to conclude at the time it was not to my liking or even more complicated than it is today. 3 major releases later I’m happy I was able to work with RAWs my at that time RAW converter with DAM could not open. Situation has changed now. I’m curious to see DxO’s efforts in terms of asset management.

Are you addressing the OP’s question, Joachim ?


I thought so, John. You were talking about the many ways to choose to work with PL and I said a couple of ways are impossible to choose. And as the OP comes from Lightroom where you can do so much more to manage images I considered it a good idea to damp the expectations a bit. At least in this forum there are a lot of people in need to work around the “ways to work with PL”. And they do so by adding more apps - else one is nailed to the folder and file names.

My understanding is OP is asking for advice on use of sidecar/.dop files and/or PL’s database (aka catalogue, in LR parlance) … and he’s a self-declared newbie; so direct and concise would be the best response - else we’ll just confuse him.


On the subject of PL sidecars, why is the .dop sidecar syntax including the original file extension (e.g.: .raw)?


  • image1.raw
  • image1.jpg
  • image1.xmp
  • image1.raw.dop

When the last bullet should be image1.dop, excluding the ‘.raw’ part?
This seems to violate the definition of a sidecar.
Some rules I wanted to set up failed because of this.

Anyone know the rationale for this?
Or a setting to change it?

You may choose to export a DNG or TIFF file first and continue editing these files requiring one DOP for the RAW file and a different DOP file for the exported DNG or TIFF.

This helps to make sure that the sidecar belongs to the right file.

  • file123.raw / file123.raw.dop
  • file123.jpg / file123.jpg.dop
  • etc.
1 Like

I see, thank you!
I had expected only edits for raw files to be saved in a sidecar.
And you generate your jpg, tiffs, etc. from the single raw file.

If I set my camera to record both RAW and JPEG files, I get two files with the same name, but with different extensions. I can edit both files differently and then, the .dop sidecars need to be different - and relate to the files thy belong to. And that’s why it makes sense to include the extension.