Just out of curiosity, I am wondering about cameras that PL doesn’t currently support that might be surprising, if any. I trialed the software and never really considered that it might not support my camera (it does), but realized after seeing the non-support of, I thought, “universal” DNG RAW file format cameras of the monochrome nature that I could potentially have been surprised that it didn’t.
So… anyone have a list, or care to note some off the top of your head?
P.S. I queried Google’s Ai search on this to see if it would/could source a list. I figured it would attempt to compile a list on the fly, and was right. OMG! Apparently, Fujifilm X-Trans sensor cameras aren’t supported! Google is fast becoming worse than useless if not already.
mwsilvers
(Mark - New Jersey, USA, Win10, RTX 4060, PL9, FP8, VP5, Nikon Zf )
3
Actually, the Google search you performed may have been incomplete but was partially correct. if you queried using the AI mode, it would have indicated that support of exportprocessing for Fuji x-trans sensors is only supported by the Elite edition.
This is what the AI mode had to say. “Fujifilm X-Trans sensors (Essential Edition): While supported, X-Trans raw processing requires DxO’s DeepPRIME AI, which is an exclusive feature of the Elite Edition.”
And, this is what DxO had to say.
”*Support for Fuji X-Trans sensors requires the use of DeepPRIME technology available only in the Elite edition.”
Oh, it did… after I told it its initial response was not correct. It then did the apology thing and told me just what you said it would say. First response was simply that X-Trans wasn’t supported. I didn’t specifically call the Ai mode, but it is what popped up, as usual, with my query. I actually was planning to just do a regular search, but decided to see what the Ai bot would say.
Thank you for the links. Of course, I know a list of supported cameras exists. I was just curious to see any cameras that one might be surprised to find aren’t supported. Looking at the list of supported cameras makes it hard to imagine anything but the very latest models not being supported.
Sigh. The DNG issue again. Please search the forum (there are way more than the links Wolfgang supplied).
DxO have always been very clear on DNG support. Apart from some changes to DNG export recently (PL9), I don’t think their position has changed in a lot of years.
Sigh. A re-reading of the original post should dispel the myth that this thread is about DNG support. It was a simple question out of curiosity about any particular camera that might not be supported, for whatever reason. I have read enough and already understand the DNG landscape from DxO’s perspective, which is why I wasn’t asking about it.
I am having trouble reading that as anything but disappointment that it doesn’t support “universal” DNGs. Regardless of the mention of monochrome cameras.
DxO supports cameras and lenses. The one exception to this is an Adobe-converted DNG (from manufacturer RAW).
you were looking for “List of notable cameras that PhotoLab does NOT support” , so here we go … and no, not every monochrome camera has DNG as a camera’s raw format
What annoys me more is lenses that are supported and bodies that are supported individually in DXO but that those lenses that work with those bodies happily in the real world do not have the combination supported in DXO.
My Nikon full frame cameras will happily work with DX lenses and auto crop the image but DXO do not support those combinations. Nikon has a decent DX 10-20mm lens but no FX equivalent. In DXO I have to manually edit the barrel distortion which doesn’t always work and I find trying to work with viewpoint 5 even harder for such images. But the worst part is because that lens is not supported for use on an FX series body the options for other parts of the program such as noise reduction is more limited.
See… that’s good to know and highlight. I suspect this catches some people out. What would completely make sense is for PL to let users choose whatever lens there is a profile available for, because I use profiles that PL offered to download for me, but were not actually the lens I used. Those profiles absolutely can work! Why not let us use them??? They do wonderfully on my lenses that aren’t actually a match.
The DNG support appears primarily to be a way to motivate users to update. E.g. changing camera type in EXIF data (I sometimes use a hex editor) enables basic support for newer cameras and/or compatibility for non-current versions of DXO. Ultimately this creates a sufficient “pay wall” for users to upgrade to avoid the hassle.
On of my use cases was AFAIR when Leica M10 was supported and M10P was not (would not open, different EXIF camera model).
DXO might have instead opted to support ‘unknown’ cameras and maybe show a warning about incomplete support. The current pay wall is clearly an intentional design choice.
DNG1files created by Adobe Lightroom, Camera Raw and DNG Converter, excluding compressed lossy DNG format, DNG files output by merge2 HDR, Panorama, or Panorama HDR from Lightroom or Camera Raw.
Apple ProRAW3 files taken with iPhone cameras (from iPhone 12 and onwards) and the native Apple Camera app.
8 and 16-bit TIFF files.
JPEG files.
HEIF/HEIC files.
JPEG and PNG files for watermark graphics, imported using the Watermark palette.
do not be that naive … I have no issues with , for example, linear DNG output from iridient *-transformers in DxO v9.10 ( just tested again ) … and I do not have any issues even to open a fully synthetic DNG for as long as I supply enough DNG tags into it to make it look like it is from the real camera - it is the beauty of DNG format as a data exchange container - you can play w/ it