@xelrojo44x_mlbts said in 120hz online:
@tvsectog_xbl said in 120hz online:
Also, controller button push to the console, the console to process it and then send it to the monitor/TV telling it what to display is additional input lag, yet not usually calculated in the monitor specs. Input lag for the monitor specs is usually just from the console to the monitor. 120 can send twice the amount of information at 60, which is why the input lag lowers in half (performance numbers are not 100% linear as there is some overhead, yet close , and hold true in this case as 5.9ms is relatively close to half of 10.9ms (a 91% speedup, technically).
Thanks for the explanation!
I remember reading a tech article that even recommended using a shorter HDMI cable to help reduce input lag... noting that a 3 ft. cable can shave off milliseconds off of your input lag vs a 6 ft cable... LOL
Depends on the quality of the cable. A shorter cable that is made poorly, won't be faster than a longer cable that is built to spec. Crimps in the cable, etc, can also affect the input lag.
However, yes, in theory a shorter cable should help, as it is less distance for the electrical signal to travel. However, the difference would really be splitting hairs at that point. Theoretically, yes, a shorter cable should be faster, yet not sure we can notice that small of a difference. A 5ms drop is noticeable, yet not sure .6ms I would be able to tell (however, maybe.....maybe....possibly, yet I'll take my 5ms input lag drop due to 120hz .... over a shorter cable .6ms )