No Products in the Cart
Our goal for Bazecor is for users to have unlimited options to make Raise a powerful tool for gaming, coding, and everyday work.
We have done numerous updates after its first release in December 2019. Most of these updates were made thanks to the users' feedback. Every comment we get is extremely valuable.
As you may know, our software is open-source and our development Trello board is public. Anyone can access our code in Github and can vote or comment on the Trello board the features that we will be implementing.
After releasing the Raise and having hundreds of users test the software and giving us feedback, we’ve solved: firmware bugs, software bugs, and we’ve also added new features that we believe are better for the user experience.
It’s important for the software to be intuitive. Although we are still far away from the UX that we aim to have, we will continue to release updates every month.
Make sure you get to upgrade Bazecor’s firmware to benefit from the latest updates, features, and bug fixes.
List of the changes we’ve done in the 0.2 version:
Miscellaneous - for better UX
There are other small changes. Please read the rest of the article for more information.
Unfortunately, we do not have the executable for the Mac Operating System yet. We detected a problem where Bazecor would crash upon startup.
We have recently got to a state where Bazecor would not crash on OSX anymore. However, it no longer connected to the Raise either, and that affected all operating systems.
So for the time being, we have released the updates without an OSX installer. As soon as we fix the connection issue that happens after fixing OSX, we will do another release with all OSes supported.
We currently have ‘LockLayer’ and ‘ShiftToLayer’, both of which activate a given layer in addition to the ones already active.
Having multiple layers active at the same time can be confusing, especially when using Lock to Layer and Transparent keys. For the sake of simplicity, we are reworking the layer system and removing Transparent keys.
Our goal for the next release (ETA March) is to have only one plugin for layers. In that plugin, you’ll be able to configure the desired behavior when you hold or tap a Layer key.
For Bazecor v0.2 we are substituting ‘LockToLayer’ with ‘MoveToLayer’ key, which activates the given layer, and deactivates the rest of layers. The implementation of ‘MoveToLayer’ is the biggest update in the new version of Bazecor. It looks like a small change, but it’s the base to develop the next stage of the Layers plugin.
Move To Layer is a simpler way to work with layers. For the sake of not overloading new users with complex features, the factory firmware will use ‘MoveToLayer’ instead of ‘LockToLayer’.
Here’s some information about our roadmap for the Layers rework:
Bazecor v0.1 (factory firmware):
Shift to Layer and Lock Layer are the keys used to change from one layer to another one.
Bazecor v0.2 (18th Feb 2020 update):
Future plans for Bazecor v0.3:
In the Bazecor v0.3, we plan to merge all these behaviors into one plugin called LEVELS.
In the advanced settings of ‘Levels’, you will be able to select the function of each behavior for the different keys: normal keys, layer keys, modifier keys.
*Boomerang Layer - tapping this key once will bring you to another layer but after you press any key on that layer, you will be brought back to the previous layer.
**Boomerang Modifier - by tapping this key once, only the next key will be modified.
This particular update came from a user’s request.
We added modifiers to the “Navigation & Miscellaneous” keys as in the previous version there was none. Now you can do functions such as Ctrl + Print Screen.
This is a new feature on the firmware of Bazecor and not in the software. Another update that came from a user’s request.
This feature allows a custom program to connect to the Raise and send it commands to change layers. This is for advanced users who can write a program and take advantage of this setting.
Keypad Enter refers to the enter key on the number pad, which is a different keycode than the enter key on the main keyboard.
The LEDs of the Raise will turn off after approximately 10 minutes of inactivity.
Now users can select the time the LEDs will turn off after inactivity.
This feature was requested by a user.
There is now an option for users to adjust the overall brightness of the Raise’s underglow and backlight.
This key will toggle all LEDs off and on. The user has to select the key in the key configurator menu.
This was a common issue we had for Mac users. If the user enabled showing built-in layers, switched to one, and then back to an EEPROM layer, Bazecor threw an error and failed to recover gracefully, resulting in a white screen.
It has been fixed by catching those errors and recovering them.
In the previous version, pressing the LED key wouldn’t wake up the keyboard. In this new version, pressing the LED key would turn on the keyboard.
When upgrading from the factory firmware to the new one, the LED mode the user saved should still be the active one, unless it was one of the removed effects.
As such, when upgrading from the old firmware to the new one, we need to adjust the saved LED mode:
For this to work, we had to store a byte in EEPROM, to signal that we've upgraded to the latest version of the firmware. This should act as a counter of sorts so we can reuse it in the future too.
The text box of the troubleshooting advice did not disappear when exited. This bug has now been fixed.
When enabling hardcoded layers, while "use custom layers only" is also enabled, the layout editor errored out and went into a blank white screen (with errors on the dev console). This only happened when the layout editor was supposed to show a negative layer.
We have fixed this bug.
When using the Spanish layout, there are two backticks in the punctuation group. The second one should be `º` instead.
The initial screen currently reads "Software update", which is not the appropriate title.
We changed it to "Select a keyboard".
GUI stands for Graphic User Interface. It’s a kind of an old school way of calling the operating systems that not a lot of youngsters know.
Instead of the not very descriptive and awkward "Left Gui" / "Right Gui" labels, GUI has been replaced by the WIN, MAC or LINUX, to match your operating system.
When in Dark mode, some texts become unclear and selected keys become indistinguishable to others. We decided to disable it entirely until we fix the UI.
In the image above, it’s hard to see that the 4 key has actually been selected.
`XXX` wasn’t a clear name for a disabled key. We’ve changed it to `NO KEY`.
Transparent keys are shown in Bazecor as no text keys. Now the key is called TRANSP. In the configurator and you’ll see `TRANS` on the key.
We got a few messages from users saying that they would get stuck in a solid color and couldn’t get back to their custom color.
We realized that having the static solid colors, such as the blue, red, green, white, may seem confusing for users especially if they accidentally hit the LED Next Effect key. This would make them think that there is a bug because the colors would not change.
To try to avoid this issue, we decided to only have light animations in the LED color modes. This way, people will know that they are in an LED effect and that they simply need to press the LED Next Key to change the colors.
We resized the boxes in the key configuration menu to be more efficient with the space.
Merging these two sections reduces clutter considerably. We decided that it made more sense to have both on the same screen - the keyboard settings would just be hidden when there's no keyboard connected yet.
Bazecor currently supports English and Hungarian. The latter isn't very useful, but having the language option gives a false impression that there are more languages supported.
For now, until more translations are available, we have removed the option. Only English is supported by Bazecor.
In the next updates, we will be working on these issues:
You can also check our progress live on our Development Trello board. Access the board here: https://trello.com/b/keS2GQcU/bazecor-firmware-development
Starting at $296.
You can change the color of some effects in the code, yes. Bazecor only supports changing the colors when in the “colormap” effect, but some of the others allow changing colors too (but only in code at the moment, not via Bazecor). Both the ripple effect and breathing can be changed by modifying the firmware (adding LEDBreathEffect.hue = 0 or WavePoolEffect.ripple_hue = 0 (where 0 is the hue of the effect, see https://en.wikipedia.org/wiki/Hue for a rough overview of what number corresponds to which color)) and recompiling. Hope this helps!
where is the mac version of this? i can’t seem to access it.
Hi Gareth, once you flash the firmware, it will say: “Firmware flashed successfully.” If it’s still not working, please email us at firstname.lastname@example.org. We handle software issues there.
Unfortunately we are still working on the v0.2 for MAC. We encountered a few issues with its executable file and we are still working on it. We hope to have it available by this month. We’ll update you or post it in our blog once we have a new version.
Can you change the colors of the LED when it’s in different effects (i.e ripple effect or breathing) or are those preset? I really like the ripple effect for the LED but I really don’t like the colors.
Did you update the firmware of your Raise?
This is just a minor suggestion and sorry if its already in place but it would be nice to be able to see if the capslock is on or off prior to typing. For example the LED could be set to turn off or change to a different colour when pressed and then back on or back to the original colour when pressed again. Like I said just a very small thing. Amazing keyboard delighted with it. Great company to deal with as well.