Basics 2: Dygma Bazecor – Changing Key Assignments and Using Layers Effectively

Anyone using Dygma keyboards such as the Raise, Raise 2, and Defy will inevitably reach the point, after the basic setup, where the factory layout is no longer regarded as an unchangeable specification, but as a starting point. The keyboard is already working, the firmware is up to date, Bazecor recognizes the hardware, and the first checks through the Keyboard Manager and the interface have been completed. Now begins the part that turns a well-built keyboard into a personal working tool: customizing the key assignments.
This guide builds directly on Basics 1: Dygma Bazecor on Windows, macOS, and Linux – Getting Started with the Rise, Raise 2, and Defy. That article focused on installation, connection, the interface, firmware, and the basic use of Bazecor. The second part now introduces the Layout Editor, explains how to reassign individual keys, and shows how additional layers can be configured and accessed. Superkeys are deliberately left out for the time being. They expand the principles explained here considerably and therefore receive their own place in Basics 3.
Once again, this is not a review or an evaluation. Nor should every key be changed merely because Bazecor provides the option. A functional layout is not created by making as many adjustments as possible, but by making a few understandable decisions. The difference between a sensibly customized keyboard and a control panel that requires even its creator to consult a map after three days often amounts to only a few enthusiastically placed mouse clicks.

The Layout Editor as the Actual Workbench

After Bazecor starts, it first displays the recognized Dygma devices. If more than one compatible keyboard is connected, the specific device to be configured can be selected. Bazecor also provides the option of creating a virtual keyboard. This allows the interface to be explored without connected hardware or a layout to be prepared in advance. Selecting Configure then opens the Layout Editor with the current assignment of the chosen device.
The graphical representation corresponds to the respective keyboard. With a Raise or Raise 2, Bazecor displays the split but otherwise largely conventional key field together with the thumb keys. The Defy appears with its columnar arrangement and more extensive thumb cluster. This keeps the exact physical position currently being edited visible at all times. That matters more than it may initially seem. An assignment can be logically correct in every respect and still end up on the wrong key if a neighboring position was selected in the editor.
Above the keyboard view is the selection for the active layer. Dygma supports up to ten individually configurable levels in Bazecor. Each of these levels has its own complete key assignment. A key can therefore type a letter on Layer 1, trigger an arrow key on Layer 2, and perform a media function on Layer 3. (⁠support.dygma.com)
Layer 1 remains selected for the first customization. It is usually the normal typing layer and forms the starting point for everyday use. Anyone who immediately begins on Layer 7 is of course free to do so, but should not be surprised later when the new assignment exists only in an area that cannot yet be accessed at all.

Before the First Change: Create a Backup

Bazecor automatically creates a backup of the configuration whenever changes are saved. According to Dygma, these backups contain layers, macros, Superkeys, and settings, and can be restored under Preferences > Backups. The storage location for automatic backups can also be changed there.
Despite this automatic protection, it is advisable to create a deliberately exported backup with a clear name before making extensive changes. “Raise2-before-layout-rebuild” still explains months later what the file contains. “Backup_final_new2,” by contrast, has approximately the same documentary value as a drawer labelled “Miscellaneous.”
A backup is useful not only in case of errors. It also allows different layout ideas to be tested without risk. If a change no longer feels right after a few days, every key does not have to be restored individually. The previous state can simply be loaded again. Dygma also provides default configurations that can be imported through Preferences > Backups > Load Backup.

Reassigning a Single Key

The actual reassignment begins by clicking the desired key in the graphical view. Bazecor then opens the available function groups. The existing keycode can be replaced with another letter, number, symbol, function key, modifier, layer function, media function, or shortcut. Dygma’s official guide describes the process in equally straightforward terms: select the key, assign the desired function, and save the change afterwards. (⁠support.dygma.com)
A simple example is swapping Caps Lock and Escape. Caps Lock has little importance in many workflows, while Escape is regularly needed in editors, applications, and dialog boxes. If the Caps Lock position is selected in the Layout Editor and assigned Escape, that physical key will send the Escape keycode from then on.
At first, only the electronic assignment changes. The label on the keycap naturally remains the same. Bazecor cannot turn a Caps Lock keycap into an Escape keycap, however capable the software may be elsewhere. On mechanically compatible positions, the keycaps can subsequently be swapped physically. This is not always possible, however, because the shape, width, and profile of the keys may differ. An incorrect label does not affect the function, but it can lead to brief moments of internal negotiation during the adjustment period.
After the change, Save changes must be selected in the upper-right corner. Only then is the new assignment transferred to the keyboard. If Bazecor is closed beforehand or another device is selected, the change may remain nothing more than a good intention. Dygma explicitly points out in its official documentation that unsaved adjustments are not transferred to the keyboard. (⁠support.dygma.com)

The Keyboard Stores the Layout

The assignments configured through Bazecor are stored in the controller or Neuron of the keyboard. Bazecor therefore does not have to remain running in the background. After saving, the keyboard can be used on another computer without first installing the same software there. Dygma explicitly confirms this behavior for the Raise 2: the software is only required to change the layout, after which the configuration remains stored in the Neuron.
This is particularly practical when switching between Windows, macOS, and Linux. The physical layout travels with the keyboard. However, the operating system still interprets the transmitted keycodes according to its own selected language and keyboard layout. If a key is configured as Z in Bazecor while the operating system expects a different assignment, the visible result may therefore differ. Bazecor does not replace the operating system’s language setting; it determines which keycode the hardware sends.
This is not an error, but the normal separation between keyboard firmware and operating system. Anyone using several computers with different keyboard languages should plan the combination deliberately. Otherwise, a situation can quickly arise in which the keyboard is working perfectly correctly, only according to a different dictionary than the computer.

Assigning Shortcuts Directly to a Key

Bazecor can assign not only a regular keycode to a single key, but also a combination consisting of a key and one or more modifiers. Dygma gives the example of selecting the S key and then adding Ctrl, causing the key to trigger the Ctrl+S shortcut.
The principle is suitable for frequently repeated combinations such as copy, paste, save, undo, or opening specific functions within an application. Instead of pressing two or three keys simultaneously, a single appropriately assigned position is sufficient.
Restraint is still worthwhile. A shortcut placed on a single key is fast, but it can also be triggered accidentally just as quickly. Ctrl+S is relatively harmless. A combination for closing a window, deleting a document, or starting a complex program sequence deserves a position that is not brushed during normal typing.
Directly assigned shortcuts also differ from macros. A shortcut consists of one key and one or more modifiers sent simultaneously. A macro, by contrast, can contain a timed sequence of several inputs. A dedicated macro is therefore unnecessary for the simple Ctrl+V combination. Using one in this case would be about as appropriate as hiring a delivery van to transport a paper clip.

Understanding Modifiers

Modifiers change the meaning of another key. These include Shift, Ctrl, Alt, Alt Gr, and the operating system key, meaning the Windows key under Windows and usually Command under macOS. Bazecor allows these modifiers to be assigned individually or combined with another key to create a shortcut.
The software also supports so-called One-Shot Modifiers. If a modifier configured in this way is tapped briefly, it applies to the next input. A single tap on Shift, for example, capitalizes the next letter. If the key is held, it behaves like a regular modifier. A double tap locks the modifier until it is pressed again. Dygma compares this behavior with Caps Lock, although it applies not only to capitalization but to whichever modifier has been selected.
This function can be useful when holding several keys simultaneously is uncomfortable. However, it changes behavior that has been practiced for decades. A first test on a less critical position is therefore advisable. Modifiers are among the foundations of almost every keyboard shortcut. If they are distributed too creatively, the computer can suddenly feel as though it is responding to commands from a slightly different parallel universe.
Tap-hold modifiers, in which a key outputs a character when tapped and a modifier when held, are implemented through Superkeys on the Raise 2 and Defy. On the original Raise, the Add a key on Tap function remains available in certain menus for this purpose. Dygma explicitly separates these options according to model and firmware version. Since Superkeys are the subject of Basics 3, this guide remains focused on regular modifiers and One-Shot Modifiers.

What Layers Actually Are

Layers appear more complicated at first contact than they really are. Dygma explains the principle using the familiar Shift key: when Shift is held, many keys already produce a different set of characters. A lowercase letter becomes an uppercase letter, and a number becomes a symbol. A layer extends this familiar principle to an entire freely configurable keyboard level.
Bazecor supports up to ten layers. Each level can be opened and edited individually through the selection menu at the top of the Layout Editor. According to Dygma, the factory-configured second and third layers contain, among other things, functions that are missing from a compact keyboard compared with a traditional 100-percent model. These can include navigation controls, function keys, a number pad, or other special functions.
A layer is not an independent profile that necessarily has to change the entire keyboard. It can just as easily contain only a few different keys. For example, Layer 2 can turn the letters I, J, K, and L into arrow keys while all remaining positions continue using the functions of the layer below.
For an unchanged position to use the assignment from the lower level, it is configured as Transparent. Transparent does not mean that the key has no function. Instead, the input passes through the current layer and uses the corresponding assignment from the layer below. This function is particularly important when an additional layer is only intended to modify a small area.
A truly disabled key, by contrast, requires a function such as No Key or the corresponding empty assignment. The difference is considerable: Transparent inherits the function below, while a disabled position sends nothing at all. Anyone who confuses the two may encounter a key that continues working with admirable dedication despite supposedly having been deactivated.

Editing a Layer

To edit a layer, the desired level is first selected at the top of the Layout Editor. Reassignment then works in exactly the same way as on the base level: click a key, select a function, and save the changes. Dygma describes precisely this procedure for layer configuration.
A simple navigation layer is a suitable starting point. The I, J, K, and L positions can, for example, be assigned the up, left, down, and right arrow keys. U and O can take over Page Up and Page Down, while H and the semicolon key become Home and End. The exact arrangement depends on personal habits. The important point is that navigation becomes accessible without moving the right hand far away from the main key field.
On a Raise, Raise 2, or Defy, the thumb keys are particularly suitable for accessing additional levels. They already sit beneath the stronger and more mobile thumbs, while traditional keyboards delegate many important modifiers to the little fingers. Placing layer access beneath the thumb therefore not only shortens movement, but also keeps the other fingers in their familiar positions.
Another useful level can recreate a number pad. This preserves the functionality of a full-size keyboard on a Defy or compact Raise without requiring a permanent physical number pad. For spreadsheet work, this layer can be locked, while for brief numerical input it can be activated only temporarily.

Layer Shift: Active While the Key Is Held

The standard method for accessing a layer is called Layer Shift. The selected level remains active only for as long as the assigned layer key is held. As soon as it is released, the keyboard returns to the previous level. Dygma again compares this behavior with a conventional Shift key.
Layer Shift is particularly suitable for functions that are needed only briefly. Anyone who wants to use two arrow keys, a function key, or a symbol can hold the layer key, perform the input, and then release it.
When choosing the position, it is worth considering which hand will use the functions on the target layer. If the navigation block is located on the right half of the keyboard, a Layer Shift key beneath the left thumb is often more comfortable. The left hand holds the layer while the right hand remains free to navigate. If the same layer access is placed beneath the right thumb, that hand has to hold the key and operate the keys above it at the same time. This is possible, but not necessarily elegant.

Layer Lock: The Level Remains Enabled

With Layer Lock, a short keypress switches permanently to the target layer. The level remains active until another assigned key triggers the return. Dygma compares the behavior with Caps Lock and names alternative layouts, number pads, spreadsheet work, and gaming layers as typical use cases.
The crucial point is the route back. If Layer 4 is locked, Layer 4 must contain a key that returns to the base level or another desired layer. If it is missing, the keyboard is not technically trapped beyond rescue, but returning through Bazecor becomes unnecessarily cumbersome.
A Layer Lock key should therefore ideally occupy the same physical position on all relevant levels. On Layer 1, it leads to Layer 4; on Layer 4, it returns to Layer 1. Muscle memory can then find the same switch regardless of the current state.
Layer Lock is useful for a permanently active gaming layer. Rarely needed keys can be disabled there, important commands can be moved closer to WASD, and other functions can be arranged deliberately. After the game, the same position returns to the normal typing level. A different lighting color for the layer can additionally indicate that the keyboard is currently following a different set of rules.

One-Shot Layer: One Level for Exactly One Input

A One-Shot Layer is activated for exactly the next key by tapping it once. The keyboard then automatically returns to the previous level. According to Dygma, double tapping the One-Shot key makes it behave like Layer Lock. Holding it, by contrast, makes it operate as Layer Shift. A single layer key can therefore provide three different methods of access.
For a One-Shot Layer to work as intended, the same position on the target layer must be assigned as Transparent. Dygma explicitly names this requirement. One-Shot Layers also cannot be nested. Likewise, a One-Shot Layer should not use Layer Lock to switch directly into another level; the keyboard must first return to the previous layer.
One-Shot is suitable for individual, infrequent inputs. A short tap can, for example, open a symbol layer, the next key produces the desired character, and the normal typing level is then restored. The layer key therefore does not have to be held simultaneously.
The function requires some adjustment but remains logical. A tap applies to one input, a hold applies for as long as the key is held, and a double tap locks the level. Anyone who remembers these three states gains flexible access without needing three separate layer keys.

Setting a Default Layer

Bazecor allows any layer to be defined as the default level. This layer is loaded when the keyboard is switched on or connected. According to Dygma, the setting can be found under Preferences > Advanced > Default Layer.
This can be useful for alternative base layouts such as Colemak or Dvorak, as well as permanently specialized workstations. For most users, Layer 1 nevertheless remains the clearest default level. An exotic default layer is technically unproblematic, but it should be chosen deliberately. Otherwise, the keyboard may start one morning in a configuration that even its owner only recognizes again after a cup of coffee.

Exporting and Loading Individual Layers

In addition to complete backups, Bazecor can export individual layers. To do this, the desired layer is selected in the Layout Editor and Share selected layer is opened through the gear icon next to its name. The level can then be saved as a file.
This option is useful for sharing individual work, gaming, or navigation layers without overwriting the entire keyboard configuration. Different versions of a layer can also be archived separately. A complete backup remains important, however, because it protects the full configuration, including all other levels, macros, Superkeys, and settings.
Every assignment should be checked when importing layers created by someone else. A layout developed on an ANSI Raise does not necessarily fit an ISO Defy without adjustment. Differences in the number and position of physical keys, together with personal habits, prevent a universal fit. A layer created by someone else should therefore be treated more as a template than as sacred scripture.

Assigning Media, LED, and System Functions

The Layout Editor also includes the Media & LED section. It contains functions for playback, volume, muting, and track navigation. Commands for keyboard lighting, monitor brightness, sleep mode, and other supported system actions can also be assigned.
These functions are particularly suitable for additional layers. A media layer can group volume, playback, and track navigation on the right hand. The left hand can simultaneously receive controls for lighting or screen brightness.
Whether every system function responds identically under every operating system partly depends on support from Windows, macOS, Linux, and the respective application. Bazecor sends standardized commands, but the operating system still decides how to handle them. A key for camera control or monitor brightness may therefore work on one computer and produce no visible response on another.

Using Colors to Distinguish Between Layers

Bazecor allows each key and the underglow segments to be assigned individual colors on every layer. The color configuration can be found in the Layout Editor under the Color tab. Changes are again transferred to the keyboard only after selecting Save changes.
A different layer color is not merely decorative. It can indicate visibly which level is currently active. A number-pad layer might use green keys, a navigation layer blue, and a gaming layer red. A quick glance is then enough to identify the current state of the keyboard.
Care is still required with the color palette. Dygma points out that changing a palette color affects every key and lighting segment that uses that color slot, including those on other layers. Editing an existing shade of red can therefore change more positions than originally intended.

Developing a Layout Step by Step

The temptation is considerable to rebuild every layer immediately after opening the Layout Editor for the first time. A gradual approach is more sensible. Begin by changing one frequently used key. After a few days, it will become clear whether the new position genuinely works better or merely looked convincing on the screen.
A simple layer, such as one for navigation, can follow. Only once it is being used reliably should a number pad, media layer, or gaming layer be added. Every extension changes muscle memory. If twenty positions are moved at the same time, it becomes difficult to determine later which change was helpful and which only created additional searching.
A good layout reduces movement and decision-making. Frequently used functions belong within easy reach, while rare commands can remain on a layer. A key should not receive a new task merely because another unassigned function has been discovered.
The thumb keys deserve particular attention. On the Raise, Raise 2, and Defy, they can hold Space, Enter, Backspace, modifiers, or layer access. Which arrangement works depends on personal typing habits. A universal ideal assignment does not exist. Bazecor’s strength lies precisely in the fact that one is not required.

Typical Mistakes When Assigning Keys

The most common mistake is editing the wrong layer. A key is changed correctly, saved, and still appears unchanged afterwards. Frequently, the new function is sitting on Layer 2 while Layer 1 remains active.
An equally common problem is the absence of a route back from a locked layer. Layer Lock works, but the target level contains no suitable key that returns to the base layer. The return route should therefore always be configured before the new layer is activated permanently.
Another classic mistake is confusing Transparent with a disabled key. Transparent inherits the assignment from a lower layer. Anyone who truly wants to deactivate a key needs the corresponding empty assignment.
Unsaved changes also regularly cause confusion. Only Save changes transfers the configuration to the keyboard. A layout that looks perfect in the editor but was never saved has approximately the same practical value as an emergency escape plan still sitting in the printer.
Finally, the operating system’s keyboard layout must not be forgotten. If the characters shown in Bazecor do not match those appearing on the screen, both the firmware configuration and the active keyboard layout under Windows, macOS, or Linux should be checked.

Preparing for Basics 3: Superkeys

Changing individual keys and creating custom layers establishes the foundation for the next part. The keyboard can now take on new functions, switch between different levels, and move frequently used commands closer to the natural hand position.
Basics 3 extends this principle with Superkeys. There, a single key receives several functions depending on how it is pressed. A short press can, for example, output a character, while holding it activates a modifier or layer. Further input sequences allow additional actions.
Until then, it is worth taking the new layout for a test run. Reassign one individual key, create a clear navigation layer, and check the route back to the base level – that is enough to establish the foundation. After that, Superkeys feel considerably less like keyboard alchemy and more like the next logically organized insert in an already opened toolbox.

Note in accordance with EU transparency requirements:

The Dygma Raise, Dygma Raise 2, and Dygma Defy used for this guide were provided to us by Dygma as non-binding or permanently supplied review samples for testing and documentation purposes. This is not paid advertising.
Dygma had no influence on the content or editorial independence of this article. All explanations and configuration steps are based on practical use of the hardware and the manufacturer’s official documentation.
We would like to thank Dygma for providing the keyboards and for the trust placed in DataHolic.de.