Imported .dng looks different (and terrible) when zoomed to 100%
I exported a .dng file from DxO Photolab 4 and opened it in C1 15.3. When the full image is viewed it looks OK, but when I zoom in the color gets sucked out and it gets very soft looking. It starts getting worse at 33% and is way off at 100%. I believe the problem stems from C1 since the preview gets worse as I zoom in, although I guess it could be a problem with the .dng file. I also exported a .jpg from Photolab and it looks like it should. Any idea what is going on and if there is a setting or something I can change so C1 shows the image correctly?
-
Capture One says that dng files other than native ones could be not correctly supported. Did you try exporting a TIFF from DxO and opening it in Capture One ?
0 -
> Ric Cohn: ...a .dng file from DxO Photolab
Depending on the application, DNG, DNG, DNG,...,DNG are all different :-)
Use the kind of DNG stated as acceptable in C1 documentation!
I do not know why so many photographers wish to believe that DNG=DNG=DNG...=DNG to all applications. It would be nice, but it is absolutely not true.
0 -
Robert and OddS thank you for your replies. However, the DNGs used to work fine. I use DxO occasionally for noise reduction. I also use the DNGs from Helicon Focus so I have used DNGs successfully with C1 that are not camera DNGs (which I've never used). I'm hoping someone who uses either DxO Photolab or DxO PureRAW can either confirm that DNGs are no longer working in C1 or tell me if I am doing something wrong. I also sent this question to C1 support but I don't know how long it will take for an answer and I am hoping a fellow user may have more knowledge about this specific problem than I do. Finally, the fact that the preview changes with magnification seems likely to be a C1 problem. Perhaps related to my M1 Mac since I experienced some preview and output issues related to Apple M1 chip compatibility before C1 updates fixed these issues.
0 -
Perhaps DxO is generating DNGs with a small embedded preview jpeg.
0 -
For the benefit of any DxO users who have this problem and find this thread, I just heard back from C1 support and they confirmed that OS 12.5 Monterey caused this bug. They say it will be fixed in the next C1 update. I should have taken the supported OS versions seriously.
0
Post is closed for comments.
Comments
5 comments