Will.

JEEZ! JUST INSTALLED THE NEW UPDATE AND ALL MY SHORTCUTS - GONE!!! UPDATE: NOT EVEN MY SAVED TEMPLATES WITH ALL MY KEYBINDINGS, I STORE ON MY EXTERNAL WORKS WHEN I IMPORT THEM. UPDATE AGAIN: NOR, IF I BIND NEW KEYS SAVE THEM CLOSE CAKEWALK AND REOPEN THE DAW!

Yep. Once we start start a request that will benefit everyone it keeps popping up. ? At the moment there's workarounds, but having it directly from the track would be a plus.

You really need this, huh? ? Pretty sure you've let loose a few bombs out from time to time on this. We had a long previous discussion on this. Also one that you've posted late last year.

Requested already

Bumping up.

Well, giving solutions that fix a problem is called "helping" the next person - not so? Create another track with the same VSTI and preset. Drag all its effects and midi data down on to the newly created insert (NOT A DUPLICATE CREATED TRACK.) So, you have to scroll up to the insert menu and insert the same VSTI (Serum with its chosen preset) from there. NOTE: if you save the preset, it will save the lockup (pop and the no sound information) within the project - unfortunately. I'm hammering on this cause i experience this a lot, with certain projects even with Kontakt stuff. The same information i'm giving you now was given to me by one of the staff members. I just happened to figure out quicker workarounds over the years from the advice they have given me. When you do find the culprit track with the VSTI or Plugin effect, you need to contact that developer with your complaint with version model and which preset (if you want to go through all that channels.)

That was two days ago. Plus, music creation and IT are two vast and widely allien worlds from one another. You cant just check the effects on the master buss. You have to go through each one in the project and then save the project, close and reopen, until the effect/Vsti causing the problem has been detected. This happens with even the most expensive and popular plugins. Whether its Fabfilter, Waves, UAD it happens. Why? I can't tell you. I wouldn't tell you something I experience from time to time, knowing exactly that I always need to remember this, when it does happen. You can't predict when this will happen in a project, but it happens. If you don't want to take my word for it - oh well. I did try and help.

I think you're missing the point. The H/W faders is not needed if and when you can change any bus to the Main Outs and Interface Outs. It might work with a Digital mixer or like the ICON mixer controller maybe. I don't own a digital mixer to test, but I have have access to the ICON which I can test next week. Even then, I don't see the reason for it.

But no other DAW has it.

There are a few interfaces that has a mono switch, it would be nice to have one on all interfaces including an on/off switch.

Definitely a plugin or Vst. If its one of the effects: Disable one by one to test. Once identified remove the effect resave and use different one. If it is a VSTi do the same, mute the track to identify the culprit, once identified do another insert and copy everything from that track to the newly created one.

In the Track view locate the OPTION TAB and remove Autofade. There will come a time when you're going to need it on surgical editing/comping when clips overlap each other, without having to drag the clip back.

You mean currently, yes. Its disappears on twh current menu list when you have over 150 plugins in a project. ??‍♂️ I still think the current section in the list needs to have subfolder for it. Outputs as a Subfolder, Effects as a subfolder and Sends as a subfolder in the current list when working in the Console view.

True, but . . . Rethink this quick. What is the difference between teh H/W and the bus besides the independent L&R channels, faders snd that you cant add FX to it? Actually zero. Doing this on the Master Bus works exactly the same . . . ??‍♂️

No need. You just need to highlight the clip

But its not "Quantization" that's just snapping the clip to the grid.

Here's the thing. When you do . . .you need to be precise and accurate with your request of explanation to them. Reason: You'll need to keep this in mind as Cakewalk has a Master H/W Output Strip to not confuse things.

To Quantize Audio in Cakewalk: Select the audio clip you want to quantize. Press Alt+A to open the AudioSnap palette. Click the Quantize button in the AudioSnap palette. Most users confuse transients snap with Audio Quantization, but this does not mean you can't use it too. Locate the edit filter box and click on it to Assign the track’s Edit Filter control to Audio Transients.

Main Outs are the OUTPUT you use as your "MAIN OUT" such as your interface/mixer OUTPUT. Interface/Mixer L Interface/Mixer R Interface/Mixer S These are your MAIN OUTPUTS. Another EXAMPLE on the signal flow. Guitar > Interface Input> Pro channel> Gain> FX bin> Sends> Pan> Fader> Output.

Main Outs are the OUTPUT you use as your "MAIN OUT" such as your interface/mixer OUTPUT in your I/O. Interface/Mixer L. Interface/Mixer R. Interface/Mixer S . These are your MAIN OUTPUTS.

I think you've kinda complicated things for yourself in the previous thread. Cakewalk does it pretty much straight forward as expected, so i'm good. Give yourself another month and you will revisit this with an "AWW-Okay" moment. Like you've said, your still new with the DAW so you're failry comfortable with how your ther DAW does it. You'll get use to this workflow. I'm Twelve years with it.

That is actually the direct monitor buttons. Don't know why they took this route with it. Theres actually no difference between them other than it is placing the signal in either Mono/ Stereo for "Direct Monitoring in Zero Latancy" with the USB switch being the pure system signal.

Direct Monitor puts the Interface in Zero Latancy. Sorry, I can't help any further on this matter. Which I knew what was really wrong, but at this moment it's a guessing game. I personally didn't experience any of the above problems mentioned in the OP. I too, use active monitors and only experienced about -3dB difference when Direct monitoring was enabled. Its not really something i (personally) would ever need. This being said: There was a difference other than the -3bB decrease in volume. Even with the Apollo twin which I use on the Mac its there. All I can think of now is to try and clean out you fans in your system. Grab a brand new paint brush, remove the cpu fans and dust them off also check some USB HUBS (if you're using any.) Also, replace some thermal paste. Your latancy might be related to something else and not Cakewalk or your Interface. You'll get it to work right, im sure.

Maybe. Try switching on Direct Monitoring on the DUO. What happens if you lower the size of your sample buffer size in the interface's settings? That will also cut down latency times. Factors that can introduce latency, are your CPU, the current DSP/processor load, your interface, interface driver quality, sample buffer size, your USB chain and sample rates. Also try lowering your project sample rate to 48000/24bit and do some tests.

USB ports and cables also play a small role in this, so try a different USB port. I think the DUO is use USB2.0 ports. You could also try this with your TASCAM. Were you recording vocals?