Please restore the theme editor

[happen135]

Looking forward to the restoration of this function

[Starship Krupa]

7 hours ago, sjoens said:

This may help

Wow, huh, very interesting. My guess was that it was an in-house tool which was then released to the general population.

If Cakewalk used it to create Tungsten, then I was sort of correct, except that it wasn't originally created by them.

Was Tungsten something that Cakewalk created using Theme Editor? IIRC, there's nothing to Tungsten that couldn't have been done using Theme Editor.

It would explain the botched MIDI Inspector strip image that I noticed and reported.

I notice that TTSRES.DLL is still around.

[sjoens]

It's the main file for GUI display.  TTSImage.dll removed the images from it for user themes and theme Editor.  If TTSImage is still around it's mostly unused left overs from a now long-forgotten age.

On 8/8/2025 at 7:41 AM, Starship Krupa said:

Was Tungsten something that Cakewalk created using Theme Editor?

Basically but it has a unique file extension over user created themes: FTH vs STH.  They are the same format and extensions are interchangeable but FTH files have to be in Cakewalk Core folder and STH files have to be in Cakewalk Themes folder to be seen in Preferences.

Edited September 11 by sjoens

[happen135]

The font size on the toolbar is too small, which makes it difficult for my aging eyes to read.24 inch monitor, 1920 * 1080

[happen135]

Top up this post just to catch the attention of developers. Please remember us for the next update

[Michael de la Motte]

Hi All

I used the colour scheme/theme called Polar Blue which I believe was designed by Steve Cocchi,  Perhaps the Developers might be able to include an option like this in the future.

Regards

Michael

 

[Starship Krupa]

On 9/24/2025 at 2:22 AM, Michael de la Motte said:

Perhaps the Developers might be able to include an option like this in the future.

Cakewalk teased adding more user options for UI customization about 7 weeks ago on Reddit and in this forum. My guess is that whenever it comes, we'll get more control over colors. From what I understand, changing graphical elements is a different ball of wax from SONAR/CbB. Those programs used static raster images whereas the new UI uses vector images.

Custom theming was a feature that helped draw me in to CbB, and I wound up making several of my own extensively customized themes. The thing I most want control over is color. My goals with the themes I made for myself to use were to give them pleasing and more visible colors, make the buttons as flat as possible, and design buttons that conformed better to current industry iconography. 3-dot options menus, turny triangles to open tree menus, etc.

Those last two have been taken care of with the new UI, so if we only get color customization, I'll be happy. The biggies for me are Track View grid lines and Browser text. Despite preferring dark themes to light ones, I sometimes use the Mercury Classic color scheme just because the Browser text is blue instead of off-white. Light grey text on a dark grey background just feels to me like it's 1988 and I'm on a monochrome monitor.

Although I always at least had green or amber monitors, so it wasn't even grey on grey.

[Mark Morgon-Shaw]

13 hours ago, Starship Krupa said:

My goals with the themes I made for myself to use were to give them pleasing and more visible colors, make the buttons as flat as possible,

I despise the flatness but if they were  gonna do it they should at least have implemented some colour pop. I just tried Bitwig and it's vector GUI is so much clearer than CW-Sonar . Hate it as a DAW though ! I think if Sonar dissappeared tomorrow I'd be a Cubase user. 

[Starship Krupa]

8 hours ago, Mark Morgon-Shaw said:

I think if Sonar disappeared tomorrow I'd be a Cubase user.

Verily, it is said to be popular in your field.

Lack of volume and pan controls in track headers makes Cubase a no-go for me. I learned about that in one of these "give us back our theming" threads. Still makes me shake my head.