OutrageProductions

Yes, according to the inference from the Bakers, although the actual term limit is yet to be determined. Best guess is 6 months from release of the new retail Sonar...

When you are playing back the recorded click, have you removed (turned off) the IRT click metronome? They would only need a couple of samples difference in latency to cause phasing/amplitude issues.

Just remember that Sample Rate relates to frequency response and Bit Depth relates to dynamic range. Which one matters the most to you? Most professionals and streaming/distribution services start from and derive their content from 48k/24b, so that is now the defacto standard. CD quality at 44.1k/16b is now passe.

This can be an issue with USB bus-powered devices if they don't get enough juice. Have you tried using a full power port or a USB power hub?

How do you have them arranged in Win settings <display>?... side by side OR top/bottom? That will determine the boundaries of the virtual desktop, regardless of resolution.

I would recommend avoiding wireless/BT devices in the playback chain... too many points of failure, unacceptable latency, and generally mediocre quality, IMHO.

Your best option may be to remove the offending plugin and find an alternative workaround. In case you have not been frequently reading this forum, the latest and final version of CbB is currently 2023.09 build 75. Very shortly everything prior to 2023.09 build 64 will not be able to authorize. And eventually CbB as we know it will be End Of Life and time out. The heir apparent will be a paid version named Sonar.

As someone who has mostly used Ultimate Ears $900 IEM's among lesser units, I highly recommend these.

@David Baay thanks for the info. That is definitely not detailed in the documentation. I always use the wheel on my control surfaces anyway, which can do measures, beats, or rolling scrub.

Try this experiment: Bounce (NOT freeze) the audio from that track out to another audio track, preferably IRT, then Archive the offending track/VST and test again. OR Disable the FX in the bin, then freeze it. Re-enable the FX after the audio is rendered.

The installed library is 732 MB.

Workspaces will save the status of the HW bus layout including narrow/wide, mute, link, and levels. I do it all the time, as I switch between nearfields, headphones, far fields, and surround systems just by changing the Master bus output to HW, and toggling the HW mutes. I have my Workspaces set to put the PRV on one monitor, Console on another, Video/Big Time on a third, in addition to TrackView/Main on a fourth. It's been this way for ages. Try it.

I was of the understanding that you are trying to trigger MIDI samples to match the existing audio track drum, so yes, Remove Silence only works on the audio track. Then you can tab from transient to transient and slide/nudge the midi note to match the implulse response of the target drum audio. If this is an incorrect interpolation, then just ignore my advice.

The 'Remove Silence' is as close to an auto split that is available. A lot of people think that making music is easy, but if you want to do it really well... it's not.

Just a thought here, but have you tried to copy the audio track and then apply the 'Remove Silence' function? By super tweaking those settings, and then tabbing through the result (which goes to next event/transient), you should be able to zoom and inspect the alignment of the MIDI trigger with the impulse of the real drum. I often have to do 'forensic' audio for clients and have found that function to be of great assistance. But it requires a lot of time, none-the-less.

As you mentioned, the intro is really a cacophony. Try to mute some things out and feed them in later in time as they become more in the pocket, before the vocals come in. Sorry to sound harsh, but this could be done better. You've got it in you...

The only options (of which you are familiar) are the Jump/LInear/Fast Curve/Slow Curve), so the short answer is NO. Ya gets what ya gets.

I concur with @David Baay on the functionality in my current build/version. AFAIK there is NO LATCH available for the 'scrub tool' as it does not appear in the tools HUD. The only way that I can invoke it is by holding the 'J' key on the QUERTY while scrubbing directly over notes in PRV, or directly over an audio track in the TV. If you have a mouse button that triggers/latches the scrub tool, that is where I would look for a modification. I cannot make it crash/hang here. It does nothing in the TV when on a MIDI track, IME.

Editing at the micro level is pretty much 'note by note', but I'd second @David Baay's concept of trying the CW DrumReplacer. Also... learn to have patience, grasshopper. ?

The CW mini-dump files are usually located in C:\Users\username\AppData\Roaming\Cakewalk\Cakewalk Core\MiniDumps. Windows has a built in reader application. Use the taskbar search for "WinDBG". Here is a starting instruction for how to use it. Most of the output is verbose, but it is NOT for the faint hearted. After running the analysis section, there should be mention of which plugin (if any) had a memory fault. Remove that plugin and save the project. Then find a workaround for the faulty plug. I've found that Breverb, and some of the CW[LP/PX/TL/TS/VS-64] (channel strip, multiband compressor, et al) can be culprits for some odd reason, and it sometimes is interactive with other loaded VST/VST3 plugs (as was my issue with Scaler yesterday... it didn't want to play nicely with NI Noire). I don't expect any of these anomalies to ever get solved in CbB, but I've been using workarounds for so much stuff over the last 40 years that it doesn't even bother me anymore. I make a healthy living in music, so as they say... "The show must go on". I also have a tendency to hit CTRL-S after nearly every edit. BTW; very cool profile pic... looks like a Selmer saxaphone.

You likely have a plugin instance in the project that probably has a checksum error and won't release memory. Try loading the project in safe mode, bypassing the plugins by a process of elimination. To invoke safe mode, hold down the SHIFT key while opening the project. You could also initiate a mini-dump at the hang (before ending the process in Task Manager) and examine it post-facto for an indication of which plug is at fault. I had a session fault four times yesterday when freezing tracks in a 62 track scoring project. Using & examining the dump file pinned it to SCALER 2. Removed that plug, problem disappeared. Info on how to do all this is covered in detail in this forum by Noel & others.

The Teensyduino ADC board inside these things have very stable buffers (from V3.4 onwards) and when programmed for MIDI output Continuous Controller values will only 'sit' on the last input; ie: if the linear signal changes from step 64 (+/-<0.5) to 65 (+/-<0.5), it will put out a change in the digital data stream; if the input device (analog voltage) stays between the interpretation of 63.5 and 64.5, the output will stay at 64(for example). But it does not continuously 'stream' data 64 after that. They can also be programmed for an analog (ie: audio taper) response, but that requires a different script than what is installed in the Sparrow series (afaik). I've only reverse engineered one of the units so far.

But use a custom non-default template name, because otherwise they may be overwritten in future. [Like there will be anymore updates... LOL ?]

I don't own one of those, but have used the 3 fader version in another production room and was quite satisfied with performance. It was assigned to CC#3, CC#14, & CC#11. #3 (breath) & #11 (expression) are present in most orchestral VST'S, and #14 is usually freely assignable, so that worked for me. Well worth the money, altho they only contain about $35 in materials and can be easily made by anyone with a modicum of soldering skills. Programming is done via web portal, and cannot be changed on the fly, but otherwise OK.

<Preferences><Customization><Editing><Clips> auto-crossfade from 0 - 25ms. Anything longer than that will likely become audible for most humans as a glitch.