Will.

Yes, the keyword here reads "Groups." So, that means the tracks that you have "Grouped" | or | have highlighted for "Quick Group" by holding down the Ctrl button - to isolate them from the rest of the tracks in the project.

Yes! I'm talking about that. Exactly. To further show how broken quick group are on certain features - pan one track 50L and the other 50R now highlight the two tracks and try to move them to 60% you drag down, but something else happens. ? Definitely with this feature. Anyway . . . I hope this gets fixed. I have been reporting this for years.

You mean the new updates/installation in-app toast notifications?

You're not on the same page. Do this with the faders . . . 1: Set them at different volumes. 2: Highlight them all. 3: Hold download Ctrl and drag down. All of them should be at the floor. The gain knobs right on top of the strips does not follow these commands.

Apologies for that dreadful typos - i fixed it. No, currently it has always just worked for the faders. To test this: Create three tracks or more - set each gain to a different dB level. Highlight the tracks>hold down Ctrl and drag the gain knobs all the way down. You will see when you reach -18dB the others does not follow all the way to -18dB and when you do a reset they add the difference in +dB. If you do this with the Sliders/Faders - you will see that it works great.

Why doesn't the gain knobs move all the way down when set to different dB levels when you hold down Ctrl+Drag down - like how the volume sliders do when you want to reset the faders to zero with quick grouping? You often want to reset a few gain knobs with a quick CTRL+Dragging down and double click to reset them back to zero, but they never do with quick group. Instead they add the difference in +dB when you hold down Ctrl and do a double click. This shortcut works great with the volume sliders, but its as if it is broken with the gain knobs. Don't involve mix recall please. Leave her alone! ?

Nope. It keeps it well oiled.

City miles are creeping up on you then.

When bypassing an effect within the plugin, is there a way for CbB to display this? I know when you bypass any effect in the FX BIN - it turns grey. An idea would be as to what it does when you insert a MONO or STEREO plugin - it display one stripe for Mono and two for Stereo. So, the idea is to have a color scheme in the bin to let us know the plugin is bypassed from the plugin itself. This would be extremely useful when bypassing a plugin with automation when working in the console view. The idea came with a region that i had on looped, where the plugin was bypassed with automation, which I have done really early in the project and literally forgot about it. I'm pretty sure you can guess how confused I was for sometime - lol.

I actually do one every 4 months. Both windows and CbB. I completely format my OS drive. Its an old habbit.?

This is actually an install from scratch. ?

I always add my synths through the insert button +. I've never used the browser to add effects or synths.

Shouldn't it be selected by default? The reason why I am actually reporting it.

Cakewalk doesn't open the Vsti on insert. Brand new clean install of CbB and windows 10. The OS 10 was updated two days ago. UPDATE 1 of CbB build 034.

Nope. Know this one two. I've had problems with this one in the past. It doesn't always play all the tracks when pressing Shift+Space. I believe you have to repeat the steps every time you do a playback too? Not quite sure now. This is giving me an idea Can you choose mouse drag as a shortcut? ?

Just tested this and it has some limitations to my workflow. It work to some degree, but not fully as requested. This i'm well aware of. Now the request is based on this, but to let the highlight do the work for you instead of highlight and Shift+L. Another way would be to Hold down Ctrl+drag on the Timeline. Can mouse drag be assigned and be linked to another key as a shortcut? ?

Haven't made a feature request in a while - been working mostly in Logic these days. So my wish and request is as follow: The ability to draw in the "playback Loop points" within the timeline. I have searched and watched some vids on the tube and I believe most daws have this feature. It makes looping playback really easy.

In the past, yes - a few times. The issue always fixed itself with a reinstall for me though. Also: Its not the first time someone did a Q&A about it - others rant like crazy on it. Some said a reboot of CbB or their systems fixed it after an update has been done. There were even times when my audio drivers messed up after updating CbB where everything i play sound distorted - even youtube and old rendered songs. I will try and add some links in a minute.

Microsoft recognise it every time. Yet, I still have to manually reselect the USB midi keyboard little box in preferences when switching it on and off while Cakewalk is running. It's not an issue. I probably have gotten used to MacOS Big Sur doing things automatically - e.g. there's a lot of drivers Microsoft requires my gear to use - which MacOS don't require at all - not even for two interfaces I own, which is clearly stated on the manufactures website. So, I don't mean to make this an issue.

Sanchez 49 USB Keystation. No, it doesnt. Logic picks it up in an instant even PT first. I can easily switch it on and off while the DAW is fired up. I can swore Cakewalk used to do it - I might be incorrect too.

?? This is the problem I have, yes. For some reason I can't recall this ever happened to me before. Cakewalk always used to assigned after it has prompt for it. Now it doesn't and like you've said - a reboot of CbB is required.

I will keep this in mind when I fire CbB back on again when ever. Would be nice to have the baker let the DAW fix this automatically, or not! After firing CbB up after many-many moons, I immediately gave a sigh and though "BUG." and instantly discouraged.

This goes for Microsoft too. So . . . what's the answer to your observation John? ??

It's on a brand new installation of windows 10 and CbB. I'm not much stressed or worried about it. I'm not using CbB lately. I'm on Mac and a different DAW for "professional" work.

Yes. It unchecks the boxes when switching the Midi Keyboard on after CbB is fired up.