Promidi

I noticed that too.... and could not resist the particular price they were asking for MMixingFXBundle

There is. I have MTurboCompLE and an upgrade to MTurboComp FULL is listed as one of the upgrade options.

Can you give us a bit more information about your set set up..

Is this with “Fast Bounce” on or off? (try both)

Some more info about your system and configuration would be handy.....

My money is on a plugin doing this

Don't forget to check your spam folder......

That all looks fine there. Very similar to mine. I am currently doing a project with AD2 and I am not having the issues you're describing. Definitely update the Focusrite drivers.... even if it doesn't solve the issue, it always good to have the latest. Just to rule out a hardware issue, have a look at the Windows system event viewer for any hardware issues that stick out... especially hard disk errors (like bad blocks). It wouldn't do any harm using a utility to check the disk's SMART info.... I use CrystalDiskinfo for this.

I have to admit to having no clue what could be causing this. Renaming your AUD.INI certainly wouldn’t do any harm. Also, have your checked that the driver for your audio interface is the latest (using manufacturer's websites rather than Windows updates)? Maybe a Windows updated borked the driver. Is your Windows fully patched? Using the latest AD2 (Which is 2.1.14 build 201201)? Can you tell us a bit about your audio subsystem (the card used, driver mode, sample rate, bit depth, audio buffer size)

If you really need notation, then you might be better of with an application that has that as it's main task. The reason I prefer the PRV is because it allows for imperfections to be visually represented and edited to the tick.

Is it possible that Adobe Audition installed it's own ASIO driver (like Magix installs its “MAGIX Low Latency Driver”)? If so then remove that and see if it makes a difference.

And besides, notation is too strict and confined compared to the flexibility afforded to by the PRV

Have you made sure that the plugin's *.DLL (if they are VST2) or *.VST3 (if they are VST3) files are in folders as defined in Preferences | VST settings | VST Scan path? If so, then you might want to perform a reset and scan from that same preferences screen.

Remember, some plugins require X3 to be present to work in Cakewalk by Bandlab.

The installer needs a dark mode..... very bright in a low light studio..... almost burned my retinas out...

That's where I would be looking. Not just the application logs but also the system logs. Also, there may disk errors that would show there as well (like bad blocks)

If you do need serials resetting, I am pretty sure PACE will tell you to contact the company in question to get this done (AIR and SONIVOX in your case)

What happens if you rename your AUD.INI file and then try to start Cakewalk? This is found in the following location: %appdata%\Cakewalk\Cakewalk Core

Some plugins already use GPU acceleration for their display. Meldaproduction employs the GPU for some of their plugin's display outputs.

More info needed....

I submitted my email address twice, didn't receive it.... (yes, checked spam folder)

No. You must use Bandlab Assistant. Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Maybe drop a note Cakewalk support here: https://help.cakewalk.com/hc/en-us/requests/new?ticket_form_id=360000025633

Have you turned off USB power management in Windows Device manager (Start + Run devmgmt.msc) under Universal Serial Bus controllers - anything with Root hub under "power Management" Also try Start + run "control powercfg.cpl,,1" and set USB Setting | USB selective suspend setting to disabled I'm also assuming you have downloaded the latest drivers for the UR44C ( using manufacturer's websites rather than Windows updates)

Does the MIDI foot controller show up in Preferences | MIDI | Devices under inputs. If so is it selected? That's the first thing you need to do Then for the plugin you wish to control using the MIDI foot controller, Check the “enable MIDI input” on the VST menu on the plugin window menu. Once that is sorted then you need to create a MIDI track with its input set to the MIDI foot controller (Press I to bring up the inspector > under “in/out” down the bottom). Near that same area, the output of that MIDI track needs to be set to whatever your plugin is you want to control. Your plugin should appear on the drop-down, along with any other MIDI devices you have. It will only appear if you have checked the “enable MIDI input” on the VST menu on the plugin window menu.