Inline Keycode Converter

[tbc]

I have a feeling this is very common, but I'm interested in an adapter that will can remap my keypresses into other keys or macros.

basically, it is a hardware version of AHK.  hopefully without the lag.

miniusb out from keyboard -> usb into converter -> microusb out from adapter -> usb into computer.

[GiraffePencils]

I don't really see how this would hope to work without lag,

Have you thought of a custom layout in windows for the Keyboard, instead of using a standard and AHK to change it?

[dorkvader]

This is possible from PS/2 of course with a soarer. Having a USB one would be sweet though (how much does a QIDO cost?)

I believe TWK_firmware has had beta support for usb, but it's experimental.
https://github.com/tmk/tmk_keyboard/tree/master/converter/usb_usb

[orihalcon]

Yep, Soarer's Converter will work with anything that is PS/2 capable to remap your keys.  Some USB keyboards are PS/2 compatible as well, like most Filco ones.  Anything that can use a USB to PS/2 adapter and most that claim to have full NKRO as that is usually only possible over PS/2. 

[engicoder]

I have a feeling this is very common, but I'm interested in an adapter that will can remap my keypresses into other keys or macros.

basically, it is a hardware version of AHK.  hopefully without the lag.

miniusb out from keyboard -> usb into converter -> microusb out from adapter -> usb into computer.

The issue here is that in order to receive the reports from the keyboard, the converter has to support USB Host. The AVR microcontrollers used most commonly here have hardware support for USB Device, but no support for Host. In order to create such a converter with these microcontrollers, the USB Host has be done completely in software. Hasu has some done some work (as dorkvader linked) that supports HID boot, which is a simpler subset of the full HID keyboard, making it more feasible to implement on the AVR.

Some of the larger AVRs do support USB OTG (i.e AT90USB647/1287), so one of these could be used and the device side done in software. Another method would be to use two AVRs, one for device and one for host, but I am not sure there is enough demand. The functionality of such a hardware converter would be similar to existing software solutions and does not provide the same level of programmability as a custom keyboard controller.