Colin Nicholls

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?

I don't really understand this statement. You could have a terminology problem. Can you describe in more detail your configuration? What audio interface you are using? What is the "amp device", what model? Plugin? Is the crackle always in the same parts of the playback, or random and different each time?

Audiority has an Octaver pedal plugin, super cheap until the end of the month,

@Lynn Wilson, try again please. I changed the link from "http" to "https" and this has made a difference in other cases. I confess I don't know why some folks have problems with plain http so I try to remember to always use https on the URL. Sorry for the inconvenience.

Thanks for double-checking my evaluation of this behavior, Starship. I would agree that Cakewalk's default appearance of the 6 impressions in the button stack is sub-optimal, I do believe that Cakewalk is using them apporpriately. Please review the screencap above (I have refreshed it using the latest version of Flight Deck) and tell me if you still agree with your statement.

I have to disagree. The UI is telling you something, and you're choosing to ignore it. CbB is NOT in the same state. We can debate about whether it is useful or not, but the fact remains, the state of the track is different and it is informing you: the opposite of poor UI. Mute button behavior is not relevant here.

@Kevin Perry, lanes don't exist until you expand them for the first time. Then that track has a lane associated with it, and the button changes to reflect this. This behavior is one of the things I try to highlight in my themes:

Not possible at present. Feel free to submit a feature request in the Feedback Loop Forum.

Nice ... backs up my findings from March. It sure would be cool to support PEEL and other multi-out effects in Cakewalk in the future.

Thank you for man-ual-splaining for us. ?