Hi guys! I was looking to get a new TV. (my Sony XBR55X805E died last year). Since I have a special discount in Samsung products, this tv seem’d like a good deal. However looking for reviews, I found this video posted just days ago: https://www.youtube.com/watch?v=ZVUhmkTzMPc (in spanish)
One of the problems the user mentions it’s the “squares” he gets in picture from time to time. He states that almos 6/10 videos has that problem in HDR with black sections. It happens even with PS5.
He states that when he got the tv, 5 months ago, the problem wasnt present or wasnt as notorious.
I was wondering if you have experienced this problem, if you think it would be fixable with futures updates or if it’s something that should ask for a replacement.
Thank you for the amazing job you do!
Big hug from Argentina.
Ofesad.
We’ve purchased the product and are waiting for it to arrive in our lab.
Can you test for the ability to send multiple keys per USB report? The lemokey L3 is equipped with the same MCU and was unable to perform this feature
Early access to our full test results is now available for Insiders! Become an insider to check it out here.
I bought the V5 Max for a friend but remapped some of the keys so that he would have access to a PrintScreen key. After remapping the keys with the official software (following their guide here: https://www.keychron.com/blogs/news/how-to-use-launcher-to-program-your-keyboard ) the keyboard’s effective update rate feels to be 125hz. Resetting the firmware (holding Fn + J + Z for 4 seconds) doesn’t help until you unplug and replug the keyboard in. Can someone from the RTings team test this to confirm quantitative data on polling rate and latency after remapping keys and then test again resetting the firmware thereafter?
I bought the V5 Max for a friend but remapped some of the keys so that he would have access to a PrintScreen key. After remapping the keys with the official software (following their guide here: https://www.keychron.com/blogs/news/how-to-use-launcher-to-program-your-keyboard ) the keyboard’s effective update rate feels to be 125hz. Resetting the firmware (holding Fn + J + Z for 4 seconds) doesn’t help until you unplug and replug the keyboard in. Can someone from the RTings team test this to confirm quantitative data on polling rate and latency after remapping keys and then test again resetting the firmware thereafter?
Hey!
Very strange issue. I went to grab the keyboard myself quickly and did a sanity check and wasn’t able to feel any difference at all. Sometimes these sorts of issues can be related to firmware, though I expect we’re both sitting at the latest version. I’d recommend double checking it for now. In the meantime, I’ll make an update for this discussion so that we can revisit it in the future if you’re still experiencing this and see if we can get some data as to whether it’s affected or not.
This product has been merged with Keychron V5 Max Custom Wireless Mechanical Gaming Keyb. Follow the discussion here.
Thiss iss how it lookss like to type in a Keeychron v1 max wwirrelesss. DDouble typing keyss. The support sent me a 35mss and 50ms firmwwwaree. Both made some keyss not typable at all. WWorsst eexperience of my computeer life.
This product has been merged with Keychron V6 Max Wireless Custom Mechanical Keyboard, 2. Follow the discussion here.
Hello, the Keychron V1 Max and probably the entire V Max lineup has a new software at https://launcher.keychron.com/, where you can adjust many things like on other keyboards. I would be happy if the keyboard could be tested with this new firmware and the appropriate settings for office and gaming.
Hello, the Keychron V1 Max and probably the entire V Max lineup has a new software at https://launcher.keychron.com/, where you can adjust many things like on other keyboards. I would be happy if the keyboard could be tested with this new firmware and the appropriate settings for office and gaming.
Hey Quarters5912! Thank you for the notification about the firmware update! I tried with the previous firmware to see if the results were consistent for the latency tests with what we currently have in the review and they were. I then did the update retested the board. To my surprise, the latency results almost doubled to what we currently have. I’m going to play with the settings a bit more to see if there’s an optimal settings and provide you with that information this coming week! Thank you again and if ever you have any questions don’t hesitate! 😄
Hey Quarters5912! Thank you for the notification about the firmware update! I tried with the previous firmware to see if the results were consistent for the latency tests with what we currently have in the review and they were. I then did the update retested the board. To my surprise, the latency results almost doubled to what we currently have. I’m going to play with the settings a bit more to see if there’s an optimal settings and provide you with that information this coming week! Thank you again and if ever you have any questions don’t hesitate! 😄
Thank you very much, I look forward to the results.
Thank you very much, I look forward to the results.
Hey Quarters5912!
I went ahead and tried different settings.
The recommended one (Eager Per Key) gives results similar to what we have in the review. By default, it’s set to 50ms but provides good stability and lowers the chances of double pressing a key.
Leaving it at 50ms or even putting it at 0ms doesn’t seem to have a big impact on the performance itself.
The only drawback is that if you put it at 0ms, even though seems to help a bit with the latency (was about 0.2ms faster) you might be at risk of having double key presses. I personally didn’t encounter it when I was experimenting it for the past few days but it’s still a plausible scenario.
The other settings such as Defer Per Key and Defer Global are are quite useful as they can help when you have chatter issues since you can set a debounce time individually for each key. These settings affects your press and release which is why I had latency results quite high.
In short, Eager Per Key is the way to go. It lets you set your own debounce in a comfortable way. 50 is by default but you can always put it at 25 or 30. The closer to 0 the higher chances of double key registering. Thank you for the question! It was fun trying that out haha. Have a great week!😄
I don’t understand why the latency is so low, from 50 ms to 0 ms, even though it’s a big jump. I sometimes have problems with double clicks, and since I like to play video games, I don’t want to have high latency, so thank you very much. I’ve now set it to 50 ms. If the difference is so small, I’d rather not have double clicks than be 0.2 ms faster. I wish you a great week too!