Nope, that absolutely won’t work. Not with LR, not with anything else that is not darktable.
The conversion (not counting the standard XMP tags like rating, etc) is one way only.
What do you exactly mean? Can darkatable for Windows read an XMP file as shown in the manual (see above)?
I feel like this is a severely off-topic. Perhaps you should start a new thread, in a proper category.
Not counting the standard XMP tags like rating, subject, keywords, etc, which should just work;
darktable should be able to read lr development steps from xmp’s;
darktable will not be able to write lr development steps into xmp’s;
lr obviously will not be able to read darktable development steps from xmp’s.
Do we have a chance to use Fast Raw Viewer and DTfW in the same streamlined workflow and re-use the XMP file after FRV? There was a discussion a year ago or so, probably stopped.
Other ways of how do not do same things twice?
Just to update the status.
Edits made in fast raw viewer will not be read by darktable, except for possibly star ratings, keywords, and other very common metadata fields. Things like exposure adjustments, curves, and other editing tools will not carry over.
What do you miss in dt what you get in frv?
Well, fast culling, raw histo accuracy, first corrections … in fact, whatever I did in FRV and saved in XMP can not be exported to DTfW. From the other hand, it can be shared with LR.
I think the idea is clear: to start the next step in the workflow exactly from the previous step results.
I am almost sure that it is doable for you to read the XMP file created in FRV. As of today, the FRV results can be exported (fully or partially) to LR and RPP (e.g. exposure, WB…).
The point is how to do the same to/from DTfW. Can save a lot of time for FRV users.
More info on FRV’s metadata compatibility can be found here: https://www.fastrawviewer.com/usermanual14/xmp-metadata. Looks like it gets along with Adobe, CaptureOne and Raw Photo Processor. If I remember correctly, FRV is made by the folks from LibRaw.
@hobo Have you tried asking the devs of FRV? If you paid for it, they might listen to your request…
Did you actually try that? If none of those settings are taken over it might help to file a bug report against darktable and add an XMP file with all those settings used.
The point is how to do the same to/from DTfW. Can save a lot of time for FRV users.
Please don’t ever call darktable DTfW again. Seriously, it hurts.
1 Like
Yes, FRV part - as of today - is Adobe-based, published and can be re-used. RPP needs it own metadata format support, this is done. If I am not wrong, the FRV guys can do more from their side if the DTfW XMP-related details will be shared.
Can I somehow find them? Who knows?
You know better!
Darktable for Windows is a bit longer to write out, you see. 
But not an old man 
1 Like
After all, DTfW is a funny single-click easy to use tool for your photos to share and publish, well, with a single click. More easy to use presets will be added in the near future. Follow DTfW on FaceBook!
A single-click easy to use tool (whatever it means) always sounds great! Many thanks in advance!
Just do not forget to find this magic button to click on and immeditately make my poor Raw files absolutely perfect.
Can you please be more specific about XMP? I am wondering if I can better use darktable together with what I have already collected.
I was actually only teasing @houz, thinking about not-so-old discussions about making an official darktable for Windows. Now there it is, unofficially, available. Besides, quite advanced presets can be made as starting points for different camera-lens-circumstances combinations. I wonder, what will happen, this tool is better than many commercial programs.
2 Likes
I’ve been at the hairdresser this morning. What I saw on the floor indicated that I am old indeed … 
Be grateful you still have a need for a hairdresser!
2 Likes
We all can probably save some time if you can share more about XMP in darktable (or provide with the link if available). Then I will prepare a couple of test files in FRV to see how it will be processed. Not sure that I can call it a bug - if something is simply not supported due to any good reason.