InputConfig vs JoyShockMapper

InputConfig maps controllers and a Mac’s keyboard, mouse, and trackpad to keyboard and mouse actions across macOS apps. It supports DualSense, DualSense Edge, DualShock 4, Xbox, Switch Pro, Joy-Cons, Stadia, 8BitDo, Steam Controller, and MFi or HID gamepads. Mappings can trigger keystrokes, clicks, pointer movement, scrolling, typed phrases, macros, MIDI notes, and system functions, including hold, double-tap, chord, and turbo actions. InputConfig can also send MIDI notes, control changes, and pitch bend through a virtual MIDI port for GarageBand, Logic, and other DAWs. The editor offers per-app profiles and profile switching, along with more than 450 presets for games, apps, and workflows. The maker describes accessibility support for adaptive controllers, one-stick driving, spoken feedback, dictation, and zoom. InputConfig is free and open source under the MIT license. It requires macOS 14 or later and supports Apple silicon and Intel Macs. Virtual-controller output is not available.

JoyShockMapper maps game controller input to keyboard, mouse, or virtual controller events for PC games. It supports gyro controls and flick stick for aiming and turning. Buttons can map to keyboard or mouse inputs with tap-and-hold, chorded, and simultaneous-press options; stick modes can control the mouse or trigger keys, including scroll-wheel and flick-stick modes. The project describes support for DualSense, DualShock 4, paired JoyCons, and Nintendo Switch Pro Controller. It loads commands from text configuration files, and its download includes example gyro configurations. JoyShockMapper is free, with a Windows release and Linux builds available from source. Development primarily targets Windows, and Linux builds may not always work. Linux use requires read and write access to /dev/uinput and the relevant /dev/hidraw device; focused-window detection works only on X11. Virtual Xbox or DS4 output requires separate ViGEm bus software. The releases page lists v3.6.1 as the latest release.