Will.

UPDATE: Was spending unnecessary long time and losing a day's worth of work and samples over this keybinding story. I think something is installing a weird path to my VST folder in the VST SETTING Tab. It looked something like %LocalAppData%VST3 . . . . something. I than deleted/removed that, and now my keys are working again. So, now I need to identify where this path came from. ??

? I rebuke this. My SDD is 5 years old and honestly, it has been showing some strains lately. This I can confirm. I dont have much knowledge on how an SSD work . . . i can fix a stuck pin of a HDD. Sometimes it lasts another 2/3 years other times weeks/days, but always retrieve everything from it once the pin is fixed. So i know my way around them. With SSD: Well, haven't had the honor in fixing one yet. I'm gonna dig deeper into that later. Right now, this issue with the keybinding hasn't place me in any mood to work in the daw right now.

For me it is not about keeping the settings (Great idea though.) I have done this before, but had trouble learning and identifying the sound of the EQ, because i was relying on the previous EQ's setting. So, my vocals never sounded right. Doing the A/B this way thrown my ear out. You only realize this outside of the DAW on different systems. Reason: The band gain of EQ-A is/might be louder than those of EQ-B including the filter frequencies and might have color you cant hear when copying settings at the time. The same goes with built-in reverb bands/filters. Same goes for compressors and replacing an effect that keeps the settings will just be extra clicking work to reset everything to 0. That's why all my plugins have a preset i call "Empty" that has all its settings/knobs/sliders to 0. I dont believe in saving a preset for a guitar, because I will never use it again. Every time you play a new melody/riff every dynamic and frequency change in it, so using the same preset, will just ruin it. Thats why i say, you never actually learn the Plugin copying setting and by using existing presets | OR | really training your ears to pickup on subtle changes made. The replace thing for me is just for when you accidentally choose the wrong effect in the list, so thats where the replace effect command seem plausible to have, without having to delete/remove the effect first, to choose the one you wanted to grab in the first place.

Well. I've redone my entire Windows OS out of frustrations. Installed Cakewalk and the EA - guess what? Same story even on factory settings and a OS that is not updated. So its bot thst Registery key.

I hear you loud and clear. Try something quick. What happens if you go in preference>project>record and change Loop Recording to "Store takes in Separate Tracks? And under TAKE BEHAVIOUR "Create new Lane."

? I think 2021 was the final year for new ideas. Articulations, Arranger, New tempo, better export settings and huge improvements on SIDECHAIN with tracks/aux (Highlight of the year for me.) This one and the Loop Construction pitch and fine tune button envelope send directly to Automation Lanes/Clip in the track view is a huge prayer and wish my side.

I always work in 64bit engine. Its the first setting i change on every new install. I'll try that registry thing after doing this current install. It didn't work in 27.11. Neither in 27.12 installing 28.02.23 now. (Works if i save, close and open the DAW again.) UPDATE: Back to losing keys bindings with 28.02.25. ? WEIRD! And frustrated now. All my win 10 security is disbaled. Cakewalk is excluded from my Antivirus. I did check for updates on Monday, but things were working fine, just before the update LITERALLY! I was still making a Mono Split and a bounce to tracks. Thanks @Kevin Perry Little frustrated now. Spirit Broken. I'll give this a try with not so frustrated thoughts tomorrow again. Thanks everyone.

I have a new clean OS installed on the system 2-3 weeks ago. Had the 2021.12 again, did the 2022.02 EA update and today the 2022.02.025 when I noticed this try to do a bounce to tracks and inserting a new audio track when nothing worked. I'll do the rollback and give feedback in a few, thanks Jonathan.

Are all your keyboard shortcuts there?

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.