scook

Try using a different driver mode, such as one of the WASAPI modes if running Win10 or WDM for older OSes.

The DAW records the signal at its input. The gain and volume controls do not affect a signal coming from outside the DAW, they affect clips in the DAW. See the signal flow diagram

If Remove DC Offset During Recording is enabled, turn it off and try recording again.

That or change the MIDI editor indicator on the clip(s) to something other than the step sequencer I have no direct information about what is going on but I here is my guess. The step sequencer came well after CAL was deprecated. There is a conversion process for creating step sequencer clips from MIDI clips. Chances are the step sequencer data is stored in a different part of the project file that CAL does not know about.

http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Browser.10.html

The envelope context menu has options to clear all nodes and delete the envelope entirely.

Try SHIFT+clicking the envelope to bring it into focus. Once in focus, right-clicking on the envelope should bring up the envelope context menu.

Do not use the RealTek ASIO driver. It is known to be buggy.

Maybe something in this thread may help

This type of question usually benefits from supplying information about the audio interface, audio driver and OS.

Bundling is fine for stripping out unused audio clips from the project but not for long term storage. For long term storage projects should be saved either using a backup utility, copying the project to backup media or using "Save As" to the backup media. As mentioned above "Save As" copies only audio clips referenced in the project. Make sure "Copy All Audio with Project" is enabled in the "Save As" dialog. Another thing that may reduce the footprint of the audio folder is Apply Trimming in the Track View Clips menu. This destructively applies edits to selected clips. If one uses slip edit a lot this can be significant.

This may be but CbB has its own discovery process and if it stalls while communicating with an audio driver, the program hangs. From the information provided there is only one audio driver installed. The DAW is not connected to a purpose build audio interface with a manufacturer supplied ASIO driver. IOW, the DAW is using the internal sound chip and a Windows supplied driver. Could some other process be blocking driver access? It could also be AV related. It may be possible to generate a hang dump. Here is how to create one and report it.

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