roze.ma

I’ve been using the MISTEL Barocco MD600 Alpha as my daily driver for a few years now. The split ergo form factor is genuinely great. I type on it all day across three machines — a Linux box, a Mac, and a Windows PC — switching between them over Bluetooth. The build quality is solid, the Cherry switches feel good, and the curvy Alice-style layout actually reduces strain.

The programming experience, on the other hand, is a piece of shit.

I’m not being hyperbolic. The on-keyboard programming interface for remapping keys is so fragile that a fast typing burst can accidentally throw you into macro recording mode, silently corrupt your layer, and leave you wondering why your Ctrl key is now producing semicolons. I’ve lost count of the number of times I’ve had to do a full reset and reprogram the thing from scratch.

So I finally sat down, documented every step, explored every dead end, and built myself a repeatable procedure. I’m posting it here in case other MD600 Alpha owners are losing their minds the same way I was.

What I want the keyboard to do

Three remaps. That’s it.

Caps Lock → Fn. Nobody needs Caps Lock. You use the Fn key constantly on a 60% board. Move it to the home row where it’s actually reachable.

Corner key → Ctrl. Nobody puts function key in the corner. (Nobody puts baby in the corner.) Ctrl belongs there.

Fn+Backspace → Delete. Because the board doesn’t have a dedicated Delete key and Fn+Backspace is the obvious place for it.

These are not exotic requests. This is basic ergonomic customization for a keyboard that advertises full programmability.

The dead ends I explored so you don’t have to

The MD600 Alpha got a firmware update (v1.2.06, now at v1.3.02) that added DIP Switch 4, which swaps the physical Fn and Ctrl keys at the hardware level. This sounds perfect — a hardware swap can’t be accidentally deprogrammed. I got excited. I spent 30 minutes flipping DIP switches and testing combinations.

It’s a dead end. Here’s why:

DIP 4 disables DIP 2 and DIP 3. The manual actually says this, buried in a footnote. So you can’t combine the Fn/Ctrl hardware swap with the Caps Lock/Fn hardware swap.

DIP 4 blocks Caps Lock as an Fn remap target. When DIP 4 is ON and you enter the Fn remap mode, the keyboard only offers Ctrl, Tab, and R_Win as valid destinations. Caps Lock isn’t lit. It’s not an option. This is documented nowhere.

DIP 2 doesn’t help either. Even with DIP 2 swapping Caps Lock and Fn at the hardware level, the macro engine still internally considers the corner key to be “Fn” — and Fn is on the prohibited key list for macro remapping. The DIP switch changes what the key sends, not what the programming engine thinks it is. So the corner key goes dark in macro mode and won’t respond. Also documented nowhere.

I also looked at OS-level solutions. Microsoft PowerToys can remap Caps Lock to Ctrl through a nice GUI. But my keyboard connects to three different machines over Bluetooth — a Linux box, a Mac, and a Windows PC. I’m not maintaining three separate OS-level remap configs across three different operating systems just because Mistel can’t write a decent firmware interface. The keyboard should do its job.

QMK/VIA? Nope. The MD600 Alpha runs proprietary firmware. People have been asking about QMK support on GitHub for years. It’s not happening.

What actually works

All DIP switches OFF. Pure on-keyboard software remaps. No shortcuts, no hardware assists, no OS-level hacks. The only approach that actually works is the one I was doing from the beginning — I just needed to do it right and document it so I could repeat it without losing my mind.

The trick is that the Fn key remap (moving Fn to Caps Lock) must happen first, using the special Fn remap mode — not macro mode. Once Fn moves away from the corner, the corner key becomes a Menu key, which is allowed in macro mode. Then you can remap it to Ctrl. Order matters.

I program all three layers identically with a color-coding scheme: Layer 1 is blue (chill, normal operations), Layer 2 is yellow (not in trouble yet, but something broke), and Layer 3 is red (defcon 1). When a typing fury corrupts Layer 1, I switch to Layer 2 and keep working. RAID for your keyboard.

The Zen Unfuck the KBD procedure

Here’s the full sequence. I keep a printout of this next to the keyboard.

Phase 1: Nuclear reset

Hold both Alt keys for 1 second. Everything wipes. Keyboard resumes in rainbow mode.

Phase 2: Color-code the layers

Using Pn (right-side Windows key) + 4 to cycle effects and Pn + 1/2/3 to adjust RGB. Default layer gets white (pure, untouched). Layer 1 gets blue. Layer 2 gets yellow. Layer 3 gets red.

Phase 3: Fn remap on all 3 layers

Select a layer (Fn+S/D/F). Hold Fn + L_Shift until the white light blinks. Tap the corner Fn key — function keys light up blue. Press Caps Lock — colors change back to the layer color. Done.

Do NOT press Caps Lock a second time. That undoes the remap. Just move on.

Repeat for all three layers.

Phase 4: Corner key to Ctrl on all 3 layers

Select a layer. Right-side Fn + L_Ctrl to enter macro mode (keyboard turns green). Press the corner key — starts blinking, turns red. Press L_Ctrl — blinks with the white light. Right-side Fn + Tab to save. Right-side Fn + L_Ctrl to exit. Now you have two Ctrl keys.

Repeat for all three layers.

Phase 5: Fn+Backspace to Delete on all 3 layers

Same macro mode entry. Press Fn + Backspace (source). Press Fn + Del (destination). Save and exit.

Repeat for all three layers.

Phase 6: Test

Ctrl+C, Ctrl+V, Fn+IJKL for arrows, Fn+Backspace for Delete. On every layer.

When it breaks again

And it will.

Switch to the next layer (new Fn + D for yellow, new Fn + F for red). Keep working. When you have a calm moment, reset the broken layer (new Fn + R, hold 1 second) and redo Phases 3–5 for that layer. The whole single-layer recovery takes about 2 minutes with the cheat sheet in front of you.

If all three layers are toast, start from Phase 1. Pour yourself something. Embrace the zen.

The real problem

The MD600 Alpha is a good keyboard with a terrible programming interface. The macro mode entry combo (Fn + L_Ctrl) is right next to keys you actually use, which means fast typing can and will accidentally trigger it. There’s no confirmation prompt, no undo, no “are you sure?” — just silent corruption. The DIP switches that were supposed to help are full of undocumented interactions that make things worse. And the documentation itself is a mix of incomplete English, untranslated Chinese, and firmware-version-specific behaviors that nobody bothered to note.

I like the form factor enough to keep using it. But I shouldn’t need a battle-tested recovery procedure and three redundant layers just to maintain a basic keyboard layout. Mistel, if you’re reading this: give us a desktop configurator. Or at least a firmware option to lock out programming mode. The hardware is great. The software experience is not.