Is USB_to_USB converter by Hasu supported?

[bogorad]

It's definitely supported by QMK (converters/usb_usb/hasu). What steps do I need to take to compile Miryoku for it?

[manna-harbour]

First, for row stagger, there are 3 options. See https://github.com/manna-harbour/miryoku_qmk/tree/miryoku/users/manna-harbour_miryoku#60_ansi for details. So you need to decide on one or more of those options.

https://github.com/qmk/qmk_firmware/tree/master/keyboards/converter/usb_usb/keymaps/manna-harbour_miryoku/config.h needs to be created, based on https://github.com/qmk/qmk_firmware/blob/master/keyboards/converter/usb_usb/keymaps/default/keymap.c and https://github.com/manna-harbour/miryoku_qmk/blob/miryoku/layouts/community/60_ansi/manna-harbour_miryoku/config.h. See #264.

Also see #287.

As an alternative to Miryoku QMK on a usb-usb converter, see https://github.com/manna-harbour/miryoku_kmonad and https://github.com/manna-harbour/xmk.

[manna-harbour]

See https://github.com/qmk/qmk_firmware/blob/master/docs/squeezing_avr.md.

In this case, the custom matrix is extremely large, so reducing the size of the matrix, or reducing the number of layers should help. You could first try adding or removing a layer from the default keymap to see if it's significant.

For Miryoku you can leave out unused layers. See #85.

For your layout, half the matrix rows are unused, so you could modify the custom matrix code to skip those.

Otherwise, Miryoku QMK has a few QMK features enabled that aren't critical and could be disabled, e.g. by editing https://github.com/manna-harbour/miryoku_qmk/blob/miryoku/users/manna-harbour_miryoku/rules.mk and https://github.com/manna-harbour/miryoku_qmk/blob/miryoku/users/manna-harbour_miryoku/manna-harbour_miryoku.c.

[manna-harbour]

Or use the approach from https://github.com/qmk/qmk_firmware/tree/master/keyboards/converter/xmk, and have the matrix represent only the keycodes used for input.

[bogorad]

Thanks! I decided to put this on hold until I better understand QMK. I'll be back with more questions :)

[bogorad]

Well, I felt comfortable enough to start rebuilding it from the ground up, and realized that the moment I enable both tap-dance and combos, I run out of space. Oh well. I'll just have to wait for the pcbs/chips for Kint to arrive.

Thanks again for your assistance!

[manna-harbour]

Changing the MCU will be the best option in general.

Tap dance is only used for the double tap guard, so that can be removed.

If you want to try the converter/xmk approach, you'd add a mapping array to map from input keycode to keymap key position, equivalent to the layout macro in the usb converter config.