scook

If the task manager in the OP image is from a freshly started OS and CbB launch then the problem could be during the audio interface driver discovery.

It is well below the recommended minimum https://help.cakewalk.com/hc/en-us/articles/360021857753-What-are-the-minimum-requirements-for-using-Cakewalk-by-BandLab- The program should run but may be limited to very simple projects.

Maybe some info about the audio interface would help. Also if the programs runs properly but does not run again after being shutdown, it may not have shut down completely. The program can get hung in memory waiting on the audio interface or Bitbridge (if using 32bit plug-ins). To see if the program is still running check the Windows task manager.

Keyboard shortcut "J" toggles MIDI scrubbing in the PRV and Staff View

The PC-2A installer should be in your old Cakewalk account, if you created a single sign-on account from Dec 2014 through Nov 2017.

In the PRV View menu enable "Show/Hide Track Pane" The track pane controls which tracks are displayed in the PRV. For more info see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=EditingMIDI.10.html

If anything works using the Scarlett headphone out then the problem is not the hardware. The problem with audio from CbB to the Scarlett is either a CbB config or project routing issue. What ever settings were used on the Scarlett to play any Windows app should be the same to play audio from CbB. Try all of the driver modes in CbB and set Scarlett as the output device. There are step-by-step instructions for ASIO using SONAR Platinum. The CbB setup is identical. The instructions are here A master bus is a good idea but not necessary when performing a simple playback test such as playing an audio clip on a track. The track may be routed directly to the hardware. Although, once past the basic hurtle of getting sound out of CbB, a proper project layout using a master bus is a good next step. Set #1 in this image to All. Any other setting hides information such as the volume, gain and pan controls.

A good place to start is support@cakewalk.com The error message makes no sense if CbB was installed taking all defaults and no versions of SONAR were install before or after CbB. If the plug-ins are in the default locations then HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Cakewalk VST X64\VSTInternalPath in the registry should be set to C:\Program Files\Cakewalk\Shared Utilities\Internal This path should contain PCS-GlossEQM.dll among others. The default scan path in preferences is shown in the image from the link If defaults were taken during install consider restoring the default scan path, enable "Generate Scan Log" then click the "Reset..." button. This will rebuild the VST Inventory in the registry using the scan path entries in preferences and the VSTInternalPath from the registry. If this runs successfully, verify the PC modules load and add back any custom scan path entries then run a Scan. The scan logs may help with any problems encountered during Reset and Scan operations.

Try setting the Windows sound to the Scarlet and see if ANY Windows program can play sound through the interface.

By default the 64bit GlossEQ bundled with CbB is installed in C:\Program Files\Cakewalk\Shared Utilities\Internal It seems very odd that the error message shows a 32bit path. I have never seen 64bit SONAR or CbB use a 32bit path for anything. Even the 32bit plug-ins bundled with SONAR were installed in "Program Files" and not "Program Files (x86)" unless the 32bit version of SONAR was installed first. Even then, the 64bit PC modules always went in "Program Files". I am not sure the update contains GlossEQ. Even if it did, it would use the 64bit folder.

Use this menu to call up the Add-ons installer page

While waiting for a change to clip gain automation try adding a gain plug-in to the clip FX rack. Although not addressing "partial" clip issues, it may offer greater gain range and more options than the regular clip gain. The free Blue Cat Bundle includes three gain plug-ins: dual mono, and stereo. Mono and stereo have a knob w/ +- 60dB. Duel has individual knobs for left and right (or mid/side) -+ 60fB. The plug-ins may be grouped (up to 9 groups allowed). Drag and drop the plug-in on the clip and automate as needed.

The current version of CbB is 26.05.0.39 This post covers how to generate a "hang dump" to send to support

As mentioned above the may be placed any where. Historically bundled audio samples not associated with a particular synth were stored in folders under C:\Cakewalk Content\Audio Library Regardless of where the folder is on the PC, the location may be added to the Content Location menu "C" for quick access by navigating to the folder and clicking "L" For more about the media browser see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.03.html

Feature requests go here That said, clip gain already exists. They are displayed by changing a tracks edit filter ("A" in the image below) to Clip Automation > Gain

The plug-ins failed to scan correctly, click the "Reset..." button in VST Preferences to force a rescan.

It is not possible to redraw a waveform by hand in CbB. It is possible to integrate any program including free and commercial audio editors into CbB and send data between the program and CbB as long as the program accepts a wave file as a command line argument. I created a free program to make the process of adding programs to the CbB Utility menu a little easier. It is called Tools Editor and is available on my Google page along with other CbB related software.

This Most Recently Used list is limited to 5 plug-ins. If you have a known collection of favorite/most used plug-ins consider creating a category at the top of the "Sort by Categories" layout or your custom layout for them.

Yeah, not much fun

It was always sold separately. The installer should be in your account. The same is true for the Concrete limiter, PC4K expander gate and CA-2A PC modules.

I don't doubt it. I only mention input echo as it is often a cause for confusion in new users when trying to play an instrument and hearing nothing. The round trip latency often needs to be experienced to appreciate direct monitoring.

My guess is the OP was trying to monitor through the DAW. Direct is a good way but it helps to know that input echo (the button to the right of the record button) must be enabled with monitoring through the DAW.

Most of the synths I use do not require an extra step in the plug-in to send MIDI data. It would be nice if all synth did require configuration. It would help avoid the problem I mentioned above.