# Zen Lab > Cronus Zen latency and polling, explained Source-based explanations of Cronus Zen latency, controller polling and test methods. Manufacturer claims and outside measurements are attributed. Subjects: Cronus Zen latency, Cronus Zen polling rate, Cronus Zen firmware, anti-recoil tuning, controller input testing. Notes by Dana Rehn at https://cronuszenlab.com/, published as Zen Lab. All notes in a single file: https://cronuszenlab.com/llms-full.txt. ## The Zen in brief, 18 November 2026 - Latest Cronus Zen firmware: 2.4.1, dated 17 November 2026, one day after 2.4.0. Per Cronus's [2026 changelog](https://guide.cronuszen.com/changelogs/changelog-26), checked 18 November, 2.4.1 fixes programming over Zen Link and 2.4.0 fixes DualShock 4 and DualSense mic and audio on PS4, PS5 and Xbox along with Xbox Wi-Fi reconnection after the pad sleeps. Neither entry states a latency figure ([firmware notes](https://cronuszenlab.com/reference/input-latency-by-firmware)). - Does the Cronus Zen add input lag? Zen Lab has published no measurement of the Zen's own delay, and Cronus's guide gives no latency figure for it. The published sources place a pass-through device such as the Zen in the peripheral stage of NVIDIA's latency model, because the console reads the Zen's reports in place of the controller's, and a wired pad then crosses two USB polling schedules ([the latency budget](https://cronuszenlab.com/reference/what-adds-controller-input-latency)). - How much delay does polling rate add? A wait of zero to one full interval on every press: up to 8 ms at 125 Hz and up to 1 ms at 1000 Hz ([polling rate](https://cronuszenlab.com/reference/controller-polling-rate-explained)). - Can two input-lag numbers be compared? Only when they time the same stretch of the chain. A camera rig and an electrical button tap time different stretches, so their figures cannot be set side by side ([measurement methods](https://cronuszenlab.com/reference/how-input-latency-is-measured)). ## Cronus software versions, read 18 November 2026 The Zen Link module had four releases in November: 2.1.5 on 4 November, 2.1.6 and 2.1.7 on 6 November, then 2.2.0 on 16 November, which can read a slot's script back and copy it to another slot. Zen Studio Live, the browser version of Zen Studio, reached v1.0.12 on 17 November; since v1.0.11 of 16 November it needs firmware 2.4.0 or newer for full operation. Any future original result would apply only to its recorded versions, and a software change calls for a new comparison ([how re-tests work](https://cronuszenlab.com/reference/retesting-after-firmware-and-patches)). ## Reference - [Constant recoil correction vs a curve: how to compare them](https://cronuszenlab.com/reference/anti-recoil-curve-tuning): A method for comparing constant and time-varying correction without unsupported performance claims. - [Cronus Zen firmware latency: what release notes establish](https://cronuszenlab.com/reference/input-latency-by-firmware): How to separate firmware fixes from measured input-lag improvements. Release notes do not establish a fastest firmware. - [Cronus Zen on PS5 vs Xbox: how to compare input lag](https://cronuszenlab.com/reference/cronus-zen-ps5-vs-xbox-series-latency): Why console totals alone cannot isolate the latency added by a Cronus Zen. - [Does a heavier Cronus Zen script add input lag?](https://cronuszenlab.com/reference/cronus-zen-script-load-latency): How to distinguish script processing load from end-to-end input latency without assuming a fixed penalty. - [How to measure an NBA 2K green window](https://cronuszenlab.com/reference/nba-2k-green-window-measurement): A green window is a timing-response curve, not the same number as a script green percentage. - [Input-lag test equipment: what a reproducible report needs](https://cronuszenlab.com/reference/test-rig): A checklist for documenting press detection, response detection, timing and the full test chain. - [Reviewing latency claims after firmware and game updates](https://cronuszenlab.com/reference/retesting-after-firmware-and-patches): How to decide what needs a new source check or a new physical test after a software change. - [Wired vs wireless through Cronus Zen: what to compare](https://cronuszenlab.com/reference/cronus-zen-wired-vs-wireless-latency): Connection type alone does not determine latency. Compare the same controller, host and display under recorded conditions. - [Zen Link Native Mode vs PS5 bypass: setup and latency claims](https://cronuszenlab.com/reference/zen-link-native-mode-vs-ps5-bypass-latency): Separate connection instructions from claims that one PS5 route is measurably faster. ## Method - [How input latency is measured: cameras, photodiodes and button taps](https://cronuszenlab.com/reference/how-input-latency-is-measured): Input lag is timed from a press to its result. What high-speed cameras, screen photodiodes, solenoids and electrical button taps each include and can resolve. - [How much delay does controller polling rate add?](https://cronuszenlab.com/reference/controller-polling-rate-explained): Up to one USB interval per press: 8 ms at 125 Hz, 1 ms at 1000 Hz. How bInterval sets the rate, with published DualSense and Xbox Series figures. - [What adds latency between a controller press and the screen](https://cronuszenlab.com/reference/what-adds-controller-input-latency): Every stage from a controller press to the screen adds delay. Published figures and bounds for each, from pad firmware and USB polling to the game frame and TV. ## Who writes the notes - [Dana Rehn](https://cronuszenlab.com/authors/editorial): Technical editor. Dana Rehn writes source-based explanations of Cronus Zen latency, polling and measurement methods. Dana funds the work personally, distinguishes manufacturer claims from outside measurements, and controls the conclusions. ## Site pages - [About Zen Lab](https://cronuszenlab.com/about): Dana Rehn explains Cronus Zen latency, polling and measurement methods using attributed sources. - [Zen Lab editorial standards](https://cronuszenlab.com/editorial-policy): Source attribution, numerical claims and corrections for the Zen Lab reference notes. - [Zen Lab methodology: sources, comparisons and measurement limits](https://cronuszenlab.com/methodology): How Zen Lab attributes outside findings and explains test design without presenting unsupported original measurements. ## Optional - [Sitemap](https://cronuszenlab.com/sitemap.xml): note and reference URLs, dated by their last edit - A note as markdown: start the path with /md, like https://cronuszenlab.com/md/reference/anti-recoil-curve-tuning --- # Constant recoil correction vs a curve: how to compare them Source: https://cronuszenlab.com/reference/anti-recoil-curve-tuning Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: anti-recoil, tuning, drift, gpc, call of duty **Quick answer.** A constant correction applies the same adjustment throughout a spray; a curve changes that adjustment over time. Which fits better depends on the weapon and conditions. A curve is not automatically better. ## Keep the comparison controlled Use the same weapon, attachments, stance, distance and sensitivity. Keep the game version, controller and script build fixed. Compare equal numbers of full-magazine trials with correction off, constant correction and the curve being evaluated. A claim about one weapon does not establish performance on other weapons. Do not use an unmatched game or attachment setup to rank two scripts. ## Report a reproducible outcome Choose a clear measure before testing: end-of-magazine displacement, spread around a reference point or displacement over time. Explain whether the reported summary is a mean, median, maximum or something else. If measurements come from video, give the resolution and timing method. At 1080 pixels in height, one vertical pixel is approximately 0.093% of frame height. A percentage can be compared across resolutions only when the scene geometry and measurement definition are also comparable. ## Limits No original recoil-drift table is published here. Earlier figures and fixture-validation claims were removed because the supporting recordings and calculation records were unavailable. This note explains comparison design; it does not establish that a particular product performs better or complies with game rules. --- # Cronus Zen firmware latency: what release notes establish Source: https://cronuszenlab.com/reference/input-latency-by-firmware Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-18 Tags: latency, firmware, benchmark, versions **Quick answer.** This page does not establish which Cronus Zen firmware has the lowest latency. A firmware changelog identifies software changes; it is not a controlled timing comparison. ## What the release record says The [Cronus firmware changelog](https://guide.cronuszen.com/changelogs/changelog-26), checked 18 November 2026, lists 2.4.1 dated 17 November as the newest release. It follows 2.4.0 of 16 November, which went out after stable 2.3.2 (18 August) and 2.3.3 Beta 1 (8 September). The 2.4.0 entry fixes controller mic and audio problems, an Xbox pad that would not reconnect over Wi-Fi after sleeping, and the Xbox transmit buffers; 2.4.1 fixes programming over Zen Link. None of these entries gives a millisecond figure or claims a change in input lag. ## What a fair comparison needs Compare a direct-controller baseline with the through-Zen path on the same controller, console, display and response screen. Repeat that pair for each firmware version. Keep the connection route and active slot unchanged, and alternate conditions so session drift does not favor one version. Record the exact firmware, sample count and method. Report the distribution of readings, not only a single best press. A result from a different controller or display cannot isolate a firmware effect. ## How to interpret an update A stability fix may matter even when no latency improvement is claimed. Use the vendor's documented update route and compatibility instructions. Do not assume a beta is faster merely because its version number is higher. ## Editorial note The earlier version of this article included original timing estimates. They have been removed because the underlying readings and statistical calculation could not be reconstructed. This version is a sourced explainer, not a firmware benchmark. ## Related reading See [how input latency is measured](/reference/how-input-latency-is-measured) and the [measurement methodology](/methodology). ## FAQ **Which Cronus Zen firmware has the least input lag?** This page does not establish a fastest firmware. The cited release notes describe software changes, not a controlled latency comparison. --- # Cronus Zen on PS5 vs Xbox: how to compare input lag Source: https://cronuszenlab.com/reference/cronus-zen-ps5-vs-xbox-series-latency Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: latency, ps5, xbox series, zen link, native mode **Quick answer.** A lower total input lag on one console does not show that the Zen is faster on that console. Compare each through-Zen path with its own direct-controller baseline first. ## Separate the device from the rest of the chain [NVIDIA's latency overview](https://www.nvidia.com/en-gb/geforce/news/reflex-low-latency-platform/) distinguishes peripheral, processing and display latency. Its examples concern PC systems; that framework helps explain why changing several parts of a console setup at once prevents a device-only conclusion. For each console, keep the controller, game scene, refresh rate and display mode fixed between the direct and through-Zen conditions. Record the PS5 connection route separately; [Cronus Zen Link setup](https://guide.cronuszen.com/zen-link/setup) documents the native connection setup. ## Report comparable quantities | Quantity | What it describes | | --- | --- | | Direct median | Typical measured delay without the Zen in that setup | | Through-Zen median | Typical delay with the Zen in that setup | | Difference of medians | Change between those two conditions | | Difference of p95 values | Change between two tail summaries, not the p95 of the Zen alone | A console comparison also changes the controller and platform software. Even after subtracting a baseline, do not generalize a single setup to every game or controller. ## Conclusion No original PS5-versus-Xbox millisecond ranking is published here. Earlier numerical claims were withdrawn because their supporting session records were unavailable. See [test design](/reference/test-rig) for the conditions a reproducible comparison should record. ## FAQ **Does Cronus Zen have less input lag on PS5 or Xbox?** There is no universal result established here. Each console needs a same-setup direct baseline and through-Zen measurement before the added delay can be compared. --- # Does a heavier Cronus Zen script add input lag? Source: https://cronuszenlab.com/reference/cronus-zen-script-load-latency Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: latency, gpc, cpu load, main loop, vm interval **Quick answer.** More script work can change processing behavior, but a load percentage does not tell you how many milliseconds reach the screen. This page does not assign a universal latency penalty to commercial scripts. ## Compare like with like A useful experiment compares an empty slot, a pass-through fixture and controlled increments of additional work. Keep the controller, firmware, console, display and test scene the same. Test whether connecting monitoring equipment changes the measurement. A synthetic arithmetic loop can isolate one kind of workload. It does not represent every commercial script, which may spend time on menus, stored settings, input sequences or different execution paths. ## Two different measurements | Measurement | Interpretation | | --- | --- | | A tool's load reading | What that tool reports about execution load | | Press-to-screen time | The response of the entire tested chain | Neither can be substituted for the other. Read a tool's documentation before treating a percentage as a hardware utilization limit or a measured delay. ## Reporting a result Name the exact fixture or script build, its settings and the sample count. Compare distributions across conditions and report the measurement resolution. A claimed sub-millisecond difference requires an instrument and analysis that can support it. The previous original load table and unverified compile statistics have been removed. No commercial script is ranked by latency here. The [latency breakdown](/reference/what-adds-controller-input-latency) explains why the entire chain matters. --- # How to measure an NBA 2K green window Source: https://cronuszenlab.com/reference/nba-2k-green-window-measurement Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: nba 2k27, green window, shot timing, method, gpc **Quick answer.** A green window is the range of release timings that can produce green shots under specified conditions. It is not the same as the percentage of shots a script greens in one session. ## Measure timings, not just success totals Choose one build, jumpshot, cue, distance and mode. Vary the hold or release timing in controlled steps. At each step, repeat the same number of attempts and record green versus non-green outcomes. Plot the success rate against timing. State how the edges are defined: a non-zero success rate, a chosen probability threshold and a fitted boundary are different definitions and can produce different widths. ## What changes the interpretation? Keep badges, stamina, contests and relevant game settings controlled. Record the game patch and connection conditions. An offline test does not establish the same curve in every online mode. A frame or sampling interval limits what the instrument can distinguish. For example, 60 frames per second gives about 16.7 ms between frames; that arithmetic is not itself a measured NBA 2K timing window. ## Green rate versus window width A fixed-count script comparison answers how many attempts were green under that protocol. Without controlled timing offsets, those attempts do not reveal the window's width in milliseconds. This article contains no original window-width estimate. Earlier center, width and confidence-interval claims were withdrawn because their trial records were unavailable. For instrumentation choices, see [how input latency is measured](/reference/how-input-latency-is-measured). --- # Input-lag test equipment: what a reproducible report needs Source: https://cronuszenlab.com/reference/test-rig Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: rig, method, latency, resolution, versions **Quick answer.** An input-lag report needs a defined start event, a defined end event and a timing method. A list of gaming hardware alone does not establish measurement accuracy. ## Define the signal being timed Record how the button press is detected and how the screen response is detected. State whether both events use the same clock. If separate clocks are involved, explain synchronization and its uncertainty. [RTINGS' input-lag method](https://www.rtings.com/tv/tests/inputs/input-lag) describes a display-specific measurement method. That is useful context, but a display-only result is not a complete controller-to-screen measurement. ## Record the chain | Part | Information to retain | | --- | --- | | Controller | Model, firmware and connection | | Device under test | Firmware, slot and script or fixture version | | Console or PC | System version, game build and scene | | Display | Model, refresh rate, mode and response location | | Instrument | Sensors, clock, sampling rate and calibration | | Trials | Conditions, sample count, order and exclusion rules | ## Resolution is not the whole uncertainty A 1000 Hz sample stream has 1 ms between samples. Sensor thresholds, display scanning, clock alignment and event detection can introduce additional uncertainty. A large number of trials does not automatically eliminate systematic error. ## Publication scope This is a measurement checklist, not a claim that Zen Lab owns or has validated a particular rig. The earlier hardware inventory and photo references were removed where they could not be confirmed. See [the method](/methodology) for how the site distinguishes sourced explanation from original results. --- # Reviewing latency claims after firmware and game updates Source: https://cronuszenlab.com/reference/retesting-after-firmware-and-patches Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: re-test, firmware, benchmark, method, versions **Quick answer.** An update can invalidate an older comparison, but a release date does not establish that latency changed. Check what changed, then decide which conditions need to be remeasured. ## Source review versus a physical retest A source review checks the current documentation and release notes. A physical retest collects new measurements under recorded conditions. The article must say which happened. | Change | What to review | | --- | --- | | Device firmware | Input routing, compatibility and any timing claims | | Controller or console update | Baseline behavior and connection settings | | Game patch | The response scene and mechanics used in a test | | Display or instrument change | Whether old and new measurements are comparable | ## Preserve context Keep the earlier version and source-check date visible when discussing an old result. Do not attach a newer update date to an old table and imply that it was retested. ## Current scope Zen Lab's current articles explain sources and test design. They do not claim that every firmware release has been physically benchmarked. An original result would need the setup, sample count and reproducible calculation described in [the methodology](/methodology). --- # Wired vs wireless through Cronus Zen: what to compare Source: https://cronuszenlab.com/reference/cronus-zen-wired-vs-wireless-latency Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: latency, wireless, bluetooth, dualsense, xbox series controller **Quick answer.** Neither USB nor wireless is automatically faster for every controller setup. A useful comparison holds the controller, host and display constant and changes only the connection being tested. ## Why a connection label is not a measurement A controller's own processing, the host, the game and the display all contribute to response time. [NVIDIA's latency overview](https://www.nvidia.com/en-gb/geforce/news/reflex-low-latency-platform/) explains these separate stages; it does not supply a Cronus Zen wired-versus-wireless result. A PC controller test is useful context, but it does not establish what happens when that controller connects through a Zen to a console. The host and routing are different. ## Conditions to record Use the same controller unit, firmware and display mode. For wireless, note distance, battery level and the radio environment. For a direct baseline, make sure the console actually uses the intended connection instead of silently falling back to Bluetooth. Measure many presses under each condition and compare both typical response and variability. A small average difference can conceal an uneven tail; one unusually fast press does not describe the normal experience. ## Practical interpretation When troubleshooting, change one setting at a time. Check the connection requirements in the device's setup instructions before assuming that a wireless route is supported. This page publishes no original wired-versus-wireless figures. Earlier tables were removed because their underlying readings were not available for checking. [Polling rate](/reference/controller-polling-rate-explained) and [the full input chain](/reference/what-adds-controller-input-latency) explain related concepts. --- # Zen Link Native Mode vs PS5 bypass: setup and latency claims Source: https://cronuszenlab.com/reference/zen-link-native-mode-vs-ps5-bypass-latency Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Reference Published: 2026-10-10 · Updated: 2026-11-14 Tags: zen link, ps5, latency, native mode, bypass **Quick answer.** A documented connection route does not establish a measured latency advantage. This page does not claim that Native Mode is a specific number of milliseconds faster than a bypass route. ## Start with the actual route [Cronus Zen Link setup](https://guide.cronuszen.com/zen-link/setup) documents native PS5 setup and recommends the A1 port for the Zen Link. Follow the current vendor instructions for the hardware model rather than combining steps from different connection methods. Record the route, firmware, controller port and console settings before comparing timings. If a route requires different settings, it needs an appropriate baseline under those settings. ## What would establish a difference? Repeat the direct and device-connected measurements with the same response screen and display mode. Specify what detects the press, what detects the screen response, and which clock timestamps both events. Resolution and variability matter. A difference of one sampling step is not automatically a repeatable improvement. A confidence interval describes uncertainty only when its input data and calculation are known. ## Scope of this note Earlier numerical comparisons have been withdrawn because the session readings were unavailable. This is a setup-and-interpretation guide, not an endorsement of either route or a compatibility guarantee. See [the measurement checklist](/reference/test-rig). --- # How input latency is measured: cameras, photodiodes and button taps Source: https://cronuszenlab.com/reference/how-input-latency-is-measured Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Method Published: 2026-10-10 · Updated: 2026-11-14 Tags: input lag, latency, measurement, photodiode, high-speed camera Input latency is measured by timestamping a press and the response it causes, and each published method puts those two timestamps at a different point in the chain. A camera starts the clock on the visible press and stops on the first changed frame, while an electrical tap closes the button contact itself and stops when the input event reaches a computer. Figures taken with different methods cover different stretches of the chain and cannot be compared directly. NVIDIA's [Reflex article of 1 September 2020](https://www.nvidia.com/en-gb/geforce/news/reflex-low-latency-platform/), by Seth Schneider, names the stretches. Peripheral latency is the input device processing the press and sending it to the PC. PC latency is a frame's trip through the PC, game and render together. Display latency runs from the finished frame to the new image on the panel, and system latency is the whole span. With a console in the chain, the console fills the PC's segment. ## Which segment does each method cover? | Method | Clock starts | Clock stops | Segments covered | Stated resolution or accuracy | | --- | --- | --- | --- | --- | | High-speed camera | Press, seen on video | First changed frame on screen | Peripheral, PC or console, display, plus finger travel | One frame: about 4.17 ms at 240 fps, 1 ms at 1000 fps | | LagBox (Bockes, Wimmer and Schmid, CHI EA 2018) | Opto-coupler closes the button contact | Input event arrives at a Raspberry Pi 2 | Peripheral, from the contact onward | Sub-millisecond, per the authors | | Schmid and Wimmer device (EHPHCI 2021) | Opto-coupler closes a mouse button contact | Photoresistor sees the screen region turn white | Peripheral from the contact onward, PC, display | Device's own delay averaged 116.5 µs over 200 readings | | Optical mouse on the screen (Casiez et al., UIST 2015) | Displayed texture moves under the mouse | Mouse reports the motion | Display output and mouse input as one loop | Up to 5 readings per second | | Blur Busters Arduino tester (2012) | Software flashes squares on screen | Photodiode sees the change | Display, against a reference | ±0.1 ms claimed after zero calibration | | NVIDIA LDAT | Mouse click | Luminance change on the panel | Peripheral, PC, display | No figure on NVIDIA's page | | NVIDIA Reflex Latency Analyzer | Click arriving at the monitor's USB port | Resulting pixel change | PC and display; peripheral too with a compatible mouse | None stated | | Gamepadla Prometheus 82 | Solenoid makes contact with the control | PC registers the input | Peripheral, including actuation | ±1 ms stated in the Prometheus 82 README | | RTINGS TV input lag test | Tool flashes a white square | Pixels at screen center start to change | Display only, pixel response excluded | Floor of 4.17 ms at 120 Hz, 8.33 ms at 60 Hz | ## Cameras count in frames A high-speed camera films the controller and the screen in one shot, and the frames between the press and the first change on screen are counted. Every reading is rounded to a whole frame. At 240 fps a frame lasts 1/240 s, about 4.17 ms; at 1000 fps it lasts 1 ms. NVIDIA's article gives that 1 ms floor for a 1000 FPS camera, puts the bare-minimum equipment at about $7,000 and says each measurement takes roughly 3 minutes. Andreas Schmid and Raphael Wimmer of the University of Regensburg give the same limits in [Yet Another Latency Measuring Device](https://epub.uni-regensburg.de/45570/1/yet-another-latency-measuring-device.pdf) (EHPHCI 2021): 1 ms at 1000 fps and 4 ms at 240 fps. They call the manual analysis of video cumbersome, which is why electrical methods were built. At 240 fps a 1 ms change is about a quarter of one frame, too small to appear in a single reading. ## Photodiodes and other screen sensors RTINGS describes its TV method on its [input lag test page](https://www.rtings.com/tv/tests/inputs/input-lag) (Adam Babcock, updated 3 October 2025). A photodiode tool sits at the center of the screen, and a test PC is connected to both the tool and the TV. The tool flashes a white square and stops timing the moment the pixels start to change, so the panel's response time is left out. The software averages several readings and ignores outliers. A TV draws each image from the top down, so a sensor at the center catches the change halfway through a refresh. On a 120 Hz TV each image takes 8.33 ms to draw, which makes 4.17 ms the lowest figure the test can record; on a 60 Hz TV the floor is 8.33 ms. Blur Busters published an early do-it-yourself version on [18 October 2012](https://www.blurbusters.com/sneak-preview-of-arduino-input-lag-meter/). Mark Rejhon's Arduino tester used a photodiode pressed against the screen and claimed input lag accuracy of ±0.1 ms once zero-calibrated against a CRT on the same system. A later edit to the post says the CRT calibration was no longer needed. NVIDIA's [LDAT](https://developer.nvidia.com/nvidia-latency-display-analysis-tool) is a discrete hardware analyzer built around a luminance sensor. NVIDIA says it measures motion-to-photon latency, click to muzzle flash, and works with GPUs from all vendors, and it publishes no accuracy figure. Schmid and Wimmer note that LDAT senses mouse button presses electrically, that it went only to a selection of hardware reviewers, and that its internals have not been published, so outside researchers cannot validate it. The Reflex Latency Analyzer, built into 360 Hz G-SYNC displays, takes another route. The mouse plugs into a designated USB port on the monitor, which watches for clicks and times until the resulting pixel change. NVIDIA says a compatible mouse adds peripheral latency to the reading, and any other mouse except a Bluetooth one gives PC plus display latency. Schmid and Wimmer point out that this clock starts when the click reaches the system, so the device's own internal latency stays outside it. Géry Casiez and colleagues ([UIST 2015](https://hal.science/hal-01226729)) turned the screen into the input. As Schmid and Wimmer summarize the method, the mouse sensor sits on the display, the display moves a texture under it, and the time until the input event arrives is the reading. The abstract gives up to five readings a second and allows software probes, such as mouse event listeners, to locate where the time goes. Their results show latency affected by the operating system and system load. ## Taps and solenoids on the button [LagBox](https://hci.uni-regensburg.de/publications/bockes_2018_lagbox) (Florian Bockes, Raphael Wimmer and Andreas Schmid, CHI EA 2018) runs on a Raspberry Pi 2. An opto-coupler soldered to a controller, mouse or keyboard button is switched from the Pi's GPIO pins, and the tool times each toggle until the input event arrives. The authors claim sub-millisecond accuracy. The group's [project page](https://hci.uni-regensburg.de/projects/input-device-latency) says a test repeats 1,000 times, with a random wait of 0.1 to 10 ms so the circuit can discharge. The same page models a device's latency as four parts: the button's mechanical delay, the device's microcontroller, the USB polling interval and the kernel's process-switching interval. Closing the contact electrically skips the first of those, so a LagBox figure starts at the contact. Schmid and Wimmer's 2021 device joins an electrical tap to a screen sensor. An Arduino Micro closes a modified mouse button through an LTV-817 opto-coupler, the test application turns a black region white, and a photoresistor taped to the monitor stops the timer. Between presses it waits a random 100 to 1,000 ms so it does not fall into step with the system under test. Its own delay averaged 116.5 µs over 200 readings, with a minimum of 112 µs and a maximum of 124 µs. Filmed for 99 readings with a Google Pixel 3a at 240 fps, its results differed from the frame counts by 2.64 ms on average, less than one frame of that video. The paper also shows how much sensor position matters: on a 60 Hz monitor the top and bottom of the screen differ by 16.67 ms. Gamepadla's [Prometheus 82](https://github.com/cakama3a/Prometheus82) keeps the mechanical stage in. Arduino hardware fires a solenoid at a button or stick, a sensor at the solenoid's tip marks the moment of contact, and Python software times until the PC registers the input. The project's README says a test repeats 500 times and gives a permissible error of ±1 ms for buttons and sticks. The test script as published sets 400 iterations with a 40 ms solenoid pulse and keeps readings between the 2% and 98% quantiles. Gamepadla's device pages measure polling rate separately with a software tool and list the Windows build behind each row. ## Why does a single reading say so little? Latency moves from one press to the next. Raphael Wimmer, Andreas Schmid and Florian Bockes measured 36 USB keyboards, mice and gamepads for [On the Latency of USB-Connected Input Devices](https://hci.uni-regensburg.de/publications/on_the_latency_of_usb-connected_input_devices_2019) (CHI 2019). The devices differed in the distribution of their latencies as well as in the average, and the authors write that reporting only means and standard deviations hides those distributions. Their project page proposes swarmplots, which draw every reading as its own point. Part of the spread comes from polling, since a press can land anywhere in the host's polling cycle. [The polling note](/reference/controller-polling-rate-explained) works through that arithmetic, and [the stage-by-stage latency budget](/reference/what-adds-controller-input-latency) lists the other stages that vary. Labs also summarize in different ways. RTINGS averages its readings and leaves out outliers. Gamepadla's script trims its readings to the 2% to 98% quantile range before averaging, while the Regensburg group plots every point. ## FAQ **How is controller input lag measured?** By timestamping a press and the response it causes. Labs close the button contact electrically or strike it with a solenoid and time the input's arrival at a computer, film the pad and screen with a high-speed camera, or put a light sensor on the screen. **Can a 240 fps phone measure 1 ms differences?** No. One frame at 240 fps lasts about 4.17 ms, so each reading is rounded to whole frames and a 1 ms difference is about a quarter of the smallest step the camera records. **What does a photodiode input lag test measure?** On RTINGS's TV test, the time from a white square being flashed until the pixels at the center of the screen start to change. The figure describes the display alone and leaves out pixel response time. **Why do latency tests repeat a press hundreds of times?** Latency varies from one press to the next. Wimmer, Schmid and Bockes found that USB input devices differ in the shape of their latency distributions, which a single reading or a mean alone cannot show. --- # How much delay does controller polling rate add? Source: https://cronuszenlab.com/reference/controller-polling-rate-explained Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Method Published: 2026-10-10 · Updated: 2026-10-10 Tags: polling rate, usb, bInterval, dualsense, xbox series controller, cronus zen Polling adds a wait of between zero and one full interval to every button press, up to 8 ms at 125 Hz and up to 1 ms at 1000 Hz, because a report that is ready between two polls stays in the controller until the host asks again. Polling rate is how often the USB host requests a new input report. The controller's descriptor asks for an interval, and the host decides how to honor it. ## Where does the interval come from? A USB controller sends its inputs over an interrupt endpoint, and that endpoint's descriptor carries a field called `bInterval`. Microsoft's driver reference for [USB_ENDPOINT_DESCRIPTOR](https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/usbspec/ns-usbspec-_usb_endpoint_descriptor) says the field holds the polling interval for interrupt and isochronous endpoints, reflects the device's configuration in firmware, and cannot be changed by drivers. It is a relative value, and its meaning depends on the link speed. At full speed, `bInterval` counts 1 ms frames. Windows maps the requested value to a polling period with this table from the same page: | `bInterval` requested (full speed) | Period Windows uses | Rate | | --- | --- | --- | | 1 | 1 ms | 1000 Hz | | 2–3 | 2 ms | 500 Hz | | 4–7 | 4 ms | 250 Hz | | 8–15 | 8 ms | 125 Hz | | 16–31 | 16 ms | 62.5 Hz | | 32–255 | 32 ms | 31.25 Hz | At high speed the unit is the microframe, eight to a 1 ms frame, and the period is `2^(bInterval-1)` microframes. A value of 1 polls every microframe (125 µs) and a value of 4 polls every eighth one, which is 1 ms. Microsoft's high-speed table reaches its longest period, 32 microframes or 4 ms, at a value of 6 and keeps it for every value up to 255. Low-speed devices get 8 ms at the shortest. Microsoft says these mappings apply to Windows 2000 and later. Linux rounds in a similar way. The Arch Wiki's [Mouse polling rate](https://wiki.archlinux.org/title/Mouse_polling_rate) page says USB controllers round the interval down to the nearest power of two, so a 10 ms request runs at 8 ms and a 7 ms request at 4 ms. ## How the wait spreads across presses The controller's chip sees the press, builds a report and holds it until the host polls. A report that is ready just after a poll waits almost a full interval, and one that is ready just before a poll barely waits. When presses land at random points in the cycle, the added delay spreads evenly from zero to one interval: across 8 ms at 125 Hz, across 1 ms at 1000 Hz. The University of Regensburg group that built LagBox counts the polling interval as one of four contributors to a device's latency on its [project page](https://hci.uni-regensburg.de/projects/input-device-latency), next to switch mechanics, the device's microcontroller and the kernel's process-switching interval. Because the offset between the device's and the host's timing drifts, each device ends up with a latency distribution of its own. Raphael Wimmer, Andreas Schmid and Florian Bockes make the reporting point in their [CHI 2019 paper on USB input latency](https://hci.uni-regensburg.de/publications/on_the_latency_of_usb-connected_input_devices_2019): a mean and a standard deviation alone conceal the distributions that device internals and polling rates produce. ## Can the host poll faster than the controller asks? On Windows, drivers cannot change `bInterval`, per Microsoft's reference. Linux exposes overrides in its usbhid driver. The Arch Wiki says the `mousepoll` option defaults to 0, which keeps the interval the device requests, and that `jspoll` and `kbpoll` do the same job for gamepads or joysticks and for keyboards. In the kernel source ([drivers/hid/usbhid/hid-core.c](https://github.com/torvalds/linux/blob/master/drivers/hid/usbhid/hid-core.c)), all three parameters start at 0, and a non-zero value replaces the descriptor's interval only when the HID collection declares itself a mouse, a joystick or a keyboard. The switch has no case for a gamepad usage, so `jspoll` reaches a pad only if it reports itself as a joystick. The Arch Wiki adds that the xhci-hcd driver used for USB 3 ports may ignore the override, and that rates above 1 kHz need a USB 2.0 High Speed link. Forcing a faster rate helps some devices and not others. Wimmer, Schmid and Bockes found that forced polling at 1000 Hz decreased latency for some of their 36 devices but not all. Their project page reports no negative side effects for most devices, with one exception: an Xbox 360 wireless controller showed about 1 ms higher average latency when polled every 1 ms. ## Published polling rates for a DualSense and an Xbox Series controller Gamepadla measures polling with a software tool that shows how often the operating system receives reports from the USB stack, separately from its Prometheus 82 latency hardware. Every row comes from a Windows PC, so the figures describe each pad on a PC host and say nothing about how a console or a Cronus Zen polls it. Cable and Bluetooth rows as listed in October 2026, each identified by the button test number Gamepadla prints on the row (dongle rows left out): | Controller | Connection | Windows build | Median polling | Gamepadla row | | --- | --- | --- | --- | --- | | [DualSense](https://gamepadla.com/sony-dualsense.html) | Cable | Windows 11, 10.0.26100 | 249.92 Hz | #4753, 16 March 2025 | | DualSense | Cable | Windows 11, 10.0.26200 | 250 Hz | #8150, 22 February 2026 | | DualSense | Cable | Windows 11, 10.0.26200 | 250 Hz | #9164, 6 June 2026 | | DualSense | Cable, labeled OC | Windows 11, 10.0.26200 | 500 Hz | #8151, 23 February 2026 | | DualSense | Cable, labeled OC | Windows 11, 10.0.26200 | 1000 Hz | #8154, 23 February 2026 | | DualSense | Bluetooth | Windows 11, 10.0.26100 | 542.42 Hz | #4752, 16 March 2025 | | DualSense | Bluetooth | Windows 11, 10.0.26200 | 798.72 Hz | #9167, 6 June 2026 | | [DualSense Edge](https://gamepadla.com/sony-dualsense-edge.html) | Cable | Windows 11, 10.0.26100 | 986.19 Hz | #4723, 14 March 2025 | | DualSense Edge | Cable | Windows 10, 10.0.19045 | 1000 Hz | #9184, 6 June 2026 | | [Xbox Series controller](https://gamepadla.com/xbox-core-controller.html) | Cable, XInput | Windows 11, 10.0.26100 | 125 Hz | #5397, 19 May 2025 | | Xbox Series controller | Bluetooth | Windows 11, 10.0.26100 | 133.16 Hz | #5399, 19 May 2025 | On cable, the standard DualSense rows without the OC label sit at about 250 Hz, a quarter of the Edge's rate on the same kind of connection. The Xbox Series controller's 125 Hz on a PC is an 8 ms cycle, and the same 8 ms figure turns up in an [Xbox Wire post](https://news.xbox.com/en-us/2020/03/16/xbox-series-x-latency/) Microsoft published on 16 March 2020 as the interval at which earlier Xbox controllers sampled and transmitted their inputs. That post credits the Series controller's Dynamic Latency Input with sampling and sending the most recent input just ahead of the game's request. It describes the Xbox Series X console, and Gamepadla's row comes from a PC, so the two figures do not share a host. ## Two polling links through a Cronus Zen A Zen sits between pad and console: it takes in the controller's report, lets the loaded script act on it and passes its own report on. A wired pad's input therefore crosses two USB polling schedules, controller to Zen and Zen to console, and each can add its own wait of up to one interval. A wireless pad adds a radio hop on the controller side, over Bluetooth to the Zen or through a wireless adapter plugged into it. The [guide Cronus publishes](https://guide.cronuszen.com) was searched in full for this note in October 2026 and again on 14 November, and it states no polling rate for either link. Polling comes up only for third-party controllers: the [controller page](https://guide.cronuszen.com/supported-devices/controller) lists modes such as "XInput mode (Xbox 360® protocol, 250 Hz)", and setup steps include setting a GameSir G7 Pro to 250 Hz for PlayStation use. The one timing entry in its [2024 changelog](https://guide.cronuszen.com/changelogs/archive/changelog-24) belongs to firmware 2.2.8 (4 December 2024), which lists "Output protocol cycle 16 ms issue" among its fixes without saying more. Marketplace copy fills the gap without a source. An undated "wiki" article on a large online marketplace, which states that its content comes from third-party contributors or is generated by AI, claims the Zen optimizes polling from a default of 1 ms (1000 Hz) to 0.5 ms (2000 Hz). It cites nothing. A 0.5 ms period is shorter than the 1 ms frame Microsoft's tables set as the full-speed minimum, and the Arch Wiki ties rates above 1 kHz to USB 2.0 High Speed, so the claim would need a high-speed link on the console side, and no Cronus figure confirms one. ## Reading a controller's descriptor On Windows, Microsoft's [USBView](https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview) (usbview.exe, installed with the Debugging Tools for Windows option of the Windows SDK) shows the device, configuration, interface and endpoint descriptors of a connected USB device. On Linux, `lsusb` lists devices with their vendor and product IDs, and the Arch Wiki's page shows how to filter one device's descriptor down to its interval: ```bash lsusb lsusb -vd VVVV:PPPP | grep bInterval ``` The value to read sits on the endpoint whose direction is IN and whose type is interrupt. The Arch Wiki notes that it shows the interval the device requests, which may differ from the one in use. The rate a console or a Zen grants can be established only by measuring on that host. The instruments able to do that are compared in [how input latency is measured](/reference/how-input-latency-is-measured), and [the full latency budget](/reference/what-adds-controller-input-latency) places polling among the other stages. ## FAQ **What is controller polling rate?** How often the USB host asks a controller for a new input report. At 1000 Hz the host asks every 1 ms; at 125 Hz, every 8 ms. **What polling rate does a DualSense use?** On cable, Gamepadla's Windows 11 rows without the OC label read 249.92 to 250 Hz on three test dates. Its Bluetooth rows read 542.42 Hz and 798.72 Hz, and all of these describe a PC host only. **Does the Cronus Zen change polling rate?** Cronus's guide gives no polling figure for either link through the Zen, controller to Zen or Zen to console. A marketplace claim of 2000 Hz cites no source. **Does a higher polling rate always lower latency?** No. Wimmer, Schmid and Bockes (CHI 2019) found that forcing 1000 Hz polling lowered latency for some USB input devices and not for others. **How can a controller's polling interval be checked?** Read bInterval on the controller's interrupt IN endpoint with USBView on Windows or lsusb -v on Linux. That value is what the controller requests, and the host may round it. --- # What adds latency between a controller press and the screen Source: https://cronuszenlab.com/reference/what-adds-controller-input-latency Author: Dana Rehn (https://cronuszenlab.com/authors/editorial) Section: Method Published: 2026-10-10 · Updated: 2026-11-14 Tags: input lag, latency budget, controller, console, display Latency between a controller press and the screen is the sum of every stage in between, and only some of those stages have a published figure or bound. Seth Schneider's [Reflex article for NVIDIA](https://www.nvidia.com/en-gb/geforce/news/reflex-low-latency-platform/) (1 September 2020) sorts the stages into peripheral, PC and display latency. On a console, the console takes the PC's place. A pass-through device such as the Cronus Zen falls inside the peripheral segment, because the console receives the Zen's reports in place of the controller's. ## The budget, stage by stage | Stage | Segment | Published figure or bound | Source | | --- | --- | --- | --- | | Switch and controller firmware | Peripheral | No general figure. Whole-pad averages on cable, PC host: 6.50 ms for an Xbox Series controller, 7.81 to 11.3 ms for a DualSense across three dates | Gamepadla, 2025–2026 | | USB polling, wired | Peripheral | Between zero and one full interval for each press (8 ms at 125 Hz, 1 ms at 1000 Hz) | Microsoft Learn; interval arithmetic | | Wireless link | Peripheral | Bluetooth LE minimum connection interval 7.5 ms historically, 375 µs with Core 6.2 when both sides support it; no controller named. Microsoft's post gives no interval for Xbox Wireless | Bluetooth SIG; Xbox Wire | | Pass-through device (Cronus Zen) | Peripheral | No latency figure in Cronus's guide; its scripting guide asks for VM load comfortably below 80 percent | Cronus GPC script guide | | Console input handling | Console | Earlier Xbox controllers sampled and transmitted every 8 ms; Dynamic Latency Input sends the newest input just before the game asks | Xbox Wire, 16 March 2020 | | Game frame | Console | 16.7 ms per frame at 60 fps, 8.3 ms at 120 fps; going from 60 to 120 fps halves a game's internal latency | Frame arithmetic; Xbox Wire | | HDMI transmission | Display | Frame transmission cut from 16.6 ms to 8.3 ms with HDMI 2.1 | Xbox Wire | | Display processing | Display | Game Mode named the most important setting; test floor 4.17 ms on a 120 Hz TV, 8.33 ms on a 60 Hz TV | RTINGS | The stages that run on cycles of their own, polling and the game frame among them, add a wait that depends on where a press lands in the cycle. That is one reason two presses on the same setup can arrive at different times. ## Inside the controller A device's own share has four parts in the model on the Regensburg LagBox [project page](https://hci.uni-regensburg.de/projects/input-device-latency): how long the switch takes mechanically, the microcontroller's processing, the USB polling interval, and how often the host kernel switches processes. When the same group timed 36 USB input devices for a [CHI 2019 paper](https://hci.uni-regensburg.de/publications/on_the_latency_of_usb-connected_input_devices_2019), the devices differed in their means and also in the shape of their latency distributions. Gamepadla publishes whole-controller figures, all taken on PC hosts. Its Prometheus 82 rig, which presses the button with a solenoid, averaged 6.50 ms for the [Xbox Series controller](https://gamepadla.com/xbox-core-controller.html) on cable in a Windows 11 test of 19 May 2025. Its cable rows for the [DualSense](https://gamepadla.com/sony-dualsense.html) without the OC label average 7.81 ms (16 March 2025), 8.27 ms (22 February 2026) and 11.3 ms (6 June 2026), from different testers and Prometheus 82 versions. One pad moving that far between dates is a reason to read any outside figure with its date and host attached. ## Polling and the radio link On a cable, each press waits from zero to one polling interval before the host collects it. [The polling note](/reference/controller-polling-rate-explained) covers where the interval comes from and lists Gamepadla's polling figures for the DualSense and the Xbox Series pad. A radio link runs on a schedule of its own. The Bluetooth SIG's [Core 6.2 feature overview](https://www.bluetooth.com/bluetooth-core-6-2-feature-overview) says the minimum Bluetooth LE connection interval was historically 7.5 ms with a 1.25 ms resolution, and that Shorter Connection Intervals reduce it to 375 µs with a 125 µs resolution, aimed at high-performance HID devices and latency-sensitive uses such as gaming. Both peers have to advertise support; otherwise the connection stays on the baseline values. The overview names no controller, and it describes itself as a marketing document that does not override the Core Specification. Microsoft's Xbox Wire post gives no radio interval for Xbox Wireless. Gamepadla's rows of 19 May 2025 show what the radio did to one pad on a PC. The Xbox Series controller averaged 6.50 ms on cable and 12.23 ms over Bluetooth, and its button jitter rose from 2.09 ms to 3.67 ms. ## A pass-through device Every input bound for the console passes through the Zen first. The device takes the controller's report, applies whatever the active script does, and emits a fresh report over its own USB link to the console, which adds a processing stage and a second polling schedule. Cronus's guide gives no latency figure for the device. What its scripting guide offers is a budget: the [performance budget section](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/advanced-architecture/performance-budget) says to keep VM load comfortably below 80 percent, and to move work such as display rendering and full table transformations behind events or dirty flags. Cronus's [2024 firmware changelog](https://guide.cronuszen.com/changelogs/archive/changelog-24) touches timing without giving a latency figure. Under version 2.2.7 (22 October 2024) it lists PS5 driver CPU usage as improved, and among the fixes in 2.2.8 (4 December 2024) is an item titled "Output protocol cycle 16 ms issue". Elsewhere the guide lists "Ultra-low latency" among [Zen Link's features](https://guide.cronuszen.com/zen-link/what-is-zen-link), with no number attached. Zen Lab does not publish original numerical estimates for the Zen's added latency. [How input latency is measured](/reference/how-input-latency-is-measured) sets out which instruments can isolate a single stage. Troubleshooting a slow or uneven Zen chain sits in a separate guide. ## Console, game frame and HDMI Microsoft's [Xbox Wire post](https://news.xbox.com/en-us/2020/03/16/xbox-series-x-latency/) of 16 March 2020 covers the console end. It puts the input cycle of earlier Xbox controllers at 8 ms, and says that with Dynamic Latency Input on Xbox Series X the controller samples and transmits the latest input right before the game requests it. The game frame sets a floor of its own. At 60 fps one frame lasts 1/60 s, about 16.7 ms; at 120 fps it lasts about 8.3 ms. The same post says games can double their frame rate from 60 to 120 fps, which halves their internal latency. It also says HDMI 2.1 let the team cut frame transmission time from 16.6 ms to 8.3 ms, and that the console invokes Auto Low Latency Mode on capable TVs. ## The display RTINGS's [input lag test page](https://www.rtings.com/tv/tests/inputs/input-lag) (updated 3 October 2025) splits a TV's share into acquiring the image, processing it and displaying it. It names Game Mode as the most important setting for the lowest input lag and notes that many TVs offer Auto Low Latency Mode, which switches into Game Mode when a game launches from a compatible device. RTINGS singles out motion interpolation: on most TVs it cannot run inside Game Mode, so turning it on means leaving the low-lag mode. RTINGS's own figure covers the display alone. A photodiode at the center of the screen stops the clock when the pixels start to change, and pixel response time is left out. Because a TV draws from the top down, the center is reached halfway through a refresh, so the lowest figure the test can report is 4.17 ms on a 120 Hz TV and 8.33 ms on a 60 Hz one. ## FAQ **What causes controller input lag?** Every stage between the button and the screen adds some: the controller's firmware, USB polling or the radio link, any pass-through device, the console's input handling, the game frame, HDMI transmission and the TV's processing. **How long is one frame at 60 fps and 120 fps?** About 16.7 ms at 60 fps and 8.3 ms at 120 fps. Microsoft's Xbox Wire post of 16 March 2020 says doubling a game's frame rate from 60 to 120 fps halves its internal latency. **Does Cronus publish an input lag figure for the Cronus Zen?** Cronus's current guide gives none. The Zen adds a processing stage and a second USB link between controller and console, and the scripting guide sets a budget instead: keep VM load comfortably below 80 percent. **Does a wireless controller add latency?** In Gamepadla's Windows 11 tests of 19 May 2025, the Xbox Series controller averaged 6.50 ms on cable and 12.23 ms over Bluetooth, with button jitter of 2.09 ms and 3.67 ms. ---