It's compareable to plain stop watches on two monitors. This is one of the biggest mistakes you can do. The timecode will definitely not be sent at the same time to the LCD of the Laptop and the HDTV through the composite connection. Whenever paused, the difference in time on both displays can be interpreted as an estimation for the input lag.ĭoing it that way reintroduces the old mistakes! The mentioned "satisfying" results are simply wrong. One such method involves connecting a laptop to an HDTV through a composite connection and run a timecode that shows on the laptop's screen and the HDTV simultaneously. Many new ways to measure input lag have been ingeniously developed and produce satisfying results. Besides, Google agrees too: Quoted search on Google "display lag" = 21,200 results Quoted search on Google "input lag" = 829,000 results Mdrejhon ( talk) 20:17, 3 October 2012 (UTC) Reply I'd rather have a single, good article "input lag" that covers the multiple different sources of of lag. An example of input lag using high speed video camera is on YouTube at showing the lag between input device and visible action. See Anandtech's definition of input lag which is a really good article of the many sources of input lag between human input ("input device"), to the human eyeballs. Mdrejhon ( talk) 23:49, 1 October 2012 (UTC) Reply Examples of Precedent. The terminology "display lag" does not cover lag introduced by the computer side. Add new section "display lag" vs "input lag", and the confusion of "input lag" (some sites refer to it as the "lag on video input", some sites refer to it as "lag relative to human input"). See my long explanation above, that explains precedent for the naming "input lag". It's certain websites that doesn't quite fully clarify "input lag" meaning. The original name was more accurate, because it's lag behind human input.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |