When DxO manage to import export in xmp i still be using this for anything else then rawfiles.įinaly, it’s better to use small effective applications for parts of your workflow then a one do it all on It’s own way so you bound to that system. Yes at the cost of poking in my property by Adobe. I use the “freeware” adobe Bridge to tag and edit iptc. So imho before exporting in xmp of keywords and such, rawfiles and there iptc info are vulnerable when using DxO’s keyword editor. Home users will use that and more demanding users will choose apps like photomechanic. If DxO builds a simple but effective editing field for iptc, xmp which export alway’s this to the external sidecar that will be enough if added to the allready present DAM facilities. Not to mention the springoff’s as tiff.s, jpegs, dng’s. So a non depending DAM system using common used file types like xmp are vital for your concistency in organising your growing rawfilecstock. Rawfiles are long term files and wile applications change over the years, the iptc and keywords are stationairy mosly on your raw archive. It’s no use to change things which are stuck in one program. The point we need to pass is ending the dependence on the DataBase for keywords.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |