Hi guys thanks for the response. Apparently my general knack for coming across strange problems that no one else experiences is holding true here. I have kind of a long strange story for you now.
My post-process procedure involves doing culling and processing on my primary SSD drive, and drive-space being a concern I archive things over to my other regular hard drives and delete from the SSD as I get through it. The past week I’ve been doing 100 images or so a day and this Lens Sharpness strangeness would occur 5-10 times a day. I had just compensated with extra microcontrast and less noise reduction and moved on. Like I said, rebooting and deleting/reinitializing the database hadn’t changed anything before.
I remembered a couple particular raw images where it had occurred, and went to load them with DXO from my archive on the standard harddrive. To my bafflement, I just spent an hour paging through 1000 images with a correction profile applied that only would apply 100% LensSharpness to test, and not a single one of them failed to apply it.
Wondering if there’s a problem with my SSD (I’ve never had a single problem with it as far as I can tell), I copied 1000 back to the SSD from the archive drive, deleted the DXO database file under AppData, indexed the folder and applied the same 100% lens sharpness correction profile, and none of them presented the problem either.
I’m kind of new to DXO, the past month has been my first fullon production project with it, and even given this strange occurence it’s an amazing program and I’ll totally be using it anyway, probably upgrading to PL3 next paycheck. Nothing else has been an issue. I’m sorry I can’t be more help with making sense of this but I thought this might be interesting data nonetheless for you.
I’ll upload 2 files anyhow: DSC_0072 and its DOP with my normal baseline custom correction profile applied (the one I used before) will be the one where the filter failed to apply, and DSC_0066 is taken a few minutes earlier on the same day/camera/lens/settings/DXO settings, but which did successfully apply lenssharpness before. They both work now for me.
More info if it’s helpful: I’m running a Windows 7 SP1 updated OS, on an AMD Ryzen 5 1500X processor and MSI RX 570 GPU, and my SSD is an Intel NVMe SSDPEKKW51 512GB. I religiously update all my software/drivers/firmware. The camera in this case is a Nikon D5500 with a Nikkor 10-24mm attached. Camera/lens dxo modules are installed and working.
The only other thing I can think of is that I do my culling process with Lightroom, and these files were scanned into a temporary Lightroom database before I worked on them in DXO. I never ran any save or export commands from it, and as far as I know they shouldn’t have been affected in any way, I just use Lightroom for its quick comparison functions, but maybe Lightroom did do something to these SSD files that made them different from my archived untouched raw files in some subtle way? Some occasional hiccup it might do to corrupt a file in some bizarre fashion?
When you guys test the program I wonder if you do it on SSDs? I have the program and all working files on one like I said. It does also very occasionally seem like if I drink too much coffee and “get ahead” of the program as it’s trying to catch up, it’ll get stuck and the preview will blur, but like Mark said, going back to another folder then back to the working screen fixes that.
Thanks again and sorry for this long and strange report!