TitanCSA

Architecture / Input and virtual devices

Interception, virtual devices and diagnostics solve different problems.

Choose the boundary your application needs before choosing a package name.

TitanCSA project documentation · Checked 18 November 2026 · AI-assisted maintenance

You already have a physical input device

An input filter is relevant when you need to receive, transform, block or forward events from a supported existing keyboard, mouse or gamepad. The Interceptor family has combined and specialized editions with separate SDKs, product masks and installers.

The diagram is a conceptual workflow, not a complete PnP stack diagram or a timing measurement. Actual HID, XUSB, XInputHID and GIP paths differ. You need evidence that the chosen device traverses the filter and that an independent consumer observes the intended change.

IntegrationStarting point
Keyboard and mouseInterceptor Keyboard & Mouse
Supported gamepad reportsInterceptor Gamepad & Controller
Combined input APIInterceptor
Historical Interception C APIInterception V2, using its matching files and documented compatibility scope
Per-device AutoHotkeyAutoHotInterceptor, adapted from evilC's AutoHotInterception

A package wrapper does not extend the underlying driver's hardware support. Keep the product edition, native architecture and bindings consistent. Follow the selected release's explicit capture/start/stop and removal instructions.

You need Windows to see a new device

Vdevice exposes a raw C++ SDK for virtual USB devices. A producer defines descriptors and exchanges reports or control data through the device contract. Windows then uses the appropriate device stack and observation API.

Creating a virtual controller does not intercept an unrelated physical controller. Changing a VID/PID is not an implementation of an entire firmware protocol. A successful send call is not proof that the target application consumed the report.

The public lab demonstrates selected vendor-HID, keyboard/mouse, XUSB, DS4, GIP and joystick paths. Its evidence is protocol-specific and virtual-only. Read the actual per-protocol results rather than inferring support from an example filename.

Open Vdevice stability finding: repeated controller/filter trials reproduced a guest WDF queue-purge crash. WDF-001 remains unresolved. Successful completed rows do not qualify repeated teardown.

You need evidence before you change behavior

Start with a read-only diagnostic or an explicit test fixture. Driver Readiness Inspector explains reported PnP/package/service evidence. Controller Repair Bench observes selected axes and report cadence. Input CI Runner validates fixture data before an optional live path.

Device hiding is another distinct job: deciding which applications can open a device is not equivalent to rewriting its reports. An already-open handle and a new open may also have different access behavior. Choose the documented access-control tool when that is the actual requirement.

Three checks before a live test

  1. Match the contract. Identify the product edition, device profile and receiver API.
  2. Match the rights and prerequisites. Check Windows build, architecture, driver package and evaluation/licence terms.
  3. Observe the result. Validate enumeration, attachment when filtering, and independently received content. A service being present is not enough.

Use the documented recovery procedure and an appropriate lab for driver experiments. Do not disable the protections of an ordinary workstation to make an unsupported configuration work.