I want a split keyboard like quefrency but with encoder and oled just like satisfaction75

Left using teensy++ 2.0 right using pro micro. I want a lot of feature but the pro micro firmware max size is limitting me from adding aditional feature. So I think of mixing different board. And it works. I almost never using the macro key on the left side and I want a dedicated encoder instead of changing layer encoder. And changing layout to make it easier for me to search for keycaps set. build log and the firmware coming soon.

This is my first time building custom handwired keyboard, even though someone else guide me to build this keeb. some mistakes were made, buying wrong part, buying unnecesery part to reach the minimum free shipping terms. buying to many part because the seller only sell in pack and so on. the cost not include the shipping cost, some part get free shipping some part don't. the cost not including the tool to build this keeb, like solder, soldering iron, caliper, multimeter and etc.

the encoder have layers, you can change it to media layer, scrolling layer, backlit layer and brightness layer. To change encoder layer,simply press fn1+encoder. to change base layer like qwerty and so on use fn2+encoder.

in media layer when you press the encoder it is a toogle button play pause KC_MPLY. when you turn the encoder clockwise and cc, it is acting as volume up and down (KC_VOLU,KC_VOLD). but when you turn the encoder while holding fn1 or fn2 it is acting as next and previous/fast forward and rewind button. my idea is awesome right? haha. explaining it in my non native lang is hard, just see my code.

void handle_encoder_switch(void){
    if(ENCODER_MODE == media){
        tap_code(KC_MPLY);
    }
    ...
}
void handle_encoder_media(bool clockwise, bool fn1, bool fn2){
    if(clockwise){
        if(fn1){
            tap_code(KC_MNXT);
        }else if(fn2){
            tap_code(KC_MFFD);
        }else{
            tap_code(KC_VOLU);
        }
    }else {
        if(fn1){
            tap_code(KC_MPRV);
        }else if(fn2){
            tap_code(KC_MRWD);
        }else{
            tap_code(KC_VOLD);
        }
    }
}

the idea is the same as media layer, when in this layer, the encoder button will act as ... just see my code

void handle_encoder_switch(void){
    ...
    else if(ENCODER_MODE == backlit) {
        rgblight_step();
    }
    ...
}
void handle_encoder_backlit(bool clockwise, bool fn1, bool fn2){
    if(clockwise){
        if(fn1){
            rgblight_increase_hue();
        }else if(fn2){
            rgblight_increase_sat();
        }else{
            rgblight_increase_val();
        }
    }else {
        if(fn1){
            rgblight_decrease_hue();
        }else if(fn2){
            rgblight_decrease_sat();
        }else{
            rgblight_decrease_val();
        }
    }
}

it is just brighness nothing else

void handle_encoder_scroll(bool clockwise, bool fn1, bool fn2){
    if(clockwise){
        if(fn1){
            tap_code(KC_WH_R);
        }else if(fn2){
            tap_code(KC_WH_R);
        }else{
            tap_code(KC_WH_D);
        }
    }else {
        if(fn1){
            tap_code(KC_WH_L);
        }else if(fn2){
            tap_code(KC_WH_L);
        }else{
            tap_code(KC_WH_U);
        }
    }
}

I want the same firmware as satisfaction75 the oled display is awesome, but I can't. So I use font image edit font using https://helixfonteditor.netlify.app/

nothing awesome about this

The base layer is just switching between qwerty mac and qwerty windows by pressing fn2+encoder, I can add another like dvorak colemak and etc but I don't want to learn them.

Edit this layout in https://www.keyboard-layout-editor.com

more photos at https://imgur.com/gallery/rXZYqem

communication protocol is serial using D3 pin, the LED Din pin use B5 pin, the right halve encoder connected to the i2c pin D1 and D0 so I have to disable the oled driver on the right halve to use encoder, and I can't use the Oled display if the right side is the master, always use left as master.

there is only 1 pin left, B5. I intend to use it for buzzer but the maximum size of pro micro firmware not allow me to add this feature :'(.

This is my first custom keyboard and it is a handwired. I am too excited to finish this keeb ASAP so I don't document my build. but here are some pictures of my build without timestamp.

trying the switch on the double layer plate acrylic (1.5mm+3mm). It is fit and click without adding some glue. the doubleplate acrylic idea by @dayatz

at first it looks good

adding the pro micro, trrs, led and etc. Disgusting wiring.

this is suppose to be underglow

I trust my ability so no need to test it on breadboard.

I am learning so much by building this keyboard, at first it confusing, but once you understand how it works, you can build it faster. I am not satisfied yet with this keyboard, I will upgrade the mcu and other part. just wait for rev2. forgive my typo and bad grammar,I try my best.

Thanks for member of Indonesian Mechanical Keyboard Group. Thank you so much @herpiko for the inspiration and the thorough guide, @dayatz for the double layer acrylic plate desain so I can reduce the cost. thanks @sendz for open sourcing his acrylic case design so I can learn to make my own version. Thanks for the qmk discord member for helping with some issue.