18-10-2018 09:44 AM
Hello,
I put the beta firmware send by David B (German moderator on Samsung Community) and all it's good, better motion, better local dimming ... but the black are completly crushed in HDR !
A friend of mine and me experiment the same bug, the first 7.5% of black is not visible on the HDR black clipping pattern (no matter which setting you use in Movie mode) and the dark scene in movie are completly "unwatchable".
Can you correct that for the futur official firmware 116x ?
Best Regards.
18-10-2018 10:30 AM
Hi @AlexScan!
In which country are you based? I was under the impression that the beta firmware was only released to a selection of TV owners in Germany to test a fix for the picture juddering/motion that a few of their Community users had experienced. Did you get the firmware directly from @DavidB?
18-10-2018 10:45 AM
He did. I asked tech support: this beta firmware should run with European TVs, we don't have any complains like his.
18-10-2018 12:25 PM
Obviously @DavidB sought the best advice. Nonetheless @AlexScan has some issues, even if not a common experience. @AlexScan have you experimented with settings to see if this makes any difference?
I do not work for Samsung or make Samsung Products but provide independent advice and valuable contributions.
18-10-2018 01:50 PM - last edited 18-10-2018 01:51 PM
I do not want to hurt David B, I asked him for the firmware, this is my fault.
Obviously this is a good step forward for the Q9, especially on motion, but the HDR bug makes me no longer able to watch movies in this format.
Actually only one friend of the HDfever forum put the firmware, same problem.
I specify that it is only on the HDMI input that this occurs, none settings un-crush blacks (i try everythings).
18-10-2018 02:01 PM
@AlexScan: No worries. I’m sure David’s cool.
Is your TV a UK model? I’m just thinking of the best place(s) for the feedback you’ve given to be directed.
18-10-2018 02:20 PM
18-10-2018 02:54 PM - last edited 18-10-2018 02:55 PM
18-10-2018 03:02 PM
26-10-2018 08:46 AM
Any new for new firmware for correcting the bug ?