Yeah, theme was made with legit b9.

Strange thing here is that theme editor doesn't even recognize exported .bte file, tried other 3rd party .json ones, nothing...

Think I found the solution, only way to get the theme working is to change the name of the theme to theme.bte and place it in User/.bitwig-theme-editor/versions/6.0 Beta 11/, directory is hidden tho.

Spoiler: Official instructions

You can also manually manage the theme after patching Bitwig Studio:

• Step 1: Run Bitwig Studio
• Step 2: A file named default.bte will be created in the Bitwig settings directory
  • Windows: C:\Users\<username>\AppData\Roaming\.bitwig-theme-editor\<version>\
  • Linux & macOS: /home/<username>/.bitwig-theme-editor/<version>/
• Step 3: Create a file named theme.bte in the same directory if doesn't exists
• Step 4: Add the lines of the color values you want to change, modify, and save
• Step 4: Click on the "Dashboard Button" or resize the window to render changes

 

Last edited: Jan 4, 2026

@Melodic Reality. Oh nice. Will test tomorrow. Thank you!

 

Hope you like it, I can edit some things further, just let me know.

Noticed that audio waveform is light grey when you open it in dedicated editor, guess it makes sense to be light grey on dark by default, but it loses the appeal when everything is lighter, so yeah, I could fix that.

Also, to get the same color of arranger, change Timeline Background to 100 in Dashboard/Settings/User Interface/Contrast.

Edit: version with updated color for audio waveform

 

Last edited: Jan 14, 2026

I'm pretty certain it's actually my ancient UC-33e's using the DrivenByMoss controller scripts, which work fine in v5.2 but just moving a fader or pot crashes Bitwig v6 betas to desktop.. Maybe I should bite the bullet, open 'em up and give 'em a good clean as they do throw out some rogue MIDI data, or wait for the controller script to update from Bitwig v5.3

 

⠀⠀⠀⠀⠀⠀⠀

 

Last edited: Jan 7, 2026

ahhhh, i use the drivenbymoss for the Maschine Mikro. I love it. Sometimes it doesn't recognize the controller, but usually unplugging and back in fixes my maschine issue. Damn that sucks man.

 

Thanks for your empathy, man... I'm desperately hoping it either gets fixed by Bitwig or an updated DrivenByMoss script will let me use my beloved UC-33's with the ace new features in v6.

 

Spoiler: Changes in Bitwig Studio 6.0, Beta 12 [released 13 January 2026]

Changes in Bitwig Studio 6.0, Beta 12 [released 13 January 2026]

Improvements
• The Flying Automation Lane can now be resized [40269]
• Automation smoothing has been improved. It is now time-symmetrical, affects a smaller time range, and offers improved anti-click performance.
• Drum Machine (Container) device: When hovering over a drum cell, the note (for example, B2) that triggers that drum chain is shown in the window footer.

Fixes
• Detail Editor Panel-related fixes:
o Release velocity behavior is identical now when adding note in Clip vs. Track contexts [40466]
o Waveform Editor: [ALT]-drag (copy) of time selection now gives predictable results [40481]
o The Pencil tool in the Arranger can now open clips in the Detail Editor Panel [40532]
o Velocity handles of selected notes are now always shown in front of those for unselected note [39686]
o Dragging an automation time selections in the Detail Editor Panel now previews correctly again (a regression) [40636]
o Working with notes in the Detail Editor Panel always visualizes the lower automation section with correct timing [40629]
o Note content now longer scrolls out of view, as it did in certain cases [40623]
o Piano Roll Editor: Zoom and scroll position was not remembered per clip (a regression)[39705]
o Comping Editor: Moving take start/end borders is no longer blocked by offering gain adjustment [39696]
o Play from Time Selection action in Clip context now works in all cases [40606]
o Copy–paste works correctly in layered editing cases, when working with notes in Track context [39975]
o Using Select Previous/Next Track now update Detail Editor Panel, when shown [39691]
o Piano Roll Editor: Background no longer disappears when moving Launcher clips [40599]
o Note auditions now trigger more consistently [40537]
o Switching to Edit View via [SHIFT]-[TAB] works properly, even when the Detail Editor Panel is empty [40399]
• Onset sorting has been improved, allowing better filtering when working with the onset Threshold
• Loop length display is now correct for all cases (and time signatures) [40468]
• De-selecting the Snap to Beat Grid no longer disables other snapping targets (e.g. Snap to Onsets) [40487]
• Metronome now works properly, even with time signature changes [40160]
• Auto-zoom [SHIFT]-[Z] no longer resets when creating points in Automation Mode [40497]
• When inserting a modulator via the Pop-up Browser, the preview playback modulator is now inserted properly without copying it first [40589]
• A vertical selection of clips in the Arranger scrolls again (a regression) [40608]
• Controller-API/Regression: fix ClipLauncherSlotBank looking at master track clip instead of group scene [40207]
• Event boundary mouse interactions are offered on short events
• Launch Next Slot no longer ignores recording clips [38569]
• FX Selector (Container) device: No longer causes volume inconsistencies when in Round-robin [40616]
• Recording audio or instrument clips onto another audio track no longer results in a late recording [40598]
• MIDI files that contain invalid MIDI messages can now be loaded (with the invalid messages ignored) [40597]
• While dragging the clip end over other clips, the preview now uses the clip's color [39811]
• Select All on the Arranger now includes transport clips [39906]
• Fade previews are always shown correctly now in all cases [40613]
• [SHIFT]-clicking to fold/unfold automation lanes of all tracks works again [40624]
• Markers on the right edge of a time selection are no longer removed when the time is removed [39751]
• Cue markers no longer go missing after Duplicate Time action [39849]
• Inserting an automation clip now properly recomputes the last point’s curvature [38948]
• Moving Scale automation no longer becomes broken when zoomed out [39877]
• Group tracks in Launcher now work properly with Automation Mode [39883]
• ALS import: Automation for VSTs is imported correctly again (a regression) [40621]
• Playing clips with colors assigned that are not part of the current palette will no longer turn white [40609]
• When the Flying Automation Lane is enabled, only tracks with automation show the blended dot in the bottom left of the track header [40197]
• Export audio dialog shows 1.1.1 again [40440]
• The interface’s Content Scaling Factor is now a percentage again [40622]
• macOS: Mouse interactions with devices no longer stop notes held from the computer keyboard (a regression) [40374]
• Softube Console 1: Fixed an issue where layers get confused when moving the plug-in [40154, 40156]
Crashes Fixed
• Fixed crash when dragging an automation clip on the Launcher to another track where that parameter doesn't exist [40472]
• Fixed audio engine crash with automation of groove parameters
• Fixed crash when moving a time selection of automation in the Arranger, via the Detail Editor Panel in Clip context [40102]
• Fixed occasional crash when quitting if the dashboard was currently loading content [38847]
• Controller API: Fixed crash with certain controllers (e.g., Novation Launch Control XL when using anything but factory template 1) [39532]