You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 54.166.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 10:02, 6 May 2025.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪Jon Kolbert‬. The reason given is Open proxy/Webhost: See the help page if you are affected .
- Start of block: 18:27, 12 November 2023
- Expiry of block: 18:27, 12 November 2028
Your current IP address is 54.166.193.9. The blocked range is 54.166.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((short description|Phenomenon associated with some types of LCDs))
((multiple issues|
((original research|date=February 2012))
((update|inaccurate=yes|date=November 2010))
((more citations needed|date=January 2012))
))
'''Display lag''' is a [[phenomenon]] associated with most types of [[liquid crystal display]]s (LCDs) like smartphones and computers and nearly all types of [[high-definition television]]s (HDTVs). It refers to [[Latency (engineering)|latency]], or [[lag (video games)|lag]] between when the [[Signal (electronics)|signal]] is sent to the display and when the display starts to show that signal. This lag time has been measured as high as ((nowrap|68 ms,))<ref>((cite web |title=Face to Face cameras, printers, ... - DigitalVersus |date= |url=http://www.digitalversus.com/duels.php?ty=6&ma1=36&mo1=332&p1=3107&ma2=36&mo2=290&p2=2810&ph=12 |accessdate=2008-03-07 ))</ref> or the equivalent of 3-4 frames on a 60&nbsp;[[Hz]] display. Display lag is not to be confused with [[pixel response time]], which is the amount of time it takes for a pixel to change from one brightness value to another. Currently the majority of manufacturers quote the pixel response time, but neglect to report display lag. ((Citation needed|date=September 2016))

== Analog vs digital technology ==
For older analog [[cathode ray tube]] (CRT) technology, display lag is nearly zero, due to the nature of the technology, which does not have the ability to store image data before display. The picture signal is minimally processed internally, simply for [[demodulation]] from a radio-frequency (RF) [[carrier wave]] (for televisions), and then splitting into separate signals for the red, green, and blue [[electron gun]]s, and for the timing of the vertical and horizontal sync. Image adjustments typically involve reshaping the signal waveform but without storage, so the image is written to the screen as fast as it is received, with only [[nanoseconds]] of delay for the signal to traverse the wiring inside the device from input to the screen.

For modern digital signals, significant computer processing power and memory storage is needed to prepare an input signal for display. For either over-the-air or cable TV, the same analog demodulation techniques are used, but after that, then the signal is converted to digital data, which must be decompressed using the MPEG codec, and rendered into an image bitmap stored in a [[frame buffer]].

For [[progressive scan]] display modes, the signal processing stops here, and the frame buffer is immediately written to the display device. In its simplest form, this processing may take several microseconds to occur.

For [[interlaced video]], additional processing is frequently applied to [[deinterlace]] the image and make it seem to be clearer or more detailed than it actually is. This is done by storing several interlaced frames and then applying algorithms to determine areas of motion and stillness, and to either merge interlaced frames for smoothing or extrapolate where pixels are in motion, the resulting calculated frame buffer is then written to the display device.

De-interlacing imposes a delay that can be no shorter than the number of frames being stored for reference, plus an additional variable period for calculating the resulting extrapolated frame buffer; delays of 16-32ms are common.<ref>((Cite web |title=HCI Design: Monitor Input Lag database |url=https://hcidesign.com/inputlag/lagdb.html |access-date=2022-05-03 |website=hcidesign.com))</ref>

== Causes of display lag ==
While the [[pixel response time]] of the display is usually listed in the monitor's specifications, no manufacturers advertise the display lag of their displays, likely because the trend has been to increase display lag as manufacturers find more ways to process input at the display level before it is shown. Possible culprits are the processing overhead of [[HDCP]], [[Digital Rights Management]] (DRM), and also [[Digital signal processing|DSP]] techniques employed to reduce the effects of [[ghosting (television)|ghosting]]&nbsp;– and the cause may vary depending on the model of display. Investigations have been performed by several technology-related websites, some of which are listed at the bottom of this article.

LCD, plasma, and DLP displays, unlike CRTs, have a [[native resolution]]. That is, they have a fixed grid of pixels on the screen that show the image sharpest when running at the native resolution (so nothing has to be scaled full-size which blurs the image). In order to display non-native resolutions, such displays must use [[video scaler]]s, which are built into most modern monitors. As an example, a display that has a native resolution of 1600x1200 being provided a signal of 640x480 must scale width and height by 2.5x to display the image provided by the computer on the native pixels. In order to do this, while producing as few [[Artifact (error)|artifacts]] as possible, advanced signal processing is required, which can be a source of introduced latency. [[Interlaced video]] signals such as 480i and 1080i require a [[deinterlacing]] step that adds lag. Anecdotally((Original research inline|date=March 2017)), display lag is significantly less when displays operate in native resolutions for a given LCD screen and in a [[progressive scan]]ning mode. External devices have also been shown to reduce overall latency by providing faster image-space resizing algorithms than those present in the LCD screen.((Citation needed|date=March 2017))  In practice this would stack the internal and external latencies.

Many LCDs also use a technology called "overdrive" which buffers several frames ahead and processes the image to reduce blurring and streaks left by ghosting. The effect is that everything is displayed on the screen several frames after it was transmitted by the video source.((Citation needed|date=April 2008))

== Testing for display lag ==
Display lag can be measured using a test device such as the Video Signal Input Lag Tester. Despite its name, the device cannot independently measure input lag. It can only measure input lag and response time together.

Lacking a measurement device, measurement can be performed using a test display (the display being measured), a control display (usually a [[cathode ray tube|CRT]]) that would ideally have negligible display lag, a computer capable of mirroring an output to the two displays, [[stopwatch]] software, and a high-speed camera pointed at the two displays running the stopwatch program. The lag time is measured by taking a [[photograph]] of the displays running the stopwatch software, then subtracting the two times on the displays in the photograph. This method only measures the difference in display lag between two displays and cannot determine the absolute display lag of a single display. CRTs are preferable to use as a control display because their display lag is typically negligible. However, video mirroring does not guarantee that the same image will be sent to each display at the same point in time.

In the past it was seen as common knowledge that the results of this test were exact as they seemed to be easily reproducible, even when the displays were plugged into different ports and different cards, which suggested that the effect is attributable to the display and not the computer system. An in depth analysis that has been released on the German website [http://www.prad.de Prad.de] revealed that these assumptions have been wrong. Averaging measurements as described above lead to comparable results because they include the same amount of systematic errors. As seen on different monitor reviews the so determined values for the display lag for the very same monitor model differ by margins up to ((nowrap|16 ms)) or even more.

To minimize the effects of asynchronous display outputs (the points of time an image is transferred to each monitor is different or the actual used frequency for each monitor is different) a highly specialized software application called SMTT <ref>((Cite web |last=Thiemann |first=Thomas |date=2020-05-22 |title=smtt.thomasthiemann.com - SMTT Website |url=https://smtt.thomasthiemann.com/index_en.html |access-date=2022-05-03 |website=Thomas Thiemann |language=en))</ref> or a very complex and expensive test environment has to be used.

Several approaches to measure display lag have been restarted in slightly changed ways but still reintroduced old problems, that have already been solved by the former mentioned SMTT. 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 and recording both screens with a separate video recorder. When the video of both screens is paused, the difference in time shown on both displays have been interpreted as an estimation for the display lag.<ref>((cite web | url=http://hdtvlag.googlepages.com/ourtest | title=Google Sites: Sign-in ))</ref> Nevertheless, this is almost identical to the use of casual stopwatches on two monitors using a "clone view" monitor setup as it does not care about the missing synchronisation between the composite video signal and the display of the laptop's screen or the display lag of that screen or the detail that the vertical screen refresh of the two monitors is still asynchronous and not linked to each other. Even if V-sync is activated in the driver of the graphics card the video signals of the analog and the digital output will not be synchronized.<ref>((cite web | url=http://www.prad.de/new/monitore/specials/inputlag/inputlag-teil18.html | title=Untersuchung des Testverfahrens einer Input-Lag-Messung | date=27 August 2009 ))</ref> Therefore, it is impossible to use a single stop watch for display lag measurements, nevertheless if it is created by a timecode or a simple stopwatch application, as it will always cause an error of up to ((nowrap|16 ms)) or even more.

== Effects of display lag on users ==

Display lag contributes to the overall latency in the interface chain of the user's inputs (mouse, keyboard, etc.) to the graphics card to the monitor. Depending on the monitor, display lag times between ((nowrap|10-68 ms)) have been measured. However, the effects of the delay on the user depend on each user's own sensitivity to it.

Display lag is most noticeable in games (especially older video-game consoles), with different games affecting the perception of delay. For instance, in ''[[World of Warcraft]]'s'' [[Player versus environment|PvE]], a slight input delay is not as critical compared to [[player versus player|PvP]], or to other games favoring quick reflexes like ''[[Counter-Strike]]''. Rhythm-based games, such as ''[[Guitar Hero]]'', also require exact timing; display lag will create a noticeable offset between the music and the on-screen prompts. Notably, many games of this type include an option that attempts to calibrate for display lag. Arguably, fighting games such as ''[[Street Fighter]]'', ''[[Super Smash Bros. Melee]]'' and ''[[Tekken]]'' are the most-affected, since they may require move inputs within extremely tight event windows that sometimes only last 1 frame or 16.67 ms on the screen.

By assuming a Gaussian human response time to a particular in-game event, it becomes possible to discuss the effect of lag in terms of probabilities.<ref>((cite web|url=http://meleeiton.me/2014/03/27/this-tv-lags-a-guide-on-input-and-display-lag/ |title=Melee It on Me &#124; Ugh, This TV Lags! |accessdate=2015-02-22 |url-status=dead |archiveurl=https://web.archive.org/web/20150220052714/http://meleeiton.me/2014/03/27/this-tv-lags-a-guide-on-input-and-display-lag/ |archivedate=2015-02-20 ))</ref> Given a lag-less display, a human has a certain probability to land his/her input within a window of frames. As video games operate on discrete frames, missing the last frame of the window even by 0.1 ms causes an input to be interpreted a full frame later. Because of this, any amount of lag will affect a human's ability to hit a particular timing window. The severity of this impact is a function of the position and variance of a human's response to a visual cue, the amount of lag introduced, and the size of the timing window. For example, given a very large window of 30 frames, a human would likely have a 99.99% chance of hitting this window. By introducing one frame of lag, the human's ability to hit the 30 frame window would likely remain in the 99.99% range (assuming the human is responding somewhere near the middle of the window). Given a smaller window of say 2 frames, however, the effect of lag becomes much more significant. Assuming the human's response is centered on the 2 frame window and the super-human has a 99.99% chance to hit the window, introducing a full frame of lag causes the success rate to drop all the way to about 50%.

If the game's controller produces additional feedback (rumble, the [[Wii Remote]]'s speaker, etc.), then the display lag will cause this feedback to not accurately match up with the visuals on-screen, possibly causing extra disorientation (e.g. feeling the controller rumble a split second before a crash into a wall).

TV viewers can be affected as well. If a home theater receiver with external speakers is used, then the display lag causes the audio to be heard earlier than the picture is seen. "Early" audio is more jarring than "late" audio. Many home-theater receivers have a manual audio-delay adjustment which can be set to compensate for display latency.

==Solutions==
=== Game mode ===
Many televisions, [[Video scaler|scalers]] and other consumer-display devices now offer what is often called a "game mode" in which the extensive preprocessing responsible for additional lag is specifically sacrificed to decrease, but not eliminate, latency. While typically intended for videogame consoles, this feature is also useful for other interactive applications. Similar options have long been available on home audio hardware and [[modem]]s for the same reason. Connection through VGA cable or component should eliminate perceivable input lag on many TVs even if they already have a game mode. Advanced post-processing is non existent on analog connection and the signal traverses without delay.

===Renaming input===
A television may have a picture mode that reduces display lag for computers. Some Samsung and LG televisions automatically reduce lag for a specific input port if the user renames the port to "PC".<ref name="morrison20150721">((Cite web |url=https://www.cnet.com/news/how-to-use-your-4k-tv-as-a-monitor/ |title=How to use your 4K TV as a monitor |last=Morrison |first=Geoffrey |date=2015-07-21 |website=CNET |language=en |access-date=2020-01-31))</ref>

== Display lag versus response time ==
LCD screens with a high [[Pixel response time|response-time]] value often do not give satisfactory experience when viewing fast-moving images (they often leave streaks or blur; called [[motion blur|ghosting]]). But an LCD screen with both high response time and significant display lag is unsuitable for playing fast-paced computer games or performing fast high-accuracy operations on the screen, due to the mouse cursor lagging behind.

== See also ==
* [[Input lag]]

== References ==
((reflist))

== External links ==
* [https://www.dein-fernseher.de/input-lag-fernseher Database with measurements from input lag for over 200 televisions (German)]
* [http://www.prad.de/new/monitore/specials/inputlag/inputlag.html Article on PRAD.de - first scientific approach to determine display lag (German)]
* [http://www.tftcentral.co.uk/articles/input_lag.htm Input Lag Testing - Article on TFT Central comparing different methods (14 Dec 2011)]
* [http://smtt.thomasthiemann.com/index_en.html SMTT - Highly optimized display lag test software to reduce the error margin that is usual for plain stopwatch applications]
* [http://www.flatpanelshd.com/focus.php?subaction=showfull&id=1229335064 FlatpanelsHD.com - Display lag test software] (Dec 15, 2008)
* [http://www.behardware.com/articles/632-1/lcds-images-delayed-compared-to-crts-yes.html BeHardware test - ''LCDs images delayed compared to CRTs? Yes !''] (Aug 3, 2006)
* [http://www.behardware.com/articles/647-4/which-22-inch-to-choose-six-monitors-tested-with-reaction-times-from-2-to-5-ms.html BeHardware tests 22inch TFT monitors for display lag] (Dec 19, 2006)
* [http://www.avsforum.com/avs-vb/showthread.php?t=558125 Avs Forum posting on display lag]
* [https://www.youtube.com/watch?v=pi2OE6hSh00 Video demonstrating display lag in Quake] (June 24, 2006)
* [https://www.youtube.com/watch?v=hVXTeGTp5tw&NR Video demonstrating display lag in UT2003] (June 27, 2006)
* [http://www.tftcentral.co.uk/features.htm TFT Central - ''Display lag and TFT features''] (Oct 29, 2008)
* [https://web.archive.org/web/20110726010059/http://fuchur.dyndns.org/nik/leaveasitis/TFTvsCRT.wmv Video demonstrating display lag in Windows UI] (Dec 12, 2006)
* [http://gear.ign.com/articles/720/720303p1.html The HDTV-Gaming-Lag Report] (July 21, 2006) (Note: this article is compiled from IGN reader opinions and not guaranteed to be accurate)
* [http://www.anandtech.com/show/2803 Anandtech article about Input Lag] (July 16, 2009)

((DEFAULTSORT:Display Lag))
[[Category:Display technology]]
[[Category:Liquid crystal displays]]

Pages transcluded onto the current version of this page (help):

Display lag (edit)
Template:Ambox (view source) (template editor protected)
Template:Ambox globe (view source) (template editor protected)
Template:Ambox globe current red (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Citation needed (view source) (protected)
Template:Cite web (view source) (protected)
Template:Delink (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix (view source) (protected)
Template:Fix/category (view source) (protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Nowrap (view source) (protected)
Template:Original research (view source) (template editor protected)
Template:Original research inline (view source) (template editor protected)
Template:Pagetype (view source) (protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:SDcat (view source) (protected)
Template:SUBJECTSPACE formatted (view source) (template editor protected)
Template:Short description (view source) (protected)
Template:Short description/lowercasecheck (view source) (protected)
Template:Update (view source) (template editor protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Delink (view source) (protected)
Module:Disambiguation/templates (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Pagetype (view source) (protected)
Module:Pagetype/config (view source) (protected)
Module:Pagetype/disambiguation (view source) (protected)
Module:Pagetype/setindex (view source) (protected)
Module:Pagetype/softredirect (view source) (protected)
Module:SDcat (view source) (protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Wikitext Parsing (view source) (protected)
Module:Yesno (view source) (protected)

Return to Display lag.

Retrieved from "https://en.wikipedia.org/wiki/Display_lag"