Will.

Love this answer. I +100 this.

Requesting Cakewalk to adopt the bandlab UI. This just looks so attractive and more modern - 21st century. Doesn't this look good?

I think where this comes down to is the "undo history" feature. I use it a lot throughout my process. My setting on that is set to 999999 - If it goes even that high. I just remember choosing lots of 9's when setting it. With that, I can go back and undo a change I had at the beginning of the project. So I think adding the fader to it would be helpful. That being said: "the revert to" value on the fader works best for me, if I only want to undo the slider value. (Different engineers, Different workflow) I used Mix recall before, that didn't go to my taste - primarily because my comfortability in my workflow is to use the "Undo History." Seriously, I cannot work without. So I agree with you to a certain extend to keep it as is. What if we do an "Undo history" feature of 20 steps on the faders separately? Unless mix recall saves after every movement/changes that is being made by the engineer (I think, I need to work with mix recall more often.)

Try doing a re-install of the EA. If that don't work, i suspect its a plugin at render that's causing it to crash. If you have a favorite VST2 plugin in the Bin - download the JBridge file.

Requests should be placed Here I too requested this years back. The feature is indeed annoying.

Funny that this should come up again - as I was the first to complain about it. 😅 Which, I'm fine with now. We get use it - changes happen. But to solve this problem once and for all - best solution would be, to allow for Renaming Inputs on the Console and Track View. More user flexibility that way?

Yes, It's exactly as you say: It interrupts workflow. I've got mine set to every 1 minute (if there was for every 10seconds, I would select that too.) but right now it's a pain. After all these years and finally giving it a try for 3 days - yeah! It's a pain. A crash (havent had these in a long while,) after an Auto Save sparked this request. Some improvements to have it running in the background, would very much welcomed.

Loop points also don't follow global tempo changes anymore. If a sample was (let's say,) 150BPM and you drag it into an empty project and change the project tempo to match that of the sample you want to use as the main tempo of the project - Cakewalks loop points used to follow these changes up until the previous update of 2021.06 [build 032 - i believe it was.]

When section is highlighted, it is important not to forget to press SHIFT+L to actually set your loop points for the region/section you want to export in Cakewalk. The blue points are just indicators. In logic, these loop points gets set automatically by the daw when you highlight a region. Most DAWs have this feature - where just by highlighting a section/region the project loops are created. It would be nice if we could adapt it too. In cakewalk when a region is highlighted only the blue indicator loop points are created. We still have to manually activate the "Project Loop Points" by pressing SHIFT+L.

Although, I haven't had any dropouts in a while (Can't even remember when last) - this feature is welcomed with opened arms. Great work guys!👍 Hawks eye activated.

Requesting Auto-Save to run in the background to have cakewalk in focus at all times.

I confirm this. This happened to me once in the week, but I thought i'd mistakenly pressed wrong - an EQ opened up.

@msmcleod Great news. Thanks a million.

No. When inserting an Audio track select the appropriate inputs for the channel. I believe your interface has 2in/2out. Normally your right input on your interface is for guitars - so input 3/4(mono left and right) and 3+4 (Stereo) should be the right inputs. Arm the track to test this. Im not too familiar with behringers interfaces. All I know it that they use "Asio4All"for their drivers. It would help to send some pictures.

What does the output inside the replaced synth reads? Seems like the plugin don't recognized the outputs.

Nope. What's the purpose then?

Are we getting new plugins? 😀

Too you it doesn't, yes. I'll break this down for you. The more space yo use on the system drive the slower it becomes. Every single thing you install - gets installed on the system drive. You can't install cakewalk on your samples drive - can you now? So all your other drives runs through your system drive. Less space - the harder and slower it reads these other disks. That brings latency too. Windows holds a footprint of your open files while its active which you will find in your Temp folders. It's in the name "Operating System."

Yes, I agree. But a copy gets used by the System drive before saving it to the project path/drive. It's the rule windows.

Theres a difference between Factory libraries that requires them to be in the same space and Path as the installation and custom libraries. Some are 12GB by factory. Omnisphere too. We all know to put sample packs on a separate drive. 500GB for system drive is definitely small.

Best choice. Definitely too small. Plugins like Waves, Perfect and Addictive drums, Kontakt (to name a few) - all have huge factory Libraries that comes free with its installation, that requires the content to be in the same folder/Disk space/path - as the installation files. 2:) Your DAW utilizes the same space for recording as your OS drive. So for best results - it is best to have "500GB" free space available to play with for this, so a 1TB for the OS, the DAW and to run your effects plugins is best here. It also eliminates that "Audio Dropout" nuance as well when theres enough space on your disk for speed recovery. (SSD's has its own limitation too.) If they get overworked when theres not enough space they burnout easily. When CPU reaches its limitations it utilizes ram and disk space too.

I've got a fellow mixing engineer that has the same problem with UAD plugins in Cakewalk. These answers look promising - I'll pass this on to him.

For this to work if you don't have an Audio Interface. Download the demo version of FL Studio and use it's drivers (FL Studio Asio). It ×10 better than Asio4All and the drivers available in Cakewalk. It's a great hack.

Feature request for the Hardware Output channels "Mutes" to work independently from the "Link" button. I like to keep the Link Button Enabled to play things safe, but it beats the purpose of listening to the balance on seperate channels independently. Or add the Ctrl+Click to mute the channels separately alone.

This comes back to what I have said earlier. It makes it a little confusing at first, but getting used to it. I think for a long time we were used to the Old Names. In fact it's good to slowly move to the language other daws uses in their routing. We just need to get that separate Mono and Stereo track insert strips on both Audio and Instruments now. 😅