"These images are either not supported or have already been processed..."

Hello.
Just experimenting with the trial version…quite an amazing experience so far.
I keep getting the title error “These images are either not supported or have already been processed in DxO PureRaw, or the files may be corrupted” , but only on images from a few folders in my archives, all from a specific year so far.
They do not seem to be corrupted as they open fine in all of my other editing/viewing software. They are .CR2 files, and others from the same camera and lens combo have processed just fine.
Anyone have any thoughts on what might be causing this? I’m new to DxO
Best Regards
Johnny C.

Please check if the files that don’t work are c-raw files. As of today, DxO does not support c-raw files.

@DxOStaffPO, should this maybe added to the manual? Systemvoraussetzungen

Also sRAW and mRAW are not supported either.

Looked a bit closer to the list of supported devices. The α1 is on it, but support will start in June 2021 … so I just have to wait …

I’ve been using it on cRAW for a week…is this just a new update?

However, on checking I discovered the problem files are indeed mRAW, from a brief experiment I tried with that format.

Thank you.

Thank you! mRaw is indeed the file type…I had forgotten all about it, but I experimented with it for a couple of shoots and the problem files are from that.

1 Like

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. It didn’t take me long to figure it out. Check the metadata on any of those files (such as in Bridge, or elsewhere). Under “file properties” you will see “application.” In that field you may see “Adobe…” Lightroom, Photoshop, etc. Or even the Adobe DNG converter. If you processed an image in probably ANY photo-editing application , you will receive this message and the file cannot be processed by DXOPR. As an IT professional of 35 years, I can see why DXO does this (even though I don’t like it!). 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. If another processing engine was used on the image, DXOPR would not have a clean slate to start with. I sympathize with that. However, for me, there’s two big draws for DXOPR: improved raw conversion of new images, and also rejuvination of old raw images. I’ve process many older images in ACR and wish to re-do them in a superior raw conversion tool. However, given the DXOPR approach I can’t.
As 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’ll just give a brief summary. ACR/Lightroom purport to never alter the original raw data, just embed changes in sidecars or within the image file itself. I don’t know how this process works, but why couldn’t DXOPR “simply” make a copy of the file (not changing the input!), restore the “adulturated” (I like that word in this context) file to purity in a second file, and then process this second, purified, file?

Hi TNT,
I’m a little bit confused, because I’m not able to reproduce what you wrote. Maybe you take at look at my comment to DxO Pure Raw - before or after import to Lightroom? on 2021-05-16: The DNG/RAWs which I sent with LR export functionality, or on which I saved the metadata explicitly, work very well in PureRAW. And of course, the application tag (called software in LR) is set to Adobe Lightroom…