What's changed

• Feat: Add theme browser for community-made themes 🥳
  • Themes are fetched from awesome-bitwig-themes repository. You can always submit a pull request to make your theme featured in the built-in theme browser!

• Fix: Add privilege escalation for userspace to prevent environment conflicts with root user (#36)
  • This means you don't need tor run the theme editor as sudo/admin anymore. It will ask you to escalate if it's necessary.

• Fix: Handle 32-bit JRE case by informing user. (#37, #40)
• Fix: Adjust Welcome window height (#39)
  • Note: I can't reproduce this bug, but tried to apply a possible fix anyway. Most probably DE-specific issue.

Full Changelog: 2.2.0...2.3.0

What's changed

• Feat: Change .bte files location to userspace (#31)
  • Now, you don't have to run your Bitwig Studio as admin! (This was highly requested)
  • Also it separates .bte files across versions, keeping it tidier
    • Windows: %APPDATA%\Roaming\.bitwig-theme-editor\versions\<version>\
    • Linux & macOS: ~/.bitwig-theme-editor/versions/<version>/
• Feat: Automatically enable compatibility mode on Bitwig Studio 6
• Feat: Add themes menu item to download themes
• Feat: Improve search
  • Search filters the matching elements now
• Feat: Automatically back up JAR file
  • Backs up the bitwig.jar automatically: bitwig.jar.bak
  • If something goes wrong, just delete corrupted bitwig.jar and rename bitwig.jar.bak back.
• Fix: Inline comment support on GUI mode
• Refactor: Improve README.md readability
• Refactor: Improve confusing logs in terms of clearity

Note: After patching the bitwig.jar with this version of theme editor 2.2.0, do not use 2.1.0 or 2.0.0.

Note: This update changes theme.bte and default.bte locations. Please move your files to the new directory to continue using them. Your already patched bitwig.jar will be automatically migrated (re-patched) to the new structure.

_{This notes are just for informational reasons and you don't have to take any additional actions besides downloading and running the new patch. Happy theming!}

Oh, btw... Happy 100th commit!

Full Changelog: 2.1.0...2.2.0

What's Changed

• Add Undo/Redo Feature and Improve GUI Error Message by @Berikai in #29
• Improvements for macOS UI

The theme editor now supports undo/redo operations. Shout out to Cyoon for the suggestion, and also the first donation for the project!

Full Changelog: 2.0.0...2.1.0

Bitwig Theme Editor 2.0.0 is OUT!

I've been working on this new theme editor version, new algorithmic approach and a native UI.

I believe it's state is now enough for it to be replaced with 1.4.3 version. From now on, I'll be developing Bitwig Theme Editor 2.x on the master branch.

What's Changed

• Self-explanatory experience enhancements for non-technical users
• Added native editor UI, no need to use a seperate WebUI
• Dynamic/real-time color change support
• New theme file format
• Gradient disabling support
• Compatibility for old themes to work with Bitwig 6.x
  ...

From now on, I'll mainly focus on finding a way to edit the color values we mention as hard-coded.

Happy theming ❤️

Full Changelog: 1.4.3...2.0.0

Click here to go 2.x-dev branch

I'll probably won't be around much and won't be able to publish a new release for more than 1 week or more, just for you to know.

I did some improvements and fixes since 2.0.0-dev1, here the 2.0.0-dev2 comes!

I'm not quite sure how can I make the theme editor find the other colors as of now, the only thing that comes to my mind is a little bit "hacky", which is checking their "hardcoded color values" (in other words, all color instances without a name attached to them) and if the color matches at initialization, attaching a name to these nameless colors, so that our approach can work. As you can see, there are some artifacts in this approach:

• Multiple colors may share same color values
• Elements rendered color and real color value may differ due to layers and FXs

And, I don't know if there are items that their color values set without creating a Color class object. We'll see hopefully, in the future...

So, the first next step for me is focusing on the UI part now, and also bug fixes if any issues created.

Also, I'd like to add that the previous file read performance concerns aren't that important since every UI item reads the theme file only if that elements needs to re-render itself and the last time its rendered was at lease 3 seconds ago. It sounds performant enough for me, and it is in practice.

Here is the changes in this dev release:

• feat: Button gradients can be disabled now
  • Add the following line to theme.bte: Gradient: false
• fix: Device Header and Device Header (selected) is editable now #23
  • Some other colors in the issue #25 is also editable, but not all yet
• fix: default.bte and theme.bte path is set to bitwig-studio/bin directory, rather than current working directory

Thanks to @yioannides and @zezic for the issues created, helps a lot!

Full Changelog: 2.0.0-dev1...2.0.0-dev2

Hi everyone!
It's been quite a while since the last time I work with Bitwig Theme Editor.

With the release of Bitwig Studio 6.0 Beta, there have been some minor changes that had to be fixed for the theme editor. Once, I started working again I become motivated enough to improve the theme editor. Also, my internship has ended and I have some little time before next semester begins, that was also one of the reasons.

Click here to go 2.x-dev branch

This release is NOT a stable release by any means, so kindly be aware of that! I just wanted to release it as is for now to not wait y'all any longer. I also inserted way too much explanatory comments in the code, so that it makes it easier to anyone who wanted to participate. I always welcome any contribution!

This release changes the theme format entirely, so old theme files won't work (but don't worry I'll write a converter tool at some point). Also, the approach is entirely different, so that it makes real time color change available.

I also want to mention that if there will be any critical perfomance drops, since new approach rely on kinda heavy filesystem reads. I'm waiting for your feedback!

TODO

• Advanced UI to edit colors with ease, especially for the untechnical folks
• Improving performance of new approach, especially if it's not bearable for some (though I don't notice any performance drops)
• Disabling button gradients

Full Changelog: 1.4.3...2.0.0-dev1

In this release, minor end-user experience improvements has been made!

• feat: Error messages include more self explanatory explanations above techincal java error messages #17

• feat: Show theme applying status in the UI as title
  

Full Changelog: 1.4.2...1.4.3

This release downgrades the required JRE version from 17 to 8 since Java 17 doesn't provide any crucial features for the sake of this project. I believe it would be more benefical in terms of out of the box support since some systems may not have Java 17 or a higher version while they already have Java 8 installed.

This issue made me realize that.

Note: This release doesn't introduce any new feature or bug fix. If you already have 1.4.1 version, it performs literally the same behavior except this release is able to run on more JREs down to Java 8.

Full Changelog: 1.4.1...1.4.2

This release brings better error handling for some cases by adding null safety checks to the code.

• Fix Timeline Playhead Crash
  • Bitwig Theme Editor ignores Timeline Playhead color if it couldn't manage to access it and warns the user (5.2 Beta 11>=)
• Fix Disable Integrity Check Crash
  • Bitwig Theme Editor skips disabling integrity check if it couldn't manage to disable it and warns the user (e.g. 4.4)

Full Changelog: 1.4.0...1.4.1

What about Timeline Playhead support for version 5.2 Beta 11 and later?

I want to add a backward compatible Timeline Playhead color support to Bitwig Theme Editor for the new changed Timeline Playhead color introduced in 5.2 Beta 11. It seems like determining the new Playhead implementation requires more effort than I initially thought, so it may take a while.

I also want to let you know that I have slowed down the development of Bitwig Theme Editor because I feel the project is in a good state right now. Adding more features makes it harder to maintain the project since it introduces more components to keep track of, which starts to seem impractical in terms of cost-benefit. There are also personal life factors that limit the time I can spend on the project. Therefore, I may take things slowly. It's a hobby project, after all. Thank you for your support, hope you are all enjoying it.

Timeline Playhead support is here!

Version 1.4.0 supports a new section called "advanced" in theme files which can contain "Timeline Playhead" property.

{
  "advanced": {
    "Timeline Playhead": "#000000ff"
  },
  "window": {
  ...
}

What's Changed

• [Feature] Add Timeline Playhead support by @Berikai in #9

Full Changelog: 1.3.1...1.4.0