Will.

No. You're misunderstanding the report. Bring the END of the loop point in . . . not the start. All the way in - you will see where it stops and then jumps. That jump is the issue. It brings limitations to loop playback to tame transient or to pin point the perfect region when doing "comping."

But the loop dont snap for playback in tick or on anything smaller than in discussion.

but it doesn't go down to milliseconds - does it? Meaning: It doesn't go further/smaller than a 128th of a note. Thats my point. Zoom in to your grid until where the loop point cant go any further. Next change your grid to 1/8th - you will be on the same discussion then. That's the equivalent the loop points reach at its limit.

Two possible factors: Could be a Vst thats consuming a lot of CPU resource that are in your master chain. Maybe a tat bit too much oversampling of a plugin. If its an outboard hardware fader - thats definitely dust in between the groove of the fader. But . . . we do not have much to go on to help you, since you havent given enough information. System specs is a great way to start with - including what effects you are using. Are you in the box | or | on hardware? Laptop or Desktop, Touch screen or no touch screen. You get point . . . ?

Yes. Like i've said: I also dont use workspaces - never have, but apparently the default screen is a "Workspace" I was told once upon a time by one of the staff members and one "mysterious undercover" staff member. 😐

I have reported this before, and workaround are often a pain to isolate the region to be worked on. When making cuts on the specific area the loop points do not go further than an 1/8th snap note on the grid, This means: If you had make cuts in a 128th of a snap - you're by yourself. Even with the snap off this does not work, nor does it by holding down Ctrl, Shift or in a combination of these keys. The reason is to get a surgical and precise region on the playback to tame some transients and to do precise comping | or | to add some dynamics to it. I can do cuts in samples/ticks and all that, but to get that precise area to work on, is a guessing game with the playback loop points not going smaller than an 1/8th snap note in the measure/bar.

Also to point it out, Ctrl+R in Track view is the default shortcut to Arm a track for Record in both CbB (and to record in windows 10 with the built-in voice recorder from microsoft) - hence to why the user is saying this . . . .

Leave these millennial morse codes alone. 🤣 😂 Who ever said caps lock are a way of shouting was drunk and probably high on drugs too. 🤣 I apologise if you feel I was. The use of an exclamation (!) mark would have told you I was shouting, but I did not use any. I'm not shouting. I was merely emphasizing the topic in discussion and even stressed it out in bold caps as a way of expression.

I think you're misunderstanding the whole thread discussion. Like I've said above. The values of the GAIN KNOBS WHEN MOVING WITH QUICK GROUP DOES NOT FOLLOW THE COMMANDS AS IT SHOULD IN dB IN CONJUCTION WITH THE OTHER TRACKS. QUICK GROUP WORKS AS IT IS SUPPOSE TO. NO ONE IS QUESTIONING THAT, BUT ITS COMMANDS AND VALUES WITHIN THE PROCESS.

Check to see that your antivirus software does not see your focurite drivers as a potential virus thread.

I too said so, but apparently, the default window is a "Workspace" I've been told. 😂 I'm trying to remember. 😂

This sounded like a bug. Quick Group should work only for the selected tracks that are highlighted and in FOCUS. Thats the whole point of it. None of my other two DAWs works as described in the old forum OR the way CbB handles it now. Dont know how they can tell other tracks are not in focus OR when L&R pan knobs are moved down to counter rotate the percentage in the stereo fields. So i believe this part of CbB has been left untouched and broken including the gain knobs.

I have had this issue in the past and spend hours with the bakers trying to fix this in the PM section. I've manage to fix it myself, but i'm trying to remember now how - to you help here. 😑 It's literally just a setting. 😐 Check if your "Apply workspace to project" is ticked, right at the bottom of teh workspace dropdown menu. I'm trying to think now. 😣 In Preferences > keyboard shortcut TAB -- make sure "Save Changes For Next Project/Session" is ticked.

Try disabling what ever antivirus software you're using. It could be mistakenly holding it as a "Potential Unwanted Thread" in its quarantine bin.

You can switch them off.

So you select them, right? 😂 You SELECT the tracks you want to "GROUP" (the keyword) not so?

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.