r2024-04-19

This release fixes an issue with the custom usages when more than one device was connected.

When updating a dual Pico HID Remapper or any of the custom boards that have two RP2040 chips, make sure to also flash B side firmware (you should always be doing it anyway).

r2024-04-09

• Custom usages (user-defined quirks) allow you to work around issues with report descriptors on certain devices without having to recompile the firmware. For example you can use them to access things like touchpad data on a DualSense controller.
• Mappings with both sticky and hold flags now work. For example you could use them to activate drag-lock on the left mouse button by holding it for a moment, while still having it work as a normal button via a separate "tap" mapping.
• Mappings with registers as inputs now respect layers.
• Registers now work as inputs on layer-triggering mappings.
• Scaling is now applied to mappings that have an absolute usage as their input, including expressions and registers.
• Custom board v8 doesn't have USB inputs, but has a single 3.5mm TRRS jack that can be used for analog inputs. For example you could use it to add analog joystick inputs to your PC or a Hori Flex controller. The jack can also be used for one or two digital inputs like buttons or switches. The firmware file for custom board v8 can also be used with a Pico board, with analog inputs on pins 26 and 27.
• Line breaks in expressions are now preserved when saving/loading the configuration.
• New emulated device type: Stadia controller. It's similar to the previously available gamepad modes, but has the advantage of showing up with the correct button/axis mapping in Android, Chrome, Steam, etc.
• The Monitor tab now shows which hub port the inputs come from.
• Zero values are now sent correctly to digital potentiometers on the v7 board.

r2024-02-14

This release adds support for HID Remapper custom board v7, which can be used to add USB inputs to the PlayStation Access controller and other similar devices.

There are no other changes.

r2024-01-10

• Mappings that trigger a macro and have the "hold" flag set should now work correctly (#48, #106).
• When changing the emulated device type, HID Remapper will now stop sending inputs until the user reconnects the device and the new device type becomes active.
• Keyboard rollover should now be handled correctly (#70).
• Some weird report descriptors should be handled better now (#97).
• A bug that caused certain macros to be corrupted when loading config back from device should now be fixed.

r2024-01-03

• Per-device mappings. You can now configure a mapping to only apply to a device connected to a certain port on a USB hub and have separate mappings for different devices.
• "DPAD" expression operation. This simplifies the expressions needed to map four keys or buttons to a game controller d-pad. For example to make the arrow keys on a keyboard work as a d-pad you might use an expression like this:

0x00070050 input_state_binary
0x0007004f input_state_binary
0x00070052 input_state_binary
0x00070051 input_state_binary
dpad

• Single Pico variant is again a "copy-to-RAM" binary, with some parts of the code kept in flash to save memory.

r2023-12-13

• Inputs like analog sticks, triggers and d-pads can now be mapped directly without having to use expressions. Unmapped inputs passthrough now also works for them. (You might still need to use expressions, depending on what you want to map them to.)
• Added a firmware build for the Waveshare RP2040-PiZero, which is an affordable board with a second USB port, ready to use with HID Remapper. You might need a USB C-to-A adapter.
• Reintroduced a check to prevent macros from overflowing the output queue in certain situations.
• Added quirks for SpaceMouse Compact and Pro, making it more straightforward to remap them.
• Single Pico variant binary is no longer "copy-to-RAM", which was a legacy leftover.

r2023-11-15

• GPIO outputs now have a second mode where an output value of "1" sets the pin to low and an output value of "0" sets the pin to high impedance. This should help with using the outputs as inputs on another device like the Xbox Adaptive Controller without additional hardware.
• Macros now have a configurable step duration (1-256ms). This should help for use cases other than text input.
• GPIO outputs now work in macros.

r2023-11-08

This release adds the possibility to set GPIO pins as outputs on a mapping.

An output value of "0" drives the pin low and an output value of "1" drives the pin high. You can use it directly with LEDs, for example to make a CapsLock LED or to visualize layer state. If you want to use the outputs to drive other devices like the Xbox Adaptive Controller, you should probably use additional hardware such as optocouplers.

Also all GPIO pins that aren't used for other functions should now be usable as inputs/outputs (previously limited to GPIO2-GPIO9).

r2023-10-18

• MIDI inputs over USB are now supported. Notes, CCs, aftertouch, program, and pitch bend can all be mapped.
• Monitor tab now has "map this" buttons that create a new mapping for that usage.
• JSON files can have custom names for inputs, which might be helpful for configurations that map devices that aren't mice/keyboards. See the Xbox controller mappings in the Examples tab. The names are not stored on device.

r2023-10-11

This release adds support for Xbox One/Series controllers connected over USB, including the Xbox Adaptive Controller.