Will.

Oh -yeah! I see your frustration now.

I on the other hand find the +6db boost to be just fine for me. I never go above +4db boost, well that I can think of ever done - probably has to do with my mic placements. Why don't you try and cut the desired section, normalize it or gain by +6 than boost it with Automation. It's never good to boost higher than +6db, but than again - I don't know your setup and of course preferences. What I can advice is, try to keep it within the "humanize" spectrum, like a +3 or even +6db less than what you prefer to have set. Let the compressor with Automation on it balance things out for you with a human feel by not boosting that high? ✌️

I still think this needs a slider or knob popping up on the area selected, instead of the dragging down method.

With 1909 there were a lot of issues with Windows 10 updates running Cakewalk. Most older vsts constantly required you to a dotNET update manually. throughout the entire build of 1909 - which still remains a flaw in the build itself. The 2004 for me personally? I find it to be heavily hungry on CPU and RAM, which also requires a 32 GB hard drive space alone for installation. So, you need to run an i3 5th gen' or higher to eliminate some of that sluggishness it will bring if you have a less powerful machine. I've been a program insider for Microsoft since 2016. Visually wise, the 2004 is great with fewer issues than 1909. Which brings me to say, Cakewalk ran it's best on the 1809 build of windows. I didn't have any problems with it - also probably because I didn't find any problems with that version build of windows. I also have to add - I was doing all BETA testing on an H81M Msi motherboard, i7 3rd gen CPU, with 8GB ram before I did all necessary updates or upgrades on my studio machine to CbB and Windows. Since I bought this machine 3 years ago, I had to get an extra 8 GB just for the 2004 to run slightly smoother on the "BETA TESTING" machine. Thoughts: 1909 build: Irritably flawed! I've reverted back to 1809 on my studio machine running Cakewalk before the new 2004 build was launched. 2004 build: Highly recommended! I find the 2004 build to have eliminated the use of "Jbridge" on certain plugins being used in Cakewalk. With all this being said. Certain outdated hardware attached also leads you to run problems. Therefore always update your equipment drivers too, before doing updates. I'm running Windows 10 2004 build on my studio machine with Cakewalk 2020.09 update without any problems so far.

Well, there's a difference between a "Major upgrade" and a recommended cumulative update of your current windows build - not so? ? Update and Upgrade (aka "Major") see the difference? We upgrade to a newer version and "update" a current build version you're running - meaning, if you're current version is 1903 you'll constantly be doing updates. If you want the new 2004 version of W10, that's an upgrade.

The M-Audio interface, is your "sound card." Just plug it into a USB port on the computer you're owning now. No need to reach for your pockets to buy an extra unnecessary Pc/Mac at all! Just download Cakewalk - it's literally all you need. Ps: Windows 10 should pick up your drivers by itself. If not - update your windows drivers and cumulative updates. I'm stressing on "dotNet3.5." This version of Net frames seem to be a highly important to most hardware and plugins. Think of it as a "Jbridge."

I hear you. This is where I find the Arranger to be more advanced. I've been close to 4weeks at it hours at a time and found that the "Arranger" for me works best. I can easily draw in crossfaders/envelopes, automation, effects and so much more "LIVE" with the arranger than the Matrix and this is what's confusing to me. ? For me they're same. I don't know, maybe I need to watch more video's on the Matrix to understand it deeper. Hope to get a more light on this here too.

Hey family, how is everybody doing? "Question time" and this is making me feel stupid, but first . . . Recently I have taking some time of mixing to spend more time with the family. Well, my hand was forced anyhow - by taking full advantage of the pandemic, unless it's a really important client. This led me to start plying around in the MATRIX window, which I don't normally do - and the newly ARRANGER window. QUESTION: Aren't they the same thing, with one just being more flexible and advanced ("Arranger") replacing the other one?

Once you have all recommended updates of your windows build installed, it should runs smooth. It was never a CbB issue - but a windows update issue, especially not having the dotnet3.5 installed. To help you with some other issues - go here. https://discuss.cakewalk.com/index.php?/topic/16404-solving-known-issues-please-try-this/

Guy's let's not turn this thread into a political debate about plugins - please. Keep the peace. Begging.

Lol! Why would you insist and assume that we have the same taste in food, when I've already said we have different taste in "cars, food and clothing."? That will always be the reality. I love the Sonitus delay, you dont - AKA "different taste." Every mixing engineer has it's own taste in plugins. I'm not agreeing, nor am I disagreeing on the free plugins. Reason for that is . . . There is better plugins, but than there's not too. Again, it's about taste.

@Starship Krupa Try out the TL - 64 -Tube leveler on vocals and tell us what you think about it. Try all 3 hidden plugins. Lazy to type now so I will drop a link on how to get them, if you haven't got them open yet. I think it's the first 3mins of the video.

The thing with this statement is . . . If it gives you a better feel of a 80's chorus effect and depth on drums, vocals or guitars with a second reverb, chorus and delay within your chain - why wouldn't you want to use them? I mean, mixing goes both ways. What sounds "ugly and degraded" can sound pleasing to the listeners ears, and what sounds "clean and beautiful not so pleasing." There's no right or wrong way in sound creation - only taste. We all have different taste in food, clothing, and cars.

This is another reason to why I think this need to be considered, other then "clients asking unnecessary questions all the time." Generating capital and gaining users, it's every brands number 1 rule. So, I'm sticking with my request -- a facelift will be a benefit. I think you've phrased it very well. @Starship Krupa

How do I move this thread to there? It is in the feedback loop forum. ?

This is so true. I never understand the concept of it, because no one question the PT. stock plugins. I use the Tube Leveler on lead vocals often, The Vocal strip VX 64 for it's Deesser and Doubler effect. There's a come back in a few genre's making their way up the charts again the past couple years . . . and that's the "Mid 80's" Pop, Rock and Disco Vibe, the others include the 90's RnB, HipHop and House/electro-house (The Daft punk Vibe) with a modern feel. So these plugins come in handy to bring out that feel.

How is everyone doing? This tread will be on a long forgotten item and request on the stock Sonitus plugins. Can we get a new modern look on it? It is still great plugins, although many might feel otherwise. I still use the Compressor, Phase and Delay on an everyday mix. I use the Sonitus compressor first in my fx chain, followed by other manufactory/brand plugins with a favorite compressor at the end of my chain -- to create a limiting effect on Vocals. I use the Sonitus delay 80% in all my mixes to create a chorus effect on guitars, vocals and snare drums, or to give the drums that slap room effect. Reason why I'm requesting an update to its UI - clients keep asking me why am I using old plugins in their projects. Now I have to explain to them, the why and the "what feel/sound" I get from using them. They still sound great. It is just really embarrassing to keep getting asked that question. So please, can we get that make-over to it and bring them to a modern look? ? W.

I'm writing this thread to help anyone with some system problems especially our veterans. I've read all over the site how users struggle with some issue's directly related to CbB and others not. So here's a few tricks and tips to help. 1: Try to keep your system up-to-date every week. Windows 10 has a scheduler build-in for you to set this feature automatically. 2: Download all recommended cumulative Visual C++ (especially and i'm stressing, "dotNet3.5") updates for your windows build manually. https://www.youtube.com/watch?v=0hjoOnybmpg New Netframe Available: Download latest Netframe 5.0.2 here Best Solution: Download the "All-in-one Runtimes" pack here. https://www.itechtics.com/net-framework-versions-offline-installers/ 3: How to check your windows build for windows 10 users: Go to your search bar, type in "WINVER" and press enter. This will pop up a little window with your current windows version. For "windows 7" users: Go start and type in "CMD" or check out this link https://www.youtube.com/watch?v=dmiMXHsziPo 4: Download and install your motherboard's "Live Updater" app from your manufacture's website. Go to their website and search for "Live Update app" trust me, this will help you tremendously - if not solving all your problems. 5: Make sure you have the recommended system specification, to run CbB fluently. 6: Make sure all your plugins are compatible and that all your analog gear drives are up-to-date. 7: Check your system for faulty hardware and disks. Optimize your hard drive and if possible - upgrade to an SSD disk. The faster your hard drive is, the fewer issues you'll have. https://www.youtube.com/watch?v=toLYV7th0L8 8: Check all your USB hubs. This might seems unrelated, but it does affect your system's performance. Especially if it's not plugged into the correct port. Make sure USB 2.0 hubs are plugged into the 2.0 ports, and all your USB 3.0-speed hubs/devices are connected to your 3.0 ports. 9: Try not to use the color tracks if you don't have enough RAM or at least a 5th Generation CPU or higher installed, as this consumes a lot of graphics and characters causing known and unknown performance issues within the DAW. 10: Try and render/bounce every virtual instrument track to a waveform before mixing. Use oversampling only when you're happy and satisfied with the end result of your mix. Some of these tips and tricks might be outside your systems capabilities, especially if you are still running windows 7, with the new Cakewalk Updates from 2020. 04 and later. Unfortunately how this works is as follow. When ever windows release a new update, does not matter which DAW you use - it has to keep up with windows update. What worked in a previous release might not be compatible with the new update. It's engine constantly has to be altered/modified/update to stay fluently working or at least lessor problematic with the new Windows update. Though this being said - feedback from users is always helpful and that is why it is highly recommended to keep the "User Analytics" box ticked under preferences. I hope this will help a lot of users. I also want to say I don't work for Bandlab - I'm a user like everyone else. It just happened to be that I have dealt with some of these problems some time ago in the past, and have found some recommended solutions that works. W. ✌️

@Marc Bleuwart This could be due CPU overload. Out of virtual memory, over sampling, a plugin that is not compatible, slowing down your system (iZotope, Lurssen) or windows update issue. I can't stress this enough - I've literally had this issue before.

To give you even a more greater experience, download your Motherboards "live updater app" from the manufactures website and update your drivers through it as well. I'm a "Program Insider" for windows, so I'm running the 2004 build before it's released to the public. It's a bit heavy on CPU and RAM - This you can actually feel. Something I have never experienced before, and I'm talking about slow or sluggish, it literally feels heavy.

Do you have the recommended cumulative windows updates installed?

An MSI or AMD computer is your best buy. It is build primarily for the purpose to take the punch of today's video games amongst the youth with its speed, graphics, memory, heavy cpu usage etc. - which cakewalk will demand by making its platform available for plugins to be used within. A strong, speedy motherboard such as AMD or MSI should be considered. This is my opinion from my past experiences with DAW's. Obviously with your quickest "i7 generation CPU you can afford, with Ram cards, (Cossiar) and SSD drive."

@msmcleod Regarding to this issue. Take a quick look if you disable the "blue pre loop indicators" if it solve this problem. When "Copying" tracks by drag and drop - you have to set that pre loop indicator's to you desired selection, in order to copy only what you want it to copy. I think this came with when the arranger was introduced. Now - I might be wrong with this, but I had a work around/something similar before regarding this. Have to go sit later to with this again. I might have used the Ctrl+D shortcut. Wish I was home right now.

Where do I start . . ? Hi team. First of all -- If there's a way to do this within Cakewalk, please let me know. So, I received a project from a client and normally, I would render every stem to be used in Cakewalk. I'd started working on this project yesterday, but in the FLP file it came with. Sitting in studio as I'm taking a break, a thought pop up. Wouldn't it be cool for EDM producers, if Cakewalk had the ability to do automation by tempo sync - much like how "FL Studio" do with "Link controller and Peak controller" combined for sidechain or for any other creative effect with any plugin. Again, if this can be done in Cakewalk - let me know. Imagine how creative those in EDM, Dance, House, Electro, Pop, HipHop can be with this in Cakewalk. Right now plugins will do, but imagine how much CPU load it will spare. Anyway. I hope this spark some good discussions and fill some holes I wasn't clear enough on. ? W.

Awesome plugin and its free! ?Whaaaaaaat?