Experience direct touchpad telemetry with RawInput Touchpad, by emoacht, a utility that captures low-level input from Windows Precision Touchpad (PTP) hardware for developers and power users. The app reads raw contact data, tracks multiple finger coordinates, and reports contact, motion, and lift events in real time using the Windows Raw Input API, bypassing high-level gesture preprocessing. It supports multi-finger tracking, PTP-specific handling, and an open-source example codebase. Targeted at developers and enthusiasts who need granular touch data for debugging, custom gesture prototyping, or hardware validation.

What data does the tool capture from a PTP?

The tool reads raw touch events exposed by Precision Touchpad hardware, including individual contact points, per-finger coordinates, and contact state over time. It reports multi-finger positions and sequences for contact, motion, and lift, producing time-stamped coordinate streams that developers can parse. Use cases include custom gesture detection, telemetry for hardware validation, and exporting contact logs for offline analysis.

Does it slow down the system during monitoring?

Designed as a lightweight utility, the implementation uses the Windows Raw Input API rather than persistent kernel drivers. Many distributions are portable executables, so the app reads events in user space and avoids installing device stacks. That approach reduces runtime persistence and keeps the utility suited to side-by-side diagnostics without adding permanent system components to a desktop.

Is it safe to inspect touch input on a production machine?

Transparency is a core attribute: the project is open-source, which permits code inspection and community review. The app collects input via the Raw Input API instead of replacing vendor drivers, and common releases avoid installer-based deployment. These factors increase auditability and limit permanent changes to a machine, important considerations when adding a diagnostic tool to a live workstation.

Do I need developer skills to use and extend the tool?

Yes, the target audience is developers and power users rather than casual end users. The open-source codebase includes a clear implementation example to jumpstart custom work. Mapping raw multi-finger data into actions or creating five-finger gestures requires configuration or source edits, and that capability depends on the chosen release and the user's willingness to modify example code.

Best suited to developers and testers; not aimed at casual gesture tuning

The tool is a practical choice for developers and hardware testers who need inspectable access to PTP event streams and example code to build on. For a smooth workflow, run it on a test device and use the included implementation as a starting point for gesture prototypes. Trade-off: users seeking a graphical, out-of-the-box gesture mapper must supply additional tooling or custom development.