Results 1 to 6 of 6

Thread: Response Time on a Computer Screen

  1. #1
    Join Date
    Nov 2008
    Posts
    45

    Response Time on a Computer Screen

    hello,

    Hello , I Have Proview 17 "TFT 1280 * 1024 with 16ms response time what is the best response times if I want to change it to newer version and My question The higher the response time is high it is better or it is low Which is better. please Clear my Doubt About it Thanks in advance for your replies thank you

  2. #2
    Join Date
    May 2008
    Posts
    1,196

    Re: Response Time on a Computer Screen

    Hello , Anything response time under 8 to 12ms is reasonably good for gaming, but 5ms or less is better, especially with a lot of activity happening on screen. Anything more than 12ms will start to look like it's smearing. I like Samsung, since they manufacture their own LCD panels and offer better warranties than anyone else I've seen.

  3. #3
    Join Date
    May 2008
    Posts
    1,149

    Re: Response Time on a Computer Screen

    For typical home and small business use, specifications are irrelevant. Any name-brand monitor sold by a reputable dealer will feature at least the minimum specifications you need: .28 dot pitch, SVGA, noninterlaced and capable of 1,024-by-768 resolution. For gaming or working with graphics, look for a monitor with a refresh rate of at least 75hz at 1,024 by 768 resolution. The display quality of most monitors matches the price. However, if you can't see a difference between two monitors, buy the one that costs less. At the same price, you get much better value from a good 15-inch monitor than a mediocre 17-inch monitor. Most Web pages are created on 17-inch monitors. If you have a 15-inch monitor, you will waste online time scrolling to view everything.The tube size and viewable area of a monitor are not the same. Read system specs carefully. One 17-inch monitor might have a 15.1-inch viewable image, while others might have 16 inches. By U.S. law, the manufacturers and retailers must indicate the actual viewable size, which is measured diagonally, but the viewable area might be in much smaller print than the tube size. Monitors are heavy and therefore expensive to ship.

  4. #4
    Join Date
    Dec 2007
    Posts
    1,727

    Re: Response Time on a Computer Screen

    This refers to how quickly a pixel can change colors, measured in milliseconds (ms); the fewer the milliseconds, the faster the pixels can change, reducing the ghosting or streaking effect you might see in a moving or changing image. In general, manufacturers' specifications rely on best-case scenarios; real-world performance could be slower. A maximum of a 12ms-to-15ms response time across the spectrum is required for gaming or viewing television and movies without ghosting or streaking. We've only just begun to see LCDs with superfast pixel-response times,

  5. #5
    Join Date
    Mar 2004
    Posts
    1,059

    Re: Response Time on a Computer Screen

    For most flat screen computer monitors the response time varied from 25 to 50 ms. In other words, the maximum number of images displayed per second varied between 20 and 40, depending on the model. This means that when you play fast action games on an LCD monitor you get a noticeable afterglow or bluring of the image. This is why only the latest 15" and 17" fast response LCD monitors can be used for action games.

  6. #6
    Join Date
    Dec 2007
    Posts
    1,547

    Re: Response Time on a Computer Screen

    • 0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
    • 1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.
    • 10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.


    Normally, response times should be as fast as possible, but it is also possible for the computer to react so fast that the user cannot keep up with the feedback. For example, a scrolling list may move so fast that the user cannot stop it in time for the desired element to remain within the available window. The fact that computers can be too fast indicates the need for user-interface changes, like animations, to be timed according to a real-time clock rather than being timed as an indirect effect of the computer's execution speed: Even if a faster model computer is substituted, the user interface should stay usable.

    In cases where the computer cannot provide fairly immediate response, continuous feedback should be provided to the user in form of a percent-done indicator [Myers 1985]. As a rule of thumb, percent-done progress indicators should be used for operations taking more than about 10 seconds. Progress indicators have three main advantages: They reassure the user that the system has not crashed but is working on his or her problem; they indicate approximately how long the user can be expected to wait, thus allowing the user to do other activities during long waits; and they finally provide something for the user to look at, thus making the wait less painful. This latter advantage should not be underestimated and is one reason for recommending a graphic progress bar instead of just stating the expected remaining time in numbers.

    For operations where it is unknown in advance how much work has to be done, it may not be possible to use a percent-done indicator, but it is still possible to provide running progress feedback in terms of the absolute amount of work done. For example, a system searching an unknown number of remote databases could print the name of each database as it is processed. If this is not possible either, a last resort would be to use a less specific progress indicator in the form of a spinning ball, a busy bee flying over the screen, dots printed on a status line, or any such mechanism that at least indicates that the system is working, even if it does not indicate what it is doing. Note added for the Web version of this essay: Most Web browsers fail in providing useful progress bars, since they don't communicate what percentage of the entire download for a page has been completed.

    For reasonably fast operations, taking between 2 and 10 seconds, a true percent-done indicator may be overkill and, in fact, putting one up would violate the principle of display inertia (flashing changes on the screen so rapidly that the user cannot keep pace or feels stressed). One could still give less conspicuous progress feedback. A common solution is to combine a "busy" cursor with a rapidly changing number in small field in the bottom of the screen to indicate how much has been done.

    source-useit.com

Similar Threads

  1. What is the response time of SONY BRAVIA?
    By tHE lUELLA in forum Portable Devices
    Replies: 4
    Last Post: 03-05-2011, 10:21 AM
  2. How to make response time fast.
    By sweetsriheart in forum Software Development
    Replies: 1
    Last Post: 30-08-2010, 05:57 PM
  3. LDAP query - can I calculate the response time?
    By Benjamin in forum Active Directory
    Replies: 3
    Last Post: 29-04-2010, 10:35 AM
  4. What is the appropriate email response time
    By Ricky58 in forum Technology & Internet
    Replies: 3
    Last Post: 08-08-2009, 08:28 AM
  5. TFT Response time
    By Tillie in forum Monitor & Video Cards
    Replies: 7
    Last Post: 27-10-2008, 02:30 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,720,813.38235 seconds with 17 queries