Will.

Thank you. Appreciate taking time in considering this. Cant you just remove the limitation on the snap from the end of the looping marker, because the start of the loop marker works in milliseconds. Most DAWs i'm familiar with works this way. Cant it just mirror the beginning? Asking.

Yes, I too have to rely on workarounds as well by using third party samplers, but why should that be, if the only thing preventing this from being done in the DAW - is the snap of the loop playback? It can at least snap to ticks.

EXAMPLE: Let's pretend this was an actual problem in the sample. Here I have a Closed hat. I only want to listen to the slightly darker (also known as the dynamic region) highlighted area, but I cant. The loop points/markers end - stucks at a 1/8th of a note. So, listening for headroom when doing comping on the attack without the use of a compressor is currently impossible. The size of this sample is a 1/16th of a note in the measure.

Noel how are we suppose to locate and hear the playback in a rapid loop to tame or add to a comping section if it doesn't go smaller than a 1/8th of a note? You cant hear the actual "perfect" headroom in the comping with this limitations on the loop points/markers? This is especially true on letters suck as S,T,K,B,P or the spike on a Snare. Advance editing is where we do vocal comping on these problem issues before I add any process effects. You get artists that do not want their vocals to go through any pitch correction vsts - so we have to rely on comping to keep the vocals natural tone and pitch in letters, and words. The less workarounds you use the more you retain that natural elements of the data. To argue this is actually disappointing, seeing it is extremely crucial edits.

It's a shame. So that means you're going to limit and prevent us from doing surgical comping edits? got it . . . perfect! I don't believe anyone render these small samples, but what we do in fact do is - we use the loop point markers to surgically locate the precise area to do a cut.

Hopefully, it will get fixed for the next release.

The midi/clip data you want to bounce always needs to be highlighted in order for it to always align up.

Have any of you tried to delete your current "saved" kbn file - not the Sonar key assignments.kbn file. Copy your current ssved keybinding file and paste it in a safe location and delete the original. Close CbB and create a clean template. Re-assign a few shortcuts, hit apply, okay and relaunch Cakewalk. Confirm if that worked.

Correct. Would appreciate it if we can finally fix this. I did report it here many versions ago - more than twice, but never gotten a positive response.

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?