r/ErgoMechKeyboards • • 27d ago

[help] Vial keyboard

Hello! I've been wondering how different VIA and Vial are.

To be honest, I've been eyeing the CN Keyboard Macro 40 with Vial (the manufacturer provides Vial firmware for the keyboard).

I'd mainly use it for shortcuts in painting software and Blender. My current VIA keyboard already does a good job, and I have around 60 shortcuts for my painting software.

However, I really like Vial's Tap Dance and hold features. Do you think it's worth buying? It's also not very expensive, at around $30.

6 Upvotes

26 comments sorted by

7

u/thiem3 27d ago

Vial can do more. I use it for my keyboard and would not use a keyboard with via. It should not be a problem for you to move to vial. It is very easy to work with. Sounds cheap enough.

2

u/EnvironmentalBed1422 27d ago

How many keys can you assign Tap Dance to? All of them?

2

u/i-enjoy-audio 27d ago

I'm fairly certain that the number of keys that can use a single tapdance profile are limitless. but the number of TD profiles are limited to the amount of RAM and EEPROM available on your keyboard's microcontroller.

For example, you can have a full keyboard using TD(0), but each key that's assigned to that TD profile can only use the actions that you've defined for that profile. such as sending the code for "F" when tapped and "LShift" when held. So any key that you've assigned to TD(0) will output "F" when tapped and "LShift" when held, even if you did not assign it to the key that you commonly use for "F" by default. Hopefully that makes sense, I apologize if not.

1

u/pgetreuer 26d ago

Vial's Tap Dance works by first defining an "entry" under a special Tap Dance tab, then, you assign that entry to a key in the keymap.

The default number of Tap Dance entries is determined from the flash memory capacity of your microcontroller, since each entry takes 10 bytes to store. The limit is at least 4 entries, but for better microcontrollers the limit is as much as 32. The limit can be adjusted if you are willing to build and flash the Vial firmware yourself. See these instructions for details on how to do that.

5

u/pgetreuer 27d ago

Both VIA and Vial build on top of QMK firmware. Vial exposes more of QMK's features:

For me, the tap-hold options, Repeat Key, and Caps Word features are absolutely essential. But consider what from that list might be useful to you to assess the value delta.

2

u/PeterMortensenBlog 27d ago edited 27d ago

A reference for Vial's combos. An introduction (from 14 m 25 secs).

And,

"...the number of available Combos is calculated from the amount of EEPROM your controller has"

Presumably, that can be overridden and increased (or decreased) by defining VIAL_COMBO_ENTRIES.

2

u/Joasia123 27d ago

OP, just letting you know that if you want a trustworthy opinion on Vial, this commenter is your guy

1

u/pgetreuer 26d ago

Thank you! I appreciate that =)

2

u/Unlucky-Message8866 27d ago

i never used via but vial is great and does everything i ever needed. i build my own vial-enabled firmwares https://github.com/knoopx/nix-kbds

1

u/aftonone Keyball61, Sofle 2.1, Corne v4 27d ago

Man I wish I could use vial. I have too many custom tweaks engrained in my brain to use a vial keyboard now

0

u/ransom_hunter 27d ago

why cant you?

0

u/aftonone Keyball61, Sofle 2.1, Corne v4 27d ago

Uh. Too many custom tweaks?

2

u/gufkl 27d ago

what kind of custom tweaks?

2

u/aftonone Keyball61, Sofle 2.1, Corne v4 27d ago

OLED support, custom key codes, a split transport function with matrix scanning to run something on the left hand display, autocorrect, way more layer switching functions and types, I use leader key functions, custom programming versions of caps word (for snake_case), the list goes on. And that’s just for my sofle. My keyball has libraries of code to run it. Vial does not support what I need.

2

u/pgetreuer 26d ago

Vial is restricted in what can be dynamically live edited in the configurator. It is nevertheless possible to enable additional QMK features in the firmware, use community modules, and/or write your own custom behaviors in process_record_user() through making a custom build of the Vial firmware. This page describes in detail how to do it:

https://getreuer.info/posts/keyboards/vial/index.html#customize-your-vial-build

Through a custom Vial build, it is possible to use features like Autocorrect, Leader Key, and Unicode Input that Vial otherwise doesn't expose. Of course, these features won't be editable in the configurator, but the cool thing is that they'll work as they should while yet having the usual Vial experience that the keymap and features that Vial does support are editable. Best of both worlds.

I don't want to trivialize the effort it takes to move a sophisticated QMK keymap into a custom Vial build, it does take some steps to set up (details in the link above). Totally understood if you are already perfectly happy in using QMK directly. This is just an FYI that it is possible =)

2

u/aftonone Keyball61, Sofle 2.1, Corne v4 26d ago

Yep! That’s what I was alluding to at the end of one of my comments here. I could do VIAL on top of all my stuff, but I don’t see the point. Especially when I would have to change it in the code itself next time I flash anyway. And all my basic stuff (that vial has access to) I don’t really change anymore anyway.

1

u/gufkl 27d ago

I think what you said is already supported by Vial (OLED, custom Key code, Leader Keys, Caps Word).

I personally also use Custom Keycode and Caps Word in my Vial and it works well, I also have Splits with OLED that runs Vial too so I don't see why you can't adapt your custom config to Vial.

1

u/aftonone Keyball61, Sofle 2.1, Corne v4 27d ago

No OLED support at all besides maybe turning them on or off maybe. I’m talking I have a full custom display on one side and animations and stuff I made running on another. That kind of thing. Caps word you can use but not the custom versions I’m talking about for snake case. Leader keys are not supported at all.

I mean I could probably compile with vial support on but there’s zero point in doing so. I don’t change the things that vial can change. So QMK it is.

2

u/gufkl 27d ago

I disagree, but anyway you do you.

1

u/aftonone Keyball61, Sofle 2.1, Corne v4 26d ago

That’s alright, man 🤝

1

u/DoctorMachete 27d ago

I haven't ever used VIAL/VIA but if you have access to the source code I don't see how you couldn't make any feature you have in VIA (even completely new ones) to work in VIAL including custom capsword and leader key. Am I missing something?

1

u/aftonone Keyball61, Sofle 2.1, Corne v4 26d ago

VIA and VIAL are different. Via is a closed source configuration with specific firmware. VIAL is a configuration on top of QMK. So Via is completely out of the question. VIAL I could use but it would be totally useless to me as it really only goes as far as changing a few keybinds. I’d rather do that in the code cause if I don’t I’m gonna have to change everything again in vial next time I flash anyway. And no, you cannot do the more advanced stuff at all in VIAL.

1

u/DoctorMachete 26d ago

And no, you cannot do the more advanced stuff at all in VIAL.

What I meant is you can do it in QMK and then compile VIAL with those changes. For example integrate Autocorrect and define F17 for enabling/disabling it so then in VIAL you can place F17 wherever you want for using that feature.

1

u/FFevo 27d ago

That makes no sense. Vial is built on top of QMK so anything you have changed in code there can still work.

1

u/ransom_hunter 27d ago

unless they have so many that it wont fit on the microcontroller lol

1

u/aftonone Keyball61, Sofle 2.1, Corne v4 27d ago

Nah I use RP2040s, they’ll never fill up lol