Colin Nicholls

Just to be clear, they were labeled "TBD" not because I couldn't find them, but because I considered them obvious and put them on the back-burner 😁 I appreciate Starship's drive to experiment with alternate expand/contract icons but I'm not sure I'm totally on board with it 🙂

This was working in 2021.04. I wonder why that changed?

The Assignable Control Name is colored by Console View > Control Text and Values The shaded "level" indicator is Console View > Slider EDIT: (YLIP document updated and uploaded.)

Warning - restart of Cakewalk is required to respect color theme changes for these Assignable Control items.

You watched Creative Sauce too, huh?

Does the effect persist in an exported audio file?

@Stewart Cormack, you need to start freezing tracks (with FX) to see if you regain smooth playback. What FX are you using?

I have no idea what the Moody Blues guitar tone is, unless you're just looking for a "moody" blues guitar. Might I recommend SwankyAmp? It's very nice.

Well, it is a display-only thing. it has no effect on the note events being recorded or transmitted... That would be nice but would be a problem for viewing multiple MIDI tracks together in one PRV, which I do a LOT. My solution was to have multiple stickys on my 88-note keyboard. I tried it on my 4.5-octave but hardware transposing puts it all out of wack

MIDI Notes, Names, and Numbers

@ian cummings, you may want to try looking at Edit > Preferences > Customization > Colors and see what these are set to:

Go ask a coral reef why it isn't a cube. Yes, if you look in the Case Study section, you'll see screen shots of selected clips and they all show the black clip fade.

Yeah, that's a bug in the document. My "Theme Tester" project has clips named "selected" but I have to remember to actually select them when taking screen shots. In the case of that latest addition discussing color prefs, I forgot to select the clips before snipping the image - because I wanted to highlight the clip fade color, I wasn't thinking that the clip name would be misleading in the image. I guess I'll have to fix that, next time I touch that part of the doc. Track view / Clips Pane / Clips / Tracks 1,11,21. . Background, etc You got it.

Yes. SONAR Platinum (at least the producer edition for sure) came with some third party pluygins, rapture and Dimension Pro, which are not available in Cakewalk By Bandlab. That said, if you have installed Platinum already, you'll still have access to these installed on your computer, in Cakewalk. yay!

(second attempt at reply, first one vanished(!)) Thanks. I agree with you about -12 not being conservative; I've updated the post. I don't think I'll post before/after samples - it's pretty subtle, and not my music, and also the post is really about the process and not the results.

No rumor. I just decided to express appreciation for a long-neglected (due to maturity?) feature.

I remastered a commercial CD from 1986 for my own entertainment, and documented the process. Maybe someone out there will find it useful. It's not meant to be super-in-depth, just "here's what I did". Blog Post: Mastering with Cakewalk Topics covered: Early CD releases and millennial remastering attempts Using dual signal paths for comparison Loudness and LUFS EQ and Compression

I have a laptop with onboard audio (Conexant ISST Audio) and when I installed Cakewalk, it used "WASAPI Shared", and I see similarly that the buffer slider is set to FAST and not being able to change it. If I change the driver mode to "WASAPI Exclusive", then after some futzing around with a message relating to bit depth being not supported, I can re-set it to 44100 and now I can adjust the buffer size. You might want to try this and see if you can get different behavior, just for experimental value. Also WDM/KS might be worth a try. (Although ASIO is offered as an alternative driver mode, I don't have an ASIO driver installed for my onboard audio and chances are there is no such thing. Don't try to use ASIO with on-board audio interfaces, unless you know what you are doing.) EDIT: Actually I see @John Vere's excellent video kind of covers all this already.

Fair point, although my own personal theory here is that the track actually does change state, from "old-school track" to "new-school track with a lane" and the show/hide button reflects this state change even though it has limited practical use to the end user, as you point out.

When Workspace = None, then everything is available and I wasn't suggesting otherwise. Anyway, Noel has confirmed the behavior and I'm mostly okay with it. However, with Tempo Track, Arranger Track, and Video Track all sharing that space, you can't trust what you're going to see if you try to drag the separator down. Best only ever use the keyboard shortcuts.

You problem is unfamiliar to me. Can you try to recreate this from scratch using a new empty project, and as few elements as possible? In the process, you might identify the issue.

Does this happen with a new, empty project? Try creating a new project and adding one MIDI track and recording a couple of notes. Does it drop out immediately? Try bypassing all FX (see Mix Module). Does it still drop out? What Audio Interface are you using? External, onboard, RealTek Audio? Etc? What driver type? ASIO? Are you using ASIO4ALL? What are the buffer settings?

I used to feel the same way but I'm warming to them. Anyway, your comment makes no sense. My suggestion in NO way would force you to use Workspaces in order to access the Video View.

Noel, sorry to piggyback on this, but is it a bug that the Video view is still available even after using a Workspace that has removed it? It doesn't appear if you press "V" obviously, but you can still drag down on the separator accidentally and reveal it. Of course "V" doesn't make it go away - you have to drag up on the separator to hide it. I would have expected the view to be completely unavailable. (and ideally, free up that strip of real-estate in the Track View header)

Hi Mario, This might be better posted in the UI Themes forum. If you have trouble with themes you have created in the past, or current themes, we can help you out. TUNGSTEN isn't a legacy theme. It's the default theme. (Well, one of two). I don't think I'm seeing what you're seeing: Looks pretty clear to me. And the ARM TRACK button doesn't seem to be tripping. I don't really see how this could be made clearer.