scook

Yes, move the slider to the left (Fast) if the machine and interface can tolerate a smaller buffer.

Take lane setup is per-project. The settings are in Preferences > Project > Record Create a custom project template to use new per-project preference settings in future projects.

Does not look like v1.7.0 which is VST3 only. The menu should look like this Maybe you have loaded an old VST2. Regardless "About Surge" should tell you which version is running.

The menu in the bottom right of the UI

Selection duration is displayed in the large Export Module.

It is your machine. Configure it as you see fit. The plug-in is not part of Cakewalk.

That looks like a SynthEdit error. The faster you can replace 32bit SynthEdit plug-ins the better. This is probably a permissions problem. Either run Cakewalk as administrator and/or move the plug-ins to a place that does not require administrator privileges to write to disk. Some SynthEdit plug-ins just need to run as administrator one time to write out all the modules to disk. Others constantly write to disk.

Glad it worked for you. You may want to add back at least C:\Program Files\Common Files\VST3 to the scan path in preferences. This is the recommended 64bit VST3 path and many installers do no deviate from the VST3 specification. VST2 plug-ins may be installed anywhere EXCEPT in C:\Program Files\Common Files\VST3

Looks like the documentation is a little old. SONAR 8 was released in 2008.

The 64bit path that corresponds to the path in the scan path is c:\program files\access music but as mentioned above the 64bit software could be installed in the x86 folder Usually installers provide information about where they will install files. Maybe uninstall and re-install carefully paying attention to the install screens.

Search for the 64bit plug-in (if there is one) on the PC Contact Virus support Wait for someone who has the same gear to reply on this forum Find another forum for Virus users

That scan path entry typically is used for 32bit software but 64bit software could be installed there too.

Plug-in lists in the DAW not the plug-in manager. There is no indication in the plug-in manager other than possibly the path. Click on the plug-in in the plug-in manager to see the path.

The clue is the standard VST header is not above the plug-in, instead it has a BitBridge header. 32bit plug-ins have (32-bit) appended to their name in the plug-in lists. The plug-in manager will show the path to the 32bit plug-in in the file name entry at the bottom of the plug-in manager window.

The pictures shows a 32bit plug-in. The Virus site has a 64bit installer.May want to try the 64bit version.

There are two things users can change that contribute to the delay from pressing a key on the controller and hearing the result. audio driver buffer size plug-in delay compensation A 256 sample buffer size is at the upper limit for real time monitoring through the DAW. To see if plug-ins are contributing to the delay click the FX button in the Mix Module to bypass all effects. While reading these sections in the help take a look at the PDC button too. To avoid PDC do not use plug-ins that need a look ahead buffer while tracking. Generally these plug-ins are intended for mastering and include dynamics processors, linear phase EQs and impulse response reverbs. Another way to work around large amounts of PDC is temporarily bounce all the tracks, archive everything except the temporary track and the track being recorded.

If you are using the Saffire, then the audio connections need to be made to the back of the Saffire and not the PC.

Writing the most recently used list is one of the last things CbB does before shutting down. If the program crashes the list does not get updated.

The VST Inventory tool gets its data from the CbB VST Inventory in the registry. This inventory is built by the CbB VST scanner. There is no attempt by the VST Inventory Tool to validate the data, that is the scanner's job. The SurgeEffectsBank VST3 in the image shows a pretty old version number and my guess is the file is not part of the current distribution. For a nightly build, it seems strange the version reported on the Surge VST2/3 plug-ins is older than the current production release. Also note Surge VST3 lacks a size. On my install the production version shows a size for this plug-ins. I thought the SurgeEffectsBank was provided for DAWs not supporting Surge as an FX. While the documentation claims Surge does not work as an effect in CbB, I have been able to use it in that capacity for some time. I tried asking the developer what did not work but never got a reply. My guess is this part of the documentation needs an update. Of course, this does nothing for those who depend on the SurgeEffectsBank plug-in but now may be a good time to stop using the dedicated effects plug-ins and use Surge instead.

no feature request go in https://discuss.cakewalk.com/index.php?/forum/8-feedback-loop/

These instructions are for SONAR Platinum. The setup is identical in CbB. https://www.cakewalk.com/Support/Knowledge-Base/Audio-Hardware-Setup-Guide?productId=CSPT100&audioDeviceId=248

Yeah, sticking with VST2 when a working VST3 version is available is asking for future pain. Not all manufacturers add the VST2 to VST3 migration code to their VST2 plug-ins.

no

Often when audio cuts out periodically it is the result of a plug-in running in demo mode.

This is probably because Windows and Cakewalk are sharing the same audio interface and Windows and Cakewalk are set to different sample rates Cakewalk is set to WASAPI Exclusive driver mode