GreenLight

This bug is reproducible with Cakewalk 2021.12 (Build 102) as well. I have now emailed support@cakewalk.com.

@msmcleod Thanks, great tip! I have used that way a lot but totally forgot about it. It would be great if the bindable rename clip action would work on multiple clips in the same way. As I say, "Always think about the keyboard". I always look for a way that requires less mouse clicking. Example of how quick it could be: Lasso clips Hit your Rename shortcut (mine is SHIFT+ALT+R) Type your name and press enter Done.

Whoa, cool! How did you bring 5 500 recordings together?! What kind of monster-setup do you have?

Neither are mine... and never will be, but I don't define success in music by that. It sounds like a cliche, but the goal is the process!

Might be worth trying to bump this again, just for fun. ? A sentence or two about what you use Cakewalk for... I suspect there will be a huge range of use cases here!

It would be really convenient if the Rename Clip command would support the renaming of multiple selected clips. More batches to the people! ?

It would be awesome to have an "Export/Import" settings feature... It would also be a good way to backup a "last known good configuration".

If you have "Bounce buffer size" set to "Playback", I believe the export speed is supposed to be the same as before. If that's what you meant? ?

Ah, the bug requires a very specific circumstance: it only occurs if the track in question is below a folder track, and that folder track itself is the first track in the project. (Compare the order of my tracks in the video compared to yours in your image.) I clarified the folder track "requirement" in the original post, thanks for pointing that out! ? About your second issue - yeah, I think I've had that too... let's see if we can figure out any repro and/or consistency to it... ?

Will try this, thanks @Bristol_Jonesey! I'll give staff a few days to see and reply here, then I'll email this bug report to support@cakewalk.com to make sure they notice it.

Thanks for the Sitala tip, looks simple and fast but powerful! ...but let's just for a second entertain an alternative future. Imagine the sweet and fast workflow of dragging a sample from the browser to, say, an audio track and voila - suddenly you have an instrument track with Sitala (or something similar) that has your sample loaded. One drag & drop and you'd be off sequencing audio samples - 808s, cowbells or even slap basses, whichever floats your boat... Update: This has been discussed a few times earlier:

Thanks a lot @billp and @Klaus! Another workaround in addition to yours, Klaus: once the nodes have been created, one can switch to the Move tool to drag the section all the way up. Let's hope the Bakers see this thread.

Hi all! Can someone please help me reproduce this bug? I have been running into it for a long time, but just now I figured out how to reproduce it. Cakewalk version This bug is reproducible with Cakewalk 2021.12 (Build 102). (Updated Jan 9, 2022) Short version: Using the region selection with the smart tool, one cannot drag automation to the maximum if the track in question is a) below a folder track and b) that folder track is the very first track in the project. Steps to repro: Start with a blank project Insert a track folder at the top Insert an audio track below (but MIDI tracks have same bug) Enable automation for, say, volume, and make it a flat line at the bottom Using the smart tool, drag a range in the track and then position it near the top of the track Try to drag the automation range to the maximum Video demonstration In the video, I first demonstrate that dragging works OK with the track folder below. Then I place a folder track above, whereby I no longer can drag the automation to its maximum:

The dotted outline on the waveform indicates that specific portion has been muted with the mute tool. To unmute, use the mute tool and drag in the lower part of the muted part. See details in the manual below. (Maybe the PDF manual is more up to date, but I think the online version below should be accurate.) Mute tool https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Tools.16.html All the best! ?

I need to try it, it IS conveniently located... I guess I've just been wary of built-in effects, somehow I have perceived external VSTs to be more reliable over time, with version changes and upgrades. But maybe it's the other way around? ? I agree. I am familiar with the side-chain concept in hardware as well and I think Cakewalk (and most other DAWs with a long heritage) have imitated hardware routing, it's a natural studio evolution. That said, I believe Cakewalk could simultaneously offer other routing options as well, while still keeping the options of the old paradigm. An example from Live: you select two audio tracks and press CTRL+G - an aux track is created, the selected tracks are grouped and routed to the aux. It's brilliantly modern, simple and FAST!

Hm, you're saying that Cakewalk's sidechain routing concept imitates hardware? Yes, I suppose that's very likely, I believe most older DAWs do. About PC, I have to confess that I'm not using ProChannel at all... and never have. Maybe it's time to start?

Hahahaha, brilliant! Loved this, laughed extra at Samplitude and Cubase! ? And you Cakewalk description "Fun for everyone, but it's especially loved by men over 35 who think that anything newer (which is just about everything) is for kids or dilettantes." is frighteningly accurate... ?

I am not a car person... but what kind of a car would Cakewalk be then? A ?or maybe?️? ?

Thanks @Jim Fogle! All methods listed above are currently still valid in Cakewalk, they differ due to different pre-requisites and needs, like if your sidechain plugin is inserted on a track or a bus. But method #1 (Will's method) is my new favorite, as it's quick and only generates a bounce of the original track (of course with the sidechain plugin effect printed), but it skips bouncing an unnecessary copy of the sidechain source track, as method #2 does. Sidechaining tracks from kickdrum tracks isn't probably as common as it used to be, since doing the same with a VST ducking plugin instead is a lot faster and simpler. And with such plugins it's easier to freeze audio tracks and VST instruments without considering any dependencies to other tracks. But if one needs to feed the sidechain input with something more irregular than a kick drum, then "real" sidechaining is still the way to go.

I thought I'd post this for a discussion and for easier referencing in the future. There are several ways to bounce tracks and buses (tracks are easier!) with side-chained plugins. I think this one that @Will_Kaydo told me about is the easiest (see embedded video at bottom): Bounce tracks with SC plugins using Source Category set to Buses - It requires that the track you want to bounce ("original track") is routed to an intermediary bus (say, "Synths"), before going to Master, and you select your "Synths" bus as a Source Category instead. If you would do this while the original track goes straight to Master, you will get the sidechain source audio mixed in (assuming it's an audible track). A couple of other ways I've done it in the past: 2. Bounce tracks with SC plugins using Source Category set to Tracks - This is how I've done it for years, with sidechained plugins according to the Cakewalk manual. In the Bounce to Tracks dialogue, select both the original track and the sidechain source, and set Source Category to Tracks. It works, but the downside is that you get two new tracks, which is slow and also a slight nuisance to have to delete. 3. Bounce buses with SC plugins using Source Category set to Entire mix and a silent sidechain source - Create a copy of your source (say, a kick drum track), set the Output to None (this will generate warnings at project load, though), or turn down the fader and set send level to pre-fader. Use Entire Mix as Source Category. The pros are that you can bounce it without it being audible and you can easily create pumping/ducking effects even when your kick is muted. But the downside is the increased project complexity. It was a few years since I did it this way, and nowadays plugins like the LFOtool are a way easier. Hm, did I get all things right? Please chime in if you have thoughts or improvements. Will's great video:

If you want, send an e-mail to u-He at support@u-he.com and describe the problem and product version numbers. I hadn't heard of TyrellN6 actually... and I see it's freeware. Is it good? How is it compared to, say, Diva?

Thanks for the u-He message, good to see that they apply the Cakewalk fix for their whole range. I agree, u-He has a great attitude, makes for great teamwork. ?

Woho, this is great news! That annoyed me so much. It was in fact yours truly who reported this very annoying bug to u-He and then Noel helped them solve the Cakewalk interoperability problem in Diva. ? Apparently u-He has some logic in Diva that checks whether the project had finished loading, that didn't work well with Cakewalk and that messed up the loading of the quality settings. Noel came to the rescue!

This bug has now been fixed by u-He in the Diva v1.4.5 update last week, fantastic! Now I don't have to manually change the settings of all my 6 or 7 Diva instances to "Fast" and "Best" every time I open a project... Thanks @Noel Borthwick for helping to solve this together with the u-He team! ?

Small tip✔️ – For years, I have had a custom keyboard shortcut for "Start/Stop Audio Engine" bound to ALT + X. It has become second nature for me to stop the audio engine when not needing an immediate response from Cakewalk. I also always stop the audio engine before saving a project, that way saving goes faster as well. Is idly running plugins and instruments an issue in all DAW's? I know the VST3 standard does include some kind of feature for plugins to to not draw CPU cycles when no audio is passing through... wasn't support for that implemented in Cakewalk recently?