Keylegend 1.2.0

Installing

Keylegend-1.2.0-setup.exe installs for the
current user — no administrator rights needed. It adds a start menu entry, offers
autostart from within the application, and removes both on uninstall.

Keylegend-1.2.0-portable.zip is the same
program to unpack and run wherever you like.

Requirements

• Windows 10 or 11
• .NET 10 Desktop Runtime
  — the installer checks and links it if it is missing
• Razer Synapse with the Chroma SDK service running

About the Windows warning

Both files are unsigned, so SmartScreen will call the publisher unknown. A signing
certificate costs a few hundred euros a year, which this project does not have.
Verify the download against SHA256SUMS.txt if you would like to check it came from
here intact:

Get-FileHash .\Keylegend-1.2.0-setup.exe -Algorithm SHA256

Which keyboards work

Every Razer Chroma keyboard. Keylegend asks Razer Synapse which one is plugged in and
reads Razer's own drawing of that model, so there is no list to be on. Which cell of
the lighting matrix each key belongs to comes from the Chroma protocol's own table,
confirmed by hand on a DeathStalker V2 in ISO-DE and correct by inference elsewhere.
If yours lights the wrong keys, the window shows which key should be lit instead —
please open an issue saying which.

What's Changed

• Keylegend 1.2.0: the lighting answers the typing by @Eistee82 in #3

Full Changelog: v1.1.0...v1.2.0

Keylegend 1.1.0

Installing

Keylegend-1.1.0-setup.exe installs for the
current user — no administrator rights needed. It adds a start menu entry, offers
autostart from within the application, and removes both on uninstall.

Keylegend-1.1.0-portable.zip is the same
program to unpack and run wherever you like.

Requirements

• Windows 10 or 11
• .NET 10 Desktop Runtime
  — the installer checks and links it if it is missing
• Razer Synapse with the Chroma SDK service running

About the Windows warning

Both files are unsigned, so SmartScreen will call the publisher unknown. A signing
certificate costs a few hundred euros a year, which this project does not have.
Verify the download against SHA256SUMS.txt if you would like to check it came from
here intact:

Get-FileHash .\Keylegend-1.1.0-setup.exe -Algorithm SHA256

Which keyboards work

Every Razer Chroma keyboard. Keylegend asks Razer Synapse which one is plugged in and
reads Razer's own drawing of that model, so there is no list to be on. Which cell of
the lighting matrix each key belongs to comes from the Chroma protocol's own table,
confirmed by hand on a DeathStalker V2 in ISO-DE and correct by inference elsewhere.
If yours lights the wrong keys, the window shows which key should be lit instead —
please open an issue saying which.

What's Changed

• Keylegend 1.1.0: the keyboard comes from the drawing Synapse already has by @Eistee82 in #2

Full Changelog: v1.0.0...v1.1.0

Keylegend 1.0.0

Installing

Keylegend-1.0.0-setup.exe installs for the
current user — no administrator rights needed. It adds a start menu entry, offers
autostart from within the application, and removes both on uninstall.

Keylegend-1.0.0-portable.zip is the same
program to unpack and run wherever you like. Keep the devices folder next to the
executable; without it Keylegend has no keyboard to describe.

Requirements

• Windows 10 or 11
• .NET 10 Desktop Runtime
  — the installer checks and links it if it is missing
• Razer Synapse with the Chroma SDK service running

About the Windows warning

Both files are unsigned, so SmartScreen will call the publisher unknown. A signing
certificate costs a few hundred euros a year, which this project does not have.
Verify the download against SHA256SUMS.txt if you would like to check it came from
here intact:

Get-FileHash .\Keylegend-1.0.0-setup.exe -Algorithm SHA256

Which keyboards work

One profile has been verified on hardware — the Razer DeathStalker V2 in the German
ISO layout. The other thirty-one are generated from standard key dimensions: their
geometry is exact, their LED mapping is an educated guess. If yours lights the wrong
keys, correcting it takes about ten minutes and no programming. See
docs/en/adding-a-keyboard.md.

Full Changelog: https://github.com/Eistee82/Keylegend/commits/v1.0.0