Has anyone with a similar configuration the same experiences after the update to 9.6 build 43?
My configuration: macOS Tahoe 26.3.1, MacBook Pro M3 Max, 64 GB memory
Fuji XT-3 RAW files.
After the update to PL 9.6, I receive the error “Correction failed on the Execute stage” when I first open the last edited RAW in the photo.
The preview of the corrections doesn’t work at all anymore; the wheel spins forever, only the preview from the RAW is displayed.
Consequently, when switching to the local settings or any other function besides manual handling, the photo is no longer displayed.
PL can only be closed by “Force Quit.”
I have already tried a complete reinstallation, including deleting all settings and the database, all without success. Unfortunately, deleting the DOP files in the folder does not help either.
The ticket goes of course also to support. I am just curious if this is an individual problem.
I have come a bit closer to the cause of my problem. During the update to 9.6, the value for the NoiseRemovalMethod in the .dop files is not updated; that seems to be a bug. When I import the RAW files fresh, meaning through a new folder without .dop files, then 9.6 works without errors.
A workaround would be to replace the value manually, but that doesn’t work either. I have to wait for an update from Photolab.
Can you please share the details?
BTW, hard to believe DxO feedback was delivered so fast
Which assumptions?
I’m on Windows, using Bayer sensor, so it’s a different environment. The NoiseRemovalMethod is updated as expected. For example, if PL9.5 dop file has “DeepRaw2RGBv4” (XD2s) then PL9.6 uses XD3 for NR and doesn’t change the setting to “DeepRaw2RGB7” (XD3) until NR settings are changed in UI (forget the glory details for now). Maybe you expect something else? It doesn’t look likely it has anything to do with your main problem, but some bugs give strange side-effects.
This is a signal for a serious problem which is usually a result of some OS resource shortage (e.g. physical/virtual memory) and/or a bug (not neccesarily in DxO code, often it’s Microsoft, NVIDIA, AMD, Intel, Apple, …). Check your OS logs, RAM and swap usage, NPU/GPU resources, and PhotoLab logs first.
DxO Support responded within 24 hours, but I had already included the diagnostic report and the test results I mentioned above.
My assumption was that the .dop files weren’t updated correctly during the update to 9.6. Whether this was related to the “DeepRaw2RGB7” value was just a guess, but it’s likely a combination of various factors.
Here is the response from DxO Support (translated from german):
"Based on your findings, your conclusion is absolutely correct. Since the same Fuji X-T3 RAW files work correctly in PhotoLab 9.6 when placed in a new folder without .dop files, this clearly indicates that the problem is not caused by the RAW files themselves. Instead, the behavior points to an issue related to pre-existing correction data (stored in .dop files) from earlier PhotoLab versions that is being used in version 9.6.
The diagnostic data also supports this and shows an error during the preview or correction process, which matches the symptoms you described (endless loading, preview not updating, application freezing).
Currently, the issue appears to be triggered when PhotoLab 9.6 attempts to interpret or migrate older .dop data, particularly in combination with certain corrections.
We will ensure that this is noted by our development team for further investigation.
"
It probably wasn’t due to the OS resources; 64 GB of RAM on a MacBook Pro M3 Max should actually be sufficient.
So it looks like DxO bug specific to X-Trans after 9.5–>9.6 update(?).
Maybe they already knew about this issue, probably many people were affected, so the response was fast. I don’t see this problem with Bayer (Nikon Z8)/Win, btw.
