AW3423DWF, ETA on EOTF firmware fix?

Hi, they actually did

here is the correct video https://www.youtube.com/watch?v=jTvqGFBPIw4

and yes, it proves Dell fixed it...So Happy!!

BradL and Nathalia- THANK YOU! You two, and the rest of the Dell team, have set a fantastic example for the rest of the industry. The follow through on support for this issue has been amazing. I'm incredibly satisfied with the end result. I hope this results in other OE's taking note, and taking time to properly finish and polish their products, even if it is with post launch support.

I cannot imagine if this had been an issue with the DW and firmware was not user-upgradeable. Being able to update the firmware as the end user has saved the day here! Regardless, I'm impressed with the result, and overall has made me much more satisfied with my expensive purchase.

Again, thank you, and thank you Dell team as a whole! You engineers rock!

My only recommendation is unplugging any secondary monitors you may have plugged in. I unplugged my secondary monitor and was able to update just fine.

Is there a chance that the  HDR performance of the aw3423dwf with AMD cards is going to be on par with Nvidia cards with a future Firmware Update?

I find it kind of puzzling that Nvidia has the advantage here as this is a freesync model.  The channel Monitors unboxed mentioned this could need some tuning.

If you're willing to use CRU, I've read that you can disable the AMD Freesync Premium Pro HDR Pipeline and end up with the perfect Nvidia curve.

From the comment on Youtube (and I've seen the same thing on Reddit, but it's on strike at the moment): "Delete the Freesync Block (Selecting the AW3423DWF, Check in Extension blocks, CTA-861..., FreeSync range )(should be 19bytes in size) add a new Freesync block with the Range of 48-165 (this now has only 7bytes). Restart using CRU provided restart64 file and you will now see that the OSD shows you HDR10+ and the Console Mode and Source Tonemapping is avaibale"

I can't test it as I'm running on Nvidia, but I'm confident that if you're seeing HDR10+ in the OSD, it means you should get your the same EOTF as Nvidia users.

Well, a workaround might be a temporary solution but a official fix would be much appreciated. 

I tried this but the new block has 9 bytes for me and it seems that nothing has changed.

So, in it's current state is the TrueBlack400 Mode still more accurate than the peak1000 Mode for AMD users?

MU mentioned its not completely fixed for AMD but i've seen people on reddit saying that its fixed apparently. I would say maybe in numbers it's not as accurate for amd but probably visually you wont tell the difference since owners on amd say its fixed?

Sorun, MSI'ın MEG 342C'si ve hatta bu panelin DW Gsync sürümü gibi aynı OLED paneline sahip rakip monitörlerin HDR 1000 EOTF ile aynı sorunu yaşamamasıdır. Bu özel modelin, özellikle de yükseltilebilir donanım yazılımıyla düzeltilememesi için hiçbir neden olmamalıdır.

The problem is that competing monitors with the same OLED panel, such as MSI's MEG 342C or even the DW G-Sync version of that panel, do not experience the same issue with HDR 1000 EOTF. There should be no reason why this particular model can't be fixed, especially with upgradeable firmware.

I am in the process of getting mine replaced under warranty, due to burn in. Once I get the new one I can see if anything has changed with the firmware.

I am assuming the latest firmware is available under the support down load section, but it's equally possible it's not.

Or it could be a new hardware revision that might address EOTF issues.

I should know next week.

Hello,

For some time now, every time the display changes the HDR profile it disconnects and reconnects again, it takes 2 seconds and moves all the windows around.

I remember some time ago this would not happen, the coclors would clearly change and the message of the profile would appear on the corner of the screen and thats it.

Is this casued by an update?

Is there a way to revert it back to how it was working before?

The way it is working now its impossible to multitask, as as soon as i go from blender to discord for example, bam 2 seconds and everything moved to go to discord and bam 2 more seconds and everything moving again to go back to blender.

Its unusable and im seriously considering forgoing HDR entirely.

Thanks.

@LucasVT​ As far as I know it has always taken a few seconds to switch from HDR to SDR and vice versa?