![]() ![]() ACR/Lightroom purport to never alter the original raw data, just embed changes in sidecars or within the image file itself. However, given the DXOPR approach I can’t.Īs an IT professional, just thinking about this problem a little while, I came up with a possible solution for DXO PR programmers, but it would probably be complicated. I’ve process many older images in ACR and wish to re-do them in a superior raw conversion tool. However, for me, there’s two big draws for DXOPR: improved raw conversion of new images, and also rejuvination of old raw images. If another processing engine was used on the image, DXOPR would not have a clean slate to start with. ![]() DXOPR must (prefers) to start processing an image as an unadulterated image that hasn’t had any metadata, xmp data, whatever “corrupted” (altered) in any way. As an IT professional of 35 years, I can see why DXO does this (even though I don’t like it!). If you processed an image in probably ANY photo-editing application, you will receive this message and the file cannot be processed by DXOPR. Download the appropriate file below, and then follow these instructions: Windows. Under “file properties” you will see “application.” In that field you may see “Adobe…” Lightroom, Photoshop, etc. Check the metadata on any of those files (such as in Bridge, or elsewhere). I’m new to PureRaw and was disconcerted when “These images are either not supported or have already been processed in DxO PureRaw, or the files may be corrupted” displayed on many image files. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |