brundlefly

Yes , I understand; no need to shout. Sjoens side-tracked the thread with mentions of Ref. Guide inaccuracy and using quick groupsing without selecting tracks so I took some time to address that as did you. My disagreement is with your use of 'SHOULD'. As menioned, regular Control Groups can work either way. Volume works the way you want Gain to work. But the way Gain works is not 'wrong' per se, it's just using the other convention. And to my mind it makes sense that Gains would maintain their levels relative to each other rather than relative to the arbitrary minimum of -18dB. If Gain went all the way to -INF like volume, it might make more sense for them to move relative to that point.

The thread I referenced was from September 2017. The last release of SONAR was 17.10, and I just confirmed it worked per the documentation - controls in all unselected tracks of the same type can be quick grouped by holding Ctrl when no tracks are selected. So it changed sometime after Bandlab picked it up. This was not a bug. It was intended behavior to make whole-project changes easy without having to select everything - like assigning all MIDI track outputs to the same mutlitimbral synth instance. But any time you have a function that can make a lot of changes with one simple gesture, you run the risk of users unintentionally messing up their projects, and this was one that they dcided to back out for that reason.

S#!+ happens . The team is tiny now; stuff is gonna get by once in a while. The Ref. Guide is highly reliable and useful in general.

If the sidechain input jack is configured as an INSERT (i.e. input/send signal between TS and output/return between RS of a TRS plug), then you might need to be using one side of a 'Y' Insert cable to take the mono output from your interface to the input side (TS) of the Insert jack. If you're using a mono cable with TS plugs at both ends or a stereo/balanced cable with TRS at both ends that might be the problem. Did that come up in your discussion with dbx?

Yes, but one of very few which suggests it's system-specific. In all my years I don't thinki I've ever had a custom binding spontaneously go missing. By any chance do you have 'Save changes for next session' unchecked?

Given how unusual a problem this is, I would guess something is going on with permisisons or antivirus on your system preventing the Windows registry from being modified or something. Nudge settings are also saved in the registry. Check if changes to Nudge values will persist. Also, maybe export your shortcut to a file and share it here to see if there might be some corruption that can be replicated on another machine. I have a 'test mule' installation on a laptop that I can freely experiment with.

To 'Select' a track means to left-click the track number to highlight it. Right-clicking a control and adding it to a group does is not technically 'Selecting' anything. Regarding what happens when you use Ctrl with no track selected. I do believe this behavior was deliberately eliminated and the documentation did not keep up. I'd have to search some old threads and release notes to find it. EDIT: Here's a thread from the old forum that discusses how dangerous it could be if you weren't aware of the feature. So it did work as documented at one time. This may have been the trigger for it going away: http://forum.cakewalk.com/Quick-Groups-Something-to-know-only-if-you-RTFM-m3651329.aspx

Meaning you want to have a track/bus in CW drive the siechain input of your compressor while it processes some other track/bus? I have not tried it but it should be pretty straightforward if you have the spare I/O channels availalable on your interface. Use an External Insert in the FX bin to apply the compressor to the relevant track/bus and route the sidechain signal to it via a Send on the other track/bus to another output. Are you encountering some specific issue?

Okay, I see that quick grouping uses what 'normal' grouping calls Absolute control for Gain - where the fixed offset between them is maintained- while 'Relative' control is used for Volume where everything moves proportionally relative to -INF. The different default behaviors may or may not be intentional - I can see justfications for both. But if you use regular/persistent control grouping, you can get the Relative behavior on Gains.

Unless I'm misunderstanding something, it's working here on both Gain knobs in the Inspector and Console and sliders in the track and with or without holding Ctrl to quick-group.

Replied to your original post:

Are you using Workspaces? Workspaces can have their own bindings but it's not enabled by default.

Where and why are you double-clicking? Single-clicking an FX bin's bypass button will bypass all the effects in the bin as intended and I found that the second click of a double-click is ignored, giving the same result. But I don't know of anything related to FX management that requires a double-click.

No, but I have long wished that it were! Possible to implement?

? I frequently double-check myself before posting.

See TransDetectorModel= in AUD.INI (Preferences > Audio > Configuration File > Edit Config File).

Actually sends are post-fader by default; you have to go out of your way to make them pre-fader. But, the OP was talking about fading the clip which is pre-everything; when the clip fade hits -Inf, nothing will be sent/output anywhere. But a long enough reverb tail would still be audible. I'm not sure why Kevin's screenshots aren't showing that. A reverb with a 20-sec decay time should definitely be audible as well as visible in the preview waveform at the high vertical zoom level in the screenshot. Here's Sonitus with a 20-second decay after a single metronome click with no zooming:

Hmmm... now I'm confused. LOL In my case, it's the 'adjust tool' techique that creates new nodes. Ctrl+drag moves the existing nodes, resulting in linear transitions to the previous and next nodes on either side of the segment rather than the jumps you're after. ?

If the goal is see the signal on CbB's Master bus as stated, Input Echo is necessary. If the goal is just to hear the input, then, yes, direct monitoring will do the trick.

The OP used the term 'send' but was really just having and issue with the track output. In all my years, I have almost never had a a problem with signal routing that didn't ultimately turn out to be my mistake and fixable without replacing anything.

Sync problems can have many causes - often user-error/misunderstanding as bdickens suggested. Start a new thread and share a copy of the clip/project.

Sticky-selected = track number is highighted. This is old terminology that may no longer appear in the Ref. Guide, but the functionality is unchanged for ages. EDIT: looks like I was mistaken that the time ruler selection wasn't happening in both cases. But it disapears on releasing the left-click after making the move if you don't have the track pre-selected so I hadn't initially noticed it happening while making the move. In any case, I can only reproduce a problem when selecting in the timeline as Mark described so its not clear to me that he's fixed your specific issue.

That's why Outrage Productions suggested, "Check the folder preferences for project templates, then look in that folder using file explorer for the actual <project>.cwt files." Correcting the path or restoring the template files to the specified path from a backup should fix it. I can't say I've ever seen an update cause a probem like this, but I have all my folder paths pointing to custom locations that are not touched by installs/updates. If I know of some new content being added that I want to use, I copy it over to my custom locations. But I just checked the default Content path, and the default template files are there as expected.

This is working as expected in the latest release for me. The time ruler selection only happens if the track is sticky-selected rather than just focused. But either way works as described in the parent track without having to open the automation lane. I don't know why it's not working in your original video clip. Can your reproduce it in a new, basic project?

Your screenshot shows the track is armed to record so the meter is showing a live input signal, but Input Echo is not engaged so that input is not being ouput to the Master bus. Rebooting alone would not have fixed that.