On a Linux installation, default.theme can be found on /opt/bitwig-studio/resources/themes. I have just opened it for the first time. It seems to have… every single elements that shows in the UI. Thousands of lines of code. I’m not a Java developer, and I don’t understand how the color values are being assigned. I haven’t found something obvious like hexadecimal color numbers. There are many references to variables, and decimal numbers in triplets. Anyway.
As it is now, this file looks very exposed. If users could happily modify values here, chances are that someone would break something soon. Or someone else would create a consciously or unconsciously malicious theme file that would post i.e. here and then other users would copy it and so forth. Probably nothing that a user with some technical knowledge could revert, but…
Perhaps a first step to test what people would come up with would be:
From all those classes, select just a very few that would be themable and document them somewhere obscure mentioned in the release notes.
Users could create and exchange .theme files that ciould be located somewhere in the .Bitwig folder in their home directory.
To use this theme, a user should give it a precise name i.e. atmyownrisk.theme and enable beta features.
If beautiful things appear and no havoc happens, then a next step could be to remove the requirement for beta releases and/or select the theme file from the Settings UI.
Then we would just need to wait until someone requests a device to modulate the theme color values on the go. Disco Bitwig!
This would be nice, although I actually like the color scheme of BW atm. I do, however, with BW had real-looking fader knobs instead of the bar graph. It probably wouldn’t take up more space, but it would just look more “professional” IMO.
This feature is also critical to improve accessibility for visually impaired people. The current default theme has already a good contrast, but not on all elements. While the hole layout is relative dark the midi editor is mid tone gray. Thats a problem because it is iven impossible to solve this with accessibility tools that simply inverts all colors.It is simply not enough to use some kine of tool that meters the contrast values and therefor came to the conclusion that this will be good. It may be somewhat usable but not necessary for a lone time or if you want to concentrate on other things than where exactly the lines in the MIDI editor are.
Most DAWs out there make the same misstake ass it comes to scaling it is mostly not availbale or so deeply hidden in settings that you are not able to reach it if you realy need it. This was for real a selling point for me as I first tested out Bitwig 2 long time ago. Simply tap top of the window and select new scaling . How gread would it be to have high contast theme and simple light theme and so on selectable the same way.
As Developer I moved to VS Code mainly hust because it was simply Ctrl+P “Theme …” that leads me directly t a high contrast theme - no headache needed - no long internet research needed it just was there ;-).
Bitwig has such a good comunity I am sure if You provide such a feature the comunity will do the rest. And maybe you could provide already some good themes like a real high contrast theme and consistant theme.
For people like me, who live with some kind of visual impairment, colors are a fundamental part of the process that defines whether you will be able to use a software or not.
Currently I can use Bitwig but thanks to a lot of juggling with the accessibility features native to OSX.
To edit MIDI or audio (which has a light background), I need to invert the screen colors.
To use Phase-4 (or any other part of the DAW that uses the color red in fonts), I need to activate the use of gray scald colors.
With the grey scale active, I can’t tell when a modulation source is being used, so… more juggling.
To use The Grid I also need to make constant adjustments in order to see the cables.
In many ocasions I have to use high contrast mode to read text.
I won’t name them all because I believe the point is already established, but, in short: Accessibility is constantly left out by developers, which is perfectly understandable since the visually impaired are a very small slice of the market, however, for the few who make use of this type of feature, makes all the difference between being able to evenuse the DAW or not.
All that said, I still believe Bitwig is the most deliteful piece of music making I have ever used in a computer and I hope that my contribution here doesn’t sound like a complaint but like a real wish for grow. I’m 40 now, and I still have a hard time explaining what are the issues that impair my life, so it’s perfectly understandable that normal sighted people should be allowed to not understand them either.
Personally, I’m very inspired by the visuals and like to customize almost everything where possible. Moreover, I think this feature can attract a large audience of people who are just looking for fun. And there are a lot of those people.
How many people reading this actually wrote to bitwig ?
It seems to be the only way to make a difference
support at bitwig.com
I think the visually impairing point is really important and as @icaria36 said well enough it’s not like a theme force anyone to use them. And a default.theme is just there.
I’m gonna write to them because i have some low level impairment and i can’t imagine with people who have worst cases.
I know they are probably overworked but its one path forward to having way more consumers and more cash flow no ?
its probably even more important than many other more interesting features for a lot of people because its actually something tied to identity and identification with visual style, personal ‘branding’. Surely almost all the people i know who use dsableton have some variations of either one of the main 5 themes or some totally customs one.
The high amount of orange in the theme makes my bass sound thin and the drums lack proper transients and punch. Shifting the color tone to a different color will immediately lead to much punchier drums and better mixes. Shifting the color tone and having an option for purple text on green background is the reason i am missing proper eye cancer on my tracks and therefore this should be included so i can invert the colors of my mastering bus and have an overall shinier tone and brightness in my mix.
After seeing FL studio sorta botch the theme thing. I’d say spending resources on this is risky imo, at least for now. Arrangement, audio editing , and piano roll background color adjusting would be nice for night time. Because it is pretty white for this. Orange is actually ideal for improving sleep quality. For morning and day I enjoy the wakefulness and focus of the current look.
But yeah having a consistent look for a daw also helps identify the daw in tutorials and for support reasons, as soon as you get themes a small portion of people start using disgusting carnival level eye bleeding themes.
I even caught myself spending shit tons of time making themes. Doesn’t help productivity, it creates another distraction.
However I do understand that the more large area white that exist on the screen could be more damaging to you eyes and sleep in the long run. (due to white containing more blue) So reducing the brightness of the arrangement, audio-editing and piano roll could assist with this.
Having a dark arrangement background option basically. Maybe even a day night switcher for the arrangement part would be interesting to me.
Hi, I’d like to say that legitimately, I’d buy Bitwig except the colours look just really bad. I hope that the team can make the colours customisable, as Orange is a nightmare colour. I am sure many others agree.