AW3423DWF, ETA on EOTF firmware fix?

What does "I'm still optimistic" mean? a few messages earlier you wrote that the problem was fixed, but the other things that this entailed need to be fixed". ..

Just to clear on this: I never claimed it might not be fixable. I stated there's a possibility this cannot be fixed with a firmware update.

Reason being is we don't know the true cause of the EOTF issue. The assumption is that it's a calibration issue that can be easily fixed with an updated calibration profile. 

Kinda wish dell would give us a bit more info of what going on, instead of leaving us in the dark.

I just bought the DWF today.  I truly hope to see a firm confirmation of a firmware fix for this HDR1000 issue.   I assume that I will love HDR 400 true black... but yes, this is an expensive monitor and HDR1000 should be working well as it does on the DW.  If this isn't fixable with firmware that should really be disclosed.  If it is fixable then some light should be shed on the actual effort/time required to remedy this issue.

Looking forward to hopefully 100% loving the DWF...  and getting a "info rich" update soon.

The last update I have is still the same and with the end of May being the last ETA I heard (this is no different from before and unfortunately I do not have any new updates since that post I made). The team is fully aware of the issue and has been continuing to work on this.  

The reason for the optimistic line is that in my personal experience sometimes a fix can change due to unforeseen circumstances, ie if the Firmware is not performing up to spec, but again I have not heard this. For example, if this was on the DW version it would only be in the form of a hardware revision because that monitor cannot be updated by the end-user with Firmware, but this one can be.

Again, when  I hear something back that's new I will update the thread, I just wanted to reassure everyone we haven't forgot about this. 

Yes, I will share updates as I get them. 

Yes, I do agree, faster updates would be nice, but until I have something more to share I don't want to give false statements. 

BradL- Thank you for confirming the team is fully aware of the issue and is working on a fix.

The end of May is approaching- but I'm still not getting my hopes up for a release soon. I'll be pleasantly surprised if it's out by the end of June. So anytime before then and I'll be happy!

Even if it seems like a lack of transparency to some in this thread, personally, I appreciate you holding out on posting until you get accurate information.

I agree.  Thanks to BradL for being reliable to status us that the issue is still being worked and not completely off of Dell's radar.

I'm fine waiting a bit longer.  What I do want to know is if the Dell team can confirm that this is fixable in firmware or if that is still a "not sure".  Getting the actual fix implemented timely would be great!  However, knowing if the Dell team is still not 100% sure that this is fixable in firmware would be something that we would all appreciate knowing. 

I.e. Is it just a matter of "when" or is there a technical reason that it is still a matter of "if".

I doubt they will divulge that information. If they knew it couldn't be fixed with firmware updates, and admitting that, would open the floodgates to tons of people initiating returns - me included lol

Definitely, if they were confident that this was fixable they would have address it, but Im getting the feeling that their not sure. What do guys think? Am i overreacting?

Probably. 

Going by what the dell rep/mod said, I'm optimistic that it'll get fixed. 

But... and I think it deserves to be stressed upon - who knows until it's officially addressed/fixed by dell. The hardware can do it, it's just a EOTF curve. I'm hardly knowledgeable on the subject of OLED inner-workings and hardware/software, so it's just my feeling.

Guess we'll find out by the end of the month either way. 

I just got an update and early June is the new ETA.

I also asked if firmware was still the plan and so far it is and what is being tested. I will update this thread as I get more updates. 

Thank you for the update, it's much appreciated.