Skip to content

Releases: mymakercorner/nazg

v0.1.0-test.5

v0.1.0-test.5 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Oct 19:48

Fifth test build of Nazg -- a keyboard configurator for VIA and Vial keyboards, for
Windows, Linux and macOS, and now in your browser too. Shared so people can try it on their
own keyboards before a first public release; expect rough edges, and please report them.

In a browser, nothing to install -- mymakercorner.com/nazg,
in Chrome, Edge or Opera on a computer (Windows, macOS or Linux). Click Add a keyboard...,
pick yours in the browser's list and click Connect; the browser remembers it for next time.
Firefox and Safari cannot reach keyboards, nor can phones. On Linux the browser needs the keyboard
allowed, as the desktop app does: allow it once with the desktop app's Allow....

Windows 10/11, 64-bit -- nazg-0.1.0-test.5-windows-x64.zip. Unzip and run nazg.exe;
nothing is installed. The build is not signed yet: if Windows says "Windows protected your PC",
click "More info", then "Run anyway".

Linux, x86-64 -- nazg-0.1.0-test.5-linux-x86_64.AppImage, one file for most distributions
(Debian 10+, Ubuntu 20.04+, Fedora, RHEL / Rocky 8+, Arch...). Make it executable and run it:

chmod +x nazg-0.1.0-test.5-linux-x86_64.AppImage
./nazg-0.1.0-test.5-linux-x86_64.AppImage

or allow it to run as a program in your file manager's Properties. No libfuse2 needed. It needs
a Vulkan driver, which any recent Mesa or NVIDIA driver has.

macOS, Apple Silicon (M1 or later), macOS 11+ -- nazg-0.1.0-test.5-macos-arm64.zip. Unzip
it and open Nazg. The app is not signed by Apple yet, so the first time macOS refuses to open
it: close that message, open System Settings > Privacy & Security, click Open Anyway
beside Nazg, and confirm. macOS remembers.

The user manual -- nazg-0.1.0-test.5-manual.html, one page to open in any browser. The
Windows zip carries it too.

New since 0.1.0-test.4

  • Nazg in your browser, at mymakercorner.com/nazg: the same
    app, every section included, running in Chrome, Edge or Opera. Seen working on a Vial board (the
    unlock, the key test, keymap changes, Leyden Jar diagnostics) and a VIA board (a definition
    imported, layouts saved and loaded), with no difference in speed from the desktop app.
  • In the browser, Import a definition..., Load from file..., Save to file... and
    Export definition... use the browser's own file picker and downloads.
  • The user manual has a new section, "In a browser".

What it does

  • Vial keyboards describe themselves and just work.
  • VIA keyboards: ships VIA's whole official registry (3513 definitions) and 737 community
    definitions vendors publish for boards VIA lacks
    (nazg-community-definitions).
    Any other board: import the via.json your vendor provides.
  • Keymap and knobs, layouts, QMK settings, lighting, audio, and a board's own menus (VIA V3) --
    written to the keyboard as you change them. Macros, tap dance, combos, key overrides and alt
    repeat keys -- written when you press Save.
  • Saved layouts in Vial's .vil format, read from and written to any board; the VIA app's
    .layout.json files load too.
  • Under Tools: the key test, the Device section (bootloader, keymap reset), and Diagnostics for
    Leyden Jar controllers (Model F Labs keyboards).

Known limits

  • The browser version: your settings and imported definitions are kept by the browser, one
    set per browser; a tab in the background pauses work on the keyboard, so keep it in front.
  • macOS has never been tried on a real Mac. Reports are especially welcome: whether it opens,
    the window, whether your keyboard is listed and opens, and whether macOS asks to allow "Input
    Monitoring" or anything else.
  • Linux: Allow... (for a keyboard Linux has not allowed yet) has only been tried in WSL. If
    your keyboard shows "not allowed", please say how Allow... went.
  • Not yet tried on real hardware: alt repeat keys, audio, Vial's knobs drawn as two direction keys.

Reporting

Open an issue with your keyboard, whether it runs
VIA or Vial, your system (Windows, macOS, or which Linux and desktop -- or which browser), and what
you did. Settings shows Nazg's version and its definitions.

v0.1.0-test.4

v0.1.0-test.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 24 Oct 16:01

Fourth test build of Nazg -- a native keyboard configurator for VIA and Vial keyboards, now
for Windows, Linux and macOS. Shared so people can try it on their own keyboards before a first
public release; expect rough edges, and please report them.

Windows 10/11, 64-bit -- nazg-0.1.0-test.4-windows-x64.zip. Unzip and run nazg.exe;
nothing is installed. The build is not signed yet: if Windows says "Windows protected your PC",
click "More info", then "Run anyway".

Linux, x86-64 -- nazg-0.1.0-test.4-linux-x86_64.AppImage, one file for most distributions
(Debian 10+, Ubuntu 20.04+, Fedora, RHEL / Rocky 8+, Arch...). Make it executable and run it:

chmod +x nazg-0.1.0-test.4-linux-x86_64.AppImage
./nazg-0.1.0-test.4-linux-x86_64.AppImage

or allow it to run as a program in your file manager's Properties. No libfuse2 needed. It needs
a Vulkan driver, which any recent Mesa or NVIDIA driver has.

macOS, Apple Silicon (M1 or later), macOS 11+ -- nazg-0.1.0-test.4-macos-arm64.zip. Unzip
it and open Nazg. The app is not signed by Apple yet, so the first time macOS refuses to open
it: close that message, open System Settings > Privacy & Security, click Open Anyway
beside Nazg, and confirm. macOS remembers.

The user manual -- nazg-0.1.0-test.4-manual.html, one page to open in any browser. The
Windows zip carries it too.

New since 0.1.0-test.3

  • macOS. A first build for Apple Silicon Macs. It has never been opened on a Mac yet:
    whether it starts, draws its window and sees your keyboard is exactly what this build is for.
  • A user manual, with screenshots: getting started on each system, every section, what to do
    when something goes wrong.
  • Linux seen working on a real desktop (KDE, a Keychron board): starting, changing keys, the
    key test. Thanks to the tester.
  • Behind the scenes: every change to Nazg is now built and tested on Windows, Linux and macOS by
    GitHub, and this release was built there too.

What it does

  • Vial keyboards describe themselves and just work.
  • VIA keyboards: ships VIA's whole official registry (3513 definitions) and 737 community
    definitions vendors publish for boards VIA lacks
    (nazg-community-definitions).
    Any other board: import the via.json your vendor provides.
  • Keymap and knobs, layouts, QMK settings, lighting, audio, and a board's own menus (VIA V3) --
    written to the keyboard as you change them. Macros, tap dance, combos, key overrides and alt
    repeat keys -- written when you press Save.
  • Saved layouts in Vial's .vil format, read from and written to any board; the VIA app's
    .layout.json files load too.
  • Under Tools: the key test, the Device section (bootloader, keymap reset), and Diagnostics for
    Leyden Jar controllers (Model F Labs keyboards).

Known limits

  • macOS has never been tried on a real Mac. Reports are especially welcome: whether it opens,
    the window, whether your keyboard is listed and opens, and whether macOS asks to allow "Input
    Monitoring" or anything else.
  • Linux: Allow... (for a keyboard Linux has not allowed yet) has only been tried in WSL. If
    your keyboard shows "not allowed", please say how Allow... went.
  • Not yet tried on real hardware: alt repeat keys, audio, Vial's knobs drawn as two direction keys.

Reporting

Open an issue with your keyboard, whether it runs
VIA or Vial, your system (Windows, macOS, or which Linux and desktop), and what you did. Settings
shows Nazg's version and its definitions.

v0.1.0-test.3

v0.1.0-test.3 Pre-release
Pre-release

Choose a tag to compare

@mymakercorner mymakercorner released this 18 Oct 18:48

Third test build of Nazg -- a native keyboard configurator for VIA and Vial keyboards, now
for Windows and Linux. Shared so people can try it on their own keyboards before a first
public release; expect rough edges, and please report them.

Windows 10/11, 64-bit -- nazg-0.1.0-test.3-windows-x64.zip. Unzip and run nazg.exe;
nothing is installed. The build is not signed yet: if Windows says "Windows protected your PC",
click "More info", then "Run anyway".

Linux, x86-64 -- nazg-0.1.0-test.3-linux-x86_64.AppImage, one file for most distributions
(Debian 10+, Ubuntu 20.04+, Fedora, RHEL / Rocky 8+, Arch...). Make it executable and run it:

chmod +x nazg-0.1.0-test.3-linux-x86_64.AppImage
./nazg-0.1.0-test.3-linux-x86_64.AppImage

or allow it to run as a program in your file manager's Properties. No libfuse2 needed. It needs
a Vulkan driver, which any recent Mesa or NVIDIA driver has.

New since 0.1.0-test.2

  • Linux. Out of the box, Linux lets only root open a keyboard: Nazg lists such a board as
    "not allowed", and Allow... lets whoever is logged in configure that one board -- a udev
    rule written after your password is asked, or shown as commands to paste in a terminal. A board
    Nazg allowed shows Allowed, where you can stop allowing it.
  • Plugging in and out: the keyboard list follows keyboards as they are plugged in or unplugged,
    and an open keyboard that is unplugged closes. No more Refresh.
  • Saved layouts: Save to file... and Load from file... in the board menu, in Vial's .vil
    format for every board -- files from Vial load in Nazg and the other way round. Files saved by
    the VIA app (.layout.json) load too. Nazg shows what would change before writing anything.
  • Device (under Tools, every board): enter the bootloader where the firmware allows it -- and
    where it does not, how to; reset the keymap to the firmware's; empty the macros.
  • The key test (Matrix view, under Tools) for every board: it reads the switches, or, where the
    firmware does not allow that, the keys your computer receives.
  • Vial keyboards in secure mode: unlocking now seen working on a real board; Cancel closes the
    board.
  • Leyden Jar controllers (Model F Labs keyboards): Diagnostics under Tools -- key presses,
    signal levels with the keys at risk, and the controller's information.
  • Nazg has its own icon.

What it does

  • Vial keyboards describe themselves and just work.
  • VIA keyboards: ships VIA's whole official registry (3513 definitions) and 737 community
    definitions vendors publish for boards VIA lacks
    (nazg-community-definitions).
    Any other board: import the via.json your vendor provides.
  • Keymap and knobs, layouts, QMK settings, lighting, audio, and a board's own menus (VIA V3) --
    written to the keyboard as you change them. Macros, tap dance, combos, key overrides and alt
    repeat keys -- written when you press Save.

Known limits

  • Linux has only been tried in WSL (Windows' Linux), not on a real desktop yet: reports from
    any distribution are especially welcome -- whether it starts, the window and its title bar, and
    Allow...'s password window.
  • Not yet tried on real hardware: alt repeat keys, audio, Vial's knobs drawn as two direction keys.

Reporting

Open an issue with your keyboard, whether it runs
VIA or Vial, your system (Windows, or which Linux), and what you did. Settings shows Nazg's
version and its definitions.

v0.1.0-test.2

v0.1.0-test.2 Pre-release
Pre-release

Choose a tag to compare

@mymakercorner mymakercorner released this 13 Oct 18:45

Second test build of Nazg -- a native keyboard configurator for VIA and Vial keyboards.
Shared so people can try it on their own keyboards before a first public release; expect
rough edges, and please report them.

Windows 10/11, 64-bit. Unzip and run nazg.exe; nothing is installed. The build is not
signed yet: if Windows says "Windows protected your PC", click "More info", then "Run anyway".

New since 0.1.0-test.1

  • Knobs (encoders): a VIA knob is drawn as a round key, its press and both turns editable;
    Vial's knobs show their two direction keys. Turns are read and written through the board's
    encoder map; a board whose firmware keeps none says so.
  • Keychron Hall-effect boards (K10 HE and others): the matrix live test no longer lags --
    their firmware answers some requests twice, and Nazg now ignores the extra reply. A few keys
    may still not show in it; reports welcome.
  • Importing a definition made for another keyboard is now explained instead of silently
    ignored: Nazg says which keyboard the file is for.
  • Community definitions v2026.10.13: 737, up from 708 -- Keychron's other branches, Keychron
    boards whose custom keys were named wrong now fixed, and GeonWorks' boards (Acheron Apollo87,
    F1-40, Krush 65, Nova, Venom and others).

What it does

  • Vial keyboards describe themselves and just work.
  • VIA keyboards: ships VIA's whole official registry (3513 definitions) and 737 community
    definitions vendors publish for boards VIA lacks
    (nazg-community-definitions).
    Any other board: import the via.json your vendor provides.
  • Keymap and knobs, layouts, QMK settings, lighting, audio, and a board's own menus (VIA V3) --
    written to the keyboard as you change them. Macros, tap dance, combos, key overrides and alt
    repeat keys -- written when you press Save.

Known limits

  • Nazg does not notice a keyboard being plugged in or out yet: plug it in first, or press
    Refresh in the keyboard list.
  • Not yet tried on real hardware: unlocking a Vial keyboard in secure mode, alt repeat keys,
    audio. Reports on these are especially welcome.

Reporting

Open an issue with your keyboard, whether it runs
VIA or Vial, and what you did. Settings shows Nazg's version and its definitions.

v0.1.0-test.1

v0.1.0-test.1 Pre-release
Pre-release

Choose a tag to compare

@mymakercorner mymakercorner released this 11 Oct 16:20

First test build of Nazg -- a native keyboard configurator for VIA and Vial keyboards.
Shared so people can try it on their own keyboards before a first public release; expect
rough edges, and please report them.

Windows 10/11, 64-bit. Unzip and run nazg.exe; nothing is installed. The build is not
signed yet: if Windows says "Windows protected your PC", click "More info", then "Run anyway".

What it does

  • Vial keyboards describe themselves and just work.
  • VIA keyboards: ships VIA's whole official registry (3513 definitions) and 708 community
    definitions vendors publish for boards VIA lacks
    (nazg-community-definitions).
    Any other board: import the via.json your vendor provides.
  • Keymap, layouts, macros, tap dance, combos, key overrides, alt repeat keys, QMK settings,
    lighting, audio, and a board's own menus (VIA V3) -- written to the keyboard as you change
    them.

Known limits

  • Nazg does not notice a keyboard being plugged in or out yet: plug it in first, or press
    Refresh in the keyboard list.
  • Not yet tried on real hardware: unlocking a Vial keyboard in secure mode, alt repeat keys,
    audio. Reports on these are especially welcome.

Reporting

Open an issue with your keyboard, whether it runs
VIA or Vial, and what you did. Settings shows Nazg's version and its definitions.