scook

The CA-2A is an upgrade to the PC-2A. It may automatically replace the PC-2A if the the old PC-2A is completely removed from the scan path. The default PC-2A folder is C:\Program Files\Cakewalk\Shared Utilities\Internal\PC2ALevelingAmplifier

Bypassing plug-ins can be done globally (keyboard shortcut "E") and at the track FX rack levels.

That sounds more like unauthorized plug-in

should be getting a dropout code http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.32.html

Just ran the installer to confirm

I believe it should be on the advanced install component pick list as one of the plug-ins.

IIRC, Bitflipper made a tool to report VST plug-ins from the VST Inventory in the registry. The only tool I know of for reporting project contents is ProjectScope. A link to the program is in this thread

IDK, never wanted to separate a project file from the audio folder below it. This is the default per-project audio folder layout and it is this way for a reason. Keeping the default per-project audio folder layout where the project's folder contains project's file(s), autosave and versions Audio folder containing project's audio Melodyne folder containing project's melodyne audio clips MixScenes folder for the project's mix scenes insures the project is complete and portable. The folders are stored in the project using relative paths. Placing folders outside of the default path breaks portability because the the folder locations are stored as absolute paths.

Great The ASIO driver for internal sound chips has never worked well

Yeah, Clint was a pretty active promoter. Here is where he found out about the plug-in.

For those who do not venture to the other parts of this forum The sale is for the X-Valvecomp. IIRC it is not really modeled after any particular SSL channel compressor. SSL no longer require a dongle for their plug-ins. They support iLok machine locking too.

Similar to the original discussion about tkdelay

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.