Set up a repeatable comparison
Choose a game menu or practice screen that reacts in a recognizable way to a single press. Keep the game mode, display settings, controller, wired or wireless connection and recording equipment the same. Test the direct controller first. Repeat through Titan Two using a neutral slot so no script timing becomes part of the comparison.
The Gtuner IV Device Monitor can help check whether an input is arriving and whether the outgoing action matches. It observes controller signals and does not include the game’s rendering time or the display’s response.
Measure and report the limits of the result
If your camera has a high-speed mode, record the physical button and the same part of the display in one shot. Count frames between the observed press and the first visible response. At 240 frames per second, a frame represents roughly 4.2 milliseconds. Treat the result as an estimate because the press and display update may occur between recorded frames.
Repeat both configurations several times and report the typical result and variation. Keep preview-based measurements separate from direct-display measurements. If one path uses a capture preview or Remote Play, its buffering or network transport is part of the result. A difference smaller than the camera’s frame interval is difficult to resolve with this method.
Keep a small trial log
Record the path, camera rate, game screen, display mode and result for each run. Use the same physical action and visible response for both conditions. If a trial includes an accidental double press or a menu transition, set it aside and explain why. A short log makes a later repeat more useful than a single best result.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.