Colin Nicholls

We're probably over-thinking it ? Suffice to say, it's a good idea to tweak that muted clip not color.

Experimentally. And a hunch.

When the LUMINANCE value of PRV Grid Background changes from 119 to 120, the selected note colorization behavior changes polarity (White to Dark) . I believe it is built-in coded behavior.

In TUNGSTEN, yes. I think that is worthy of a feature change request. In MERCURY, no. It is quite a reasonable default for the light PRV.

I initially reverted to 2021.01. Then I ran Cakewalk_by_BandLab_Download_Setup_1.0.0.013.exe. I thought I was installing the installer, if you know what I mean, but it appeared to go ahead and install Cakewalk By Bandlab twice. I ended up with two separate "Setup has finished installing Cakewalk By Bandlab on your computer" dialogs on the screen, simultaneously. I'm wrong, it hasn't finished. After I closed those two windows, it started a progress bar for installing Studio Instruments. I don't think I had those installed here on the laptop before so maybe that is expected. Still, apparently that install didn't start until I had closed the other two "finished" dialogs. I will try and reproduce this. UPDATE: I think it was a consequence of checking the Add-ins installation. When I left them un-checked (they are, after all, already installed) the installer seemed to work as expected.

I think it is on by default. I have an almost-default-install of Cakewalk on my laptop and it is set to Hide, there. UPDATE: it isn't even persistent between launches of the application. You have to chose to in-hide mute clips, each time you run Cakewalk. The default white is actually more-than-adequately visible in Tungsten, almost too obvious. And in Mercury, it is just visible but, yeah, could be more obvious. So grey would be a good compromise and work in both default themes, to boot. I'll add a recommendation.

Confirmed. Document updated to reflect, and uploaded. Take as many internet points as you can hold in your fist, from this narrow-necked jar.

Okay this took some time to figure out. Using a new empty project: A new, empty track will show Impression 1. When you Archive it, it will show Impression 5. (You can't Freeze it, no clips) Recording a clip into the track with show Impression 6. A second, new empty track shows Impression 1 (of course). If you drag a clip from another track into it, it shows Impression 6. Archiving or Freezing these tracks will show Impression 6. So, I think this is explicable, expected behavior, and we can document it as such. HOWEVER. I have my Theme-testing project that, when I open it in Cakewalk, shows an Archived track, with clips, showing impression 5: If I un-archive it, it shows Impression 1 (but it has clips!!!!) If I freeze it instead, it shows Impression 5 again! This is the only track that behaves that way. So, for some reason Cakewalk is confused about the status of the track and is using take lane button impressions as per an empty track. I'm gonna go with "Cakewalk is confused about this specific track. See above for normal, expected behavior". I guess YLIP needs another update. Thanks for keeping me honest.

Hmm, you might want to double-check that. My research indicates that impression 5 is used when the track is Archived. Frozen tracks show impression 6. However, I do see that the YLIP doesn't reflect this, so I'll update the doc, and award you 1 internet point.

Hi Simon, Unfortunately Bandlab doesn't make these types of resources available. So the only way I know of obtaining such without actually putting in the work to create them yourself, is to ask nicely if an established theme designer is willing to share here on the forum. Personally, I have spent countless hours building libraries of multi-layered versions of many, if not most, of the Cakewalk graphics. Forgive me for not wanting to just give them away at this time. One trick you might find that meets your goals with minimal work is to find an existing theme with images that are close, and use your graphic editor's hue transformation tools. Paint.Net allows you to take an image and move the values through RGB space; along with gamma and brightness, contrast.... you can achieve a lot with just a flat image and comprehensive transformation tools.

Please post this in the Feedback Loop forum.

You misunderstand me. The colors of the slider (or text) for all controls can be changed to whatever color you like, so long as they are all the same color.

We do. They can't.

Erik, your tweak for the clips is definitely working for the max.wave option. There's a lot to like in this theme, and as I've said before I'm loath to be critical but we all have to recognize the theming is intensely subjective and everyone is different. The clip background color is, to me, not quite right. In the context of the application UI, they seem "washed out" to me. If I wanted to use the theme, I would abandon the "dark on selected" goal and flip it so that the clips were normally quite dark, almost black, and then get successively washed out as they unsolo/mute/archive etc. I find the PC EQ Grid on console view strips too bright, especially on strips that don't have PC enabled. I'd go darker on the grid lines. But that's me. I'm not designing the theme, you are.

I like your style. It would take some getting used to. I normally run with "[X] Maximize waveform height", though, and it doesn't work so well for that option. She's a hard road creating the perfect theme, boy. Good on ya, mate.

If I recall, if you put a border/transparent row of pixels down the left edge, it stops this behavior - maybe you accidently did that?

It's the first time I've needed to "zoom in" on an image when pasting it into the document. Usually it's shrink to fit. I realize that my running at high PPI makes spotting things like this very difficult.

Document has been updated at the usual location

Wow. Incredibly good catch. THREE INTERNET POINTS to Matthew. I'll update the YLIP with this crucial information. ?

Um, for me in 2021.06.0.041 it still appears to be behaving as expected. I use "Lock Module Order and Centered" all the time, and the control bar background color is definitely coming from the theme's medium custom background. Are you sure about this?

I ran Cakewalk on my laptop today and noticed the console background has gone back to normal grey, from the unusual white. I have not changed or updated the theme in anyway. Or updated Cakewalk. There is definitely a random aspect to this, assuming it is the same issue which frankly I can't believe it isn't.

Well, they say imitation is the sincerest form of flattery or something like that ? It's a nice theme overall.

I think it's intended to be right-hand corner triangle = Mouse Right-Click to open

Not automatically. IF you haven't bounced in the project, AND the vocal track is stored in one file, AND your replacement file is the same length, then, MAYBE you could locate the file name under the clip and then do a file system level file swap, saving the replacement as the same name as the "original".... And then maybe Cakewalk won't notice and will load the project and you will have your revised audio in situ. Let us know how you get on. Back up your project first. Including the audio. Are you using Per Project folders yet?

I've noticed this on my laptop, but not on my tower DAW. Same theme, different appearance. I couldn't figure it out. I'm glad someone else is seeing it.