Colin Nicholls

@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.

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?

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.

Welcome to the club! Is there anything specific about this theme you'd like to tell us about? Did you have goals in mind, while developing it?

Please don't ever remove the ability to run CAL scripts over a MIDI track. It really helped me today with my beloved yet aging Roland A-80 controller that likes to burp CC:65 events while recording. (and if anyone needs a script to strip out CC# 65 from a track, let me know ? )

I've just updated Bandlab Assistant, and after logging in I can see four tabs across the top: Library, Sounds, Mastering, and Apps. "Mastering" seems to be new.

Do you have a trial version of a plugin somewhere in your FX chain?

This was a mistake. That said, I don't understand how that would lead to this: Definitely save your project under a new name in order to diagnose the problem. Usually Cakewalk is non-destructive: all the audio you recorded should be intact and you will be able to recreate your good mix, with effort. Even normalizing - which does "destructively" change the underlying audio files - shouldn't introduce distortion. Worst case, you should be able to re-assemble your project using the files in the audio folder.

I don't understand why, if this is "by design", that there is an option on the Console > Strips menu for selecting "Instrument" tracks only, that doesn't work. It's even documented as working in the manual.

You mean, during playback? Sometimes. Depends on the synth and specific edits I'm making.

I'm astounded that all these new young users aren't clamouring for the Track Layers feature to be restored.

When inactive, yes, they are hard to read. I agree that they should present themselves as visible even when inactive. I see now that "Drop Out" is completely invisible. I'll fix these. UPDATE: Done. ZIP refreshed with v.1.0.4.

@Starship Krupa and I have been talking about this, whilst working on our respective themes. We haven't identified a pattern of when Folder Stats/Notes uses the "correct" theme element (Description Field) and when it reverts to some gradient area.

Huh. Easy to reproduce. That's got to be a bug. There's no way that makes sense. Submit it as a bug!

So tempted to say "yes". No, I added it this morning to reinforce my argument, and then decided it was worth keeping as a feature. So I refreshed the theme.zip in my other post. There may or may not be other enhancements in the theme that _were_ there in 1.0.0 but I'll let them be discovered naturally.

Well well, this morning I get an email from Spitfire LABS about their new free BASS GUITAR plugin/sound set. If you're up for messing around in Spitfire LABS ecosystem, give it a go?