scook

32bit VST plug-ins run just as well in 64bit DAWs on Win10 as they do on Win7. The plug-ins do not run directly in the DAW. Instead they rely on bridge software to host the plug-ins and communicate with the DAW. 32bit DX plug-ins do not run in 64bit DAWs. There is no comparable bridge for DX plug-ins. That said, some 32bit DX plug-ins will work by using a VST wrapper making them appear as 32bit VST plug-ins to bridge software. This is a very fragile solution.

Try the different driver modes in preferences. Make sure to set Cakewalk to 48kHz sample rate. According to this pdf, the device is fixed at 48kHz 24bit.

Yeah, if the project is old enough, it will not have the QCEQ loaded and does show Gloss EQ (aka Quad Curve EQ) in the PC menu. I have not opened a file that old in years. If this is the case here, the install is OK. AFAIK, once added the QCEQ cannot be removed by DAWs that support the ProChannel. The QCEQ is treated a little differently from the PC modules.

That is a messed up installation. Gloss EQ is the name of the Quad Curve EQ dll (the actual name is PCS-GlossEQM.dll). The QCEQ should appear in the ProChannel of all tracks and buses. It should not appear in the PC module menu.

The per-track EQ feature pre-dates the ProChannel. It was added in SONAR 4. The Quad Curve EQ is an update to the original per-track EQ hosted in the ProChannel. The QCEQ cannot be removed.

Above 24bit this is floating point too.

That is right and it is easy to verify by checking the recorded clips. Unless one is processing the recording audio stream on the fly in the DAW, I doubt there is any advantage to recording higher than the audio driver bit depth.

Record and render bit depth support up to 64bit. The audio engine is 32 or 64bit based on 64-bit Double Precision Engine setting. It has been this way for a very long time (2005).

goes by @Steve Patrick

It is hard to guess what is going on with interpreted error message. It may help to post an image of the error message. Without it, my best guess is something is interfering with file creation such as anti-virus software. I recall an anti-malware program called ByteFence causing problems with file creation. If this is installed, removed it.

Yes, and there have been cases reported where devices that are supposed to automatically change sample rate fail to do so resulting in the audio recorded at the interface sample rate and audio clip headers reporting the DAW sample rate. To avoid surprises, when changing sample rate, it may be a good idea to verify the project and the interface are running the sample sample rate. If the audio interface is also used for Windows, this gets a little more complicated as Windows and the DAW should always be set to the same sample rate too.

To set the sample rate for new projects (and project without audio) or change the sample rate of a project with audio see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.05.html

The area is not part of the plug-in layout. It is a recently used list maintained separately in the registry - HKEY_CURRENT_USER\SOFTWARE\Cakewalk Music Software\Cakewalk\Core\Recently Used Synths Delete the duplicates using regedit if you wish. They should naturally retire when other synths are used.

The icons to the left of the names in the most recently used area are all VST2. Not sure how one doubles up entries in the MRU list like the image shows. I tried but could not replicate it.

similar thread

One solution is use aux tracks as buses. Make sure the sends feeding the sidechain inputs on the FX in aux track are pre-fader.

FWIW... WASAPI Shared uses a buffer set by the OS and cannot be changed by CbB. All other driver modes have an adjustable buffer but some manufacturers do not support changing ASIO buffer size from the DAW. For these interfaces, the buffer must be adjusted with software supplied by the manufacturer.

Hold down the SHIFT key for fine control

Enable the Keystroke button on the right above the plug-in UI.

Another possibility is the playback software is "enhancing" the signal. To see if the exported audio sounds like the original Cakewalk project, import the audio into a new project and play it. If it sounds like the original project, the problem is the playback software setup. If it sounds different than the original project, it may be a routing or export issue.

The Pantheon plug-in bundled with SONAR Producer was DX format. It is registered when installed and does not get scanned by the VST scanner. A VST reset will not help. Looking in the "Sort by" layouts provided by CbB is good idea.

These are included in CbB too, see http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Plug-ins.1.html and http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Plug-ins.2.html#1765955 TH-U on the other hand is not bundled with CbB. It is not free.

I found a related thread with a little more info

I do not use Kontakt but my guess is the Zero Controllers When Play Stops setting is the issue.