Will.

That's because this is the global input reading.

Try that with gain and see how far you get.

Can we get Cakewalk to reset different volume/gain and pan values to 0dB simultaneously, with the CTRL+FADER/GAIN/PAN-POTS DOUBLE CLICK command key - when tracks are highlighted in pairs/groups, or all.

I'm not talking about instrument tracks. I'm talking about regular Audio Tracks - NOT INSTRUMENT INSERTS. When inserting a SAMPLE, I want to choose MONO or STEREO from the dialog box. Same for the PC insert button shortcut. The SAME goes for recording VOCALS /GUITARS. And every time I press the INSERT key it should keep the memory. A

I dont drink: but, I will definitely raise a glass to this right here. ?

Too much effect of the Console and Tape Emulators (The more tracks you add, the more of the effect is being added.) It could be the recording too at "high volume" or fan noises. It could be anything - as there's not enough information for us to go by.

+1 it would be nice see a facelift to them.

Glad you ask this . . . There's no way when inserting a sample to choose Mono or Stereo output for it. The same with the add track menu - shown in a previous reply above OR by shortcuts CTRL+T and the INSERT button (One I use a lot during recording) and they dont follow up previous settings.

I know your thread is about the Sonitus Multiband, but I just want to elaborate on the idea. I prefer to use the Sonitus Delay on my Drums and Guitars to create a Spread Stereo | Chorus OR Tom Rolls effect. Like @bitflipper said. If it works - well, it works.

I just did a test with this. You can draw in nodes before you record - record you melody or vocal and it works. Though, it doesnt work as how I had it in my head - LOL.

Do you want cakewalk to draw nodes in as you record with the envelope itself? Don't get me wrong: I like the sound of it and the idea - but that will come with so many complications and not to mention a messy situation. You gona sit with thousands of nodes, as it will be written in by a fraction of a millisecond. That means, a node on ever fraction of a millisecond value. Even on a 128note or 1/4note - it'll be a messy situation. It'll bring limitation to every send knob, channel fader/slider, and effect - as it will lock up all the information. And having to work every node then, wouldn't be a speedy workflow at all. That's why the straight linear line was the best option with the invention of the Automation in every DAW and Software that uses Automation lanes.

I could, but creating themes are so 2000's and done unattractively with the theme app. (No disrespect) Plus, there's no way for the user to get the exact look or even close as this one because the console need to look the part as well.

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

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

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.

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.

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.

Nope. What's the purpose then?

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.