Will.

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

Then you have a serious problem on your system. No one on this forum ever complained about them. Maybe you should contact their support team. Fabfilter never give problems. Try to remove the VST 2 DLL file if you have it installed. If you would like to keep it . . . get the JBridge Software to convert it to 64bit.

Been working fine here for 2 years. Make sure it's in the correct path folder and that your 3.5dotNet is updated.

Why doesn't the "flatbed menu" work on plugin preset menus too?

Can we have the "Bounce to Track" to commit the midi file to "Audio" as a shortcut on the right click menu on the clip too.

Exactly.

Don't know why you're repeating what I've said.

100% Agree with you. But there's also room for software intelligence.

Bro, I'm with you on this one too. ?

Just asking: Shouldn't it be that way? Having the I/O to read as "Mono/Stereo-in" | or | "Mono/Stereo-out?" What defines the strips I/O as "Mono or Stereo?" Maybe I'm just confusing myself with this. ?

I Understand. Although it would make more sense for the input to follow the interleave as well. It's not a big deal - just a naming/visual thing. Just thought some might find it confusing to read.

Hi Noel. Thanks for responding. No, I'm sending to a normal Aux track. I'm just asking, shouldn't the input display follow the interleave as well. Example: "M: Reverb" to indicate that it's in fact in Mono on the input too.

Always appreciate new features and changes. Awesome work guys. Been at it for 4hours with no issues to this update. Just a Question: When changing the interleave to MONO on a send aux - shouldn't the Input Names Reads/Change to Mono too? Right now it say's L+R Filter instead of following the interleave on the channel and reading as MONO FILTER (M: Filter) when the interleave on the "FX Aux channel" has been changed.

It can be done in Cakewalk already. It's just displayed differently.

Its just a time ruler format change and not as what/how you describe in your original post. FWIW: Cakewalk has had this for years.

You're referring to "TIMECODE-STAMPS."

? I'm just gona laugh at that. ? You're sending back information i'm giving you in answer here. LAST TIME: Zero is One | and | One is Zero and that's why the count starts at 1. So i'm gonna say this "EXACTLY" a 24hr clock only starts at 01:00 Here's the thing. We've all worked an 8hrs shift before right? But out of that 8hrs you get 1hrs lunch so basically you're working only 7hrs right? So from the start you go on lunch until the end of your lunch - thats "1" hour. not 0 hrs right? Now to come back to you "Wikipedia" research. There's 24hrs in a day correct! But the day ends on iets 23hr with the minutes and seconds making up for it. Now heres the question: what happens to that 24th hr? Answer: That's that "LUNCH BREAK" in your 8hr shift. So now on the world clock that count starts at 01:00 again. So between 1am and 2am thats One Measure. Your 1 metronome measure counts (Or 4 beats count.) So on the clock 00:00 to 01:00 will be your 24th Measure and whole note count. ("96 Beats on a 1/4 Note.)