scook

Until they elect to make the change...create the binding yourself in preferences The local binding overrides the global binding so if SHIFT+B is set to toggle Strips|Buses in the Console View area when the console view has focus nothing will happen in the track view.

Windows presents the driver as pairs of channels but the DAW can record each channel separately on mono tracks by using the left and right side. Use the "Left" for the odd number channels and "Even" for the even numbered channels of the interface IOW - Left 1-2 uses channel 1 of the interface Right 1-2 uses channel 2 of the interface Stereo 1-2 uses both channels of the interface with 1 on the left side and 2 on the right Left 3-4 uses channel 3 of the interface Right 3-4 uses channel 4 of the interface Stereo 3-4 uses both channels of the interface with 3 on the left side and 4 on the right ... Left 15 - 16 uses channel 15 of the interface Right 15 - 16 uses channel 16 of the interface Stereo 15 - 16 uses both channels of the interface with 15 on the left side and 16 on the right

Don't have Drawmer but do have TSAR-1 and Tube Delay. Both VST3 v2.4.96 plug-ins load and play OK in CbB 2020.04 build 179. When re-installing (or simply placing the dll and vst3 files outside of the scan path) scan after removing the plug-ins to clear the VST Inventory entries then after replacing the plug-ins make sure to enable the "Generate Scan Log" option and scan from preferences or run a VST Reset from preferences with the "Generate Scan Log Enabled" If the plug-ins still do not show up, review the scan log. Also make sure the "Rescan Failed Plug-ins" and "Rescan All Plug-ins" are not enabled in preferences (and the plug-in manager even though scan should not be run from the plug-in manager).

A very nice gift.

Thanks for the heads up. It has been a long time since I performed an initial or clean install and do not recall under what conditions activation happens. It may be BA needs to be running in the background for the initial run or CbB just fail to run it. Can't say for sure.

There is no need to run CbB from BA, Try running CbB directly from disk. The default location of the Cakewalk.exe is C:\Program Files\Cakewalk\Cakewalk Core If the DAW is configured to run as administrator, Windows requires that any program launching the DAW also run as administrator. The only time CbB needs to run as administrator is if some plug-in needs elevated privileges to write to protected areas of the disk or registry. To see if CbB has been set to run as administrator right-click on the Cakewalk.exe select Properties from the context menu open the Compatibility tab The "Run this program as an administrator" option is near the bottom of the window. If for some reason CbB must run as administrator, BA must be set the same way. Setting the "Run this program as an administrator" option for the BA shortcut is the same as setting it for the Cakewalk.exe.

Don't have Ctrlr. If the plug-in has it's own MIDI routing feature and is not using the regular "Enable MIDI Output" option built into CbB for VSTs, I would try using a virtual MIDI cable (LoopBe1) to send the data to a MIDI track and point the track to the MIDI interface. If that did not work, I would try connecting the virtual MIDI cable to MIDIOX.

reading a description of the plug-in, it looks like an audio effect so try the second set of instructions in this post

Yeah, I created a directory junction in place of "C:\Newfangled Audio" to point to the old presets location ("Newfangled Audio" in my documents folder) and made a copy of the presets folder in anticipation of the fix deleting the folder.

Maybe a workspace (lens in Platinum) is selected. If so, either create a custom workspace or set the workspace drop down to None.

I have Anthology XI so there may be some individual plug-ins in the collection that were not updated. All the plug-ins not in Anthology were updated except for SP2016 which was updated 2020-05-04. Installers available from https://www.eventideaudio.com/support/downloads The link also has Newfangled Audio updates from 2020-05-07

Hold down the SHIFT key while opening the project to load it in safe mode. Sometimes just running in safe mode is enough to open a project but, if it still locks up, safe mode can skip plug-ins which may be the issue.

may want to ask support@bandlab.com This forum is primarily for the PC-based Cakewalk by BandLab not the browser-based BandLab DAW.

@Scott Wheeler, Cakewalk uses the VST2.1 opcode effGetMidiKeyName to populate names in the Piano Roll View and Step Sequencer.

During install, Rapture Session/Pro copy the Cakewalk Sound Center, Dimension Pro and Rapture Classic programs into their program folders. It is a one time event so if one is in the habit of saving programs in the older synths, they do not automatically find their way into the Rapture Session/Pro program folder. To resync the program folders either manually copy them or rerun the Rapture Session/Pro installer. I suppose one could create directory junctions to eliminate the need to manually sync programs but I prefer to keep the original program folders separate. I did integrate the sample libraries though.

Often plug-in documentation will indicate the amount of latency added by the plug-in. If not plug-ins that add latency often make referenced to look ahead buffers. It is these buffers that must be accounted for when computing plug-in delay compensation. Some plug-ins such as IR reverbs add latency because of the computation time needed for its operation. Often these plug-ins have adjustments to change the amount of latency introduced by the plug-in. Finally there is a tool mentioned in the old forum http://forum.cakewalk.com/FindPost/3411418

Same here

While you are probably better off getting the OS updated to answer your question there is a rollback installer link in

Yes, forget about RealTek ASIO try the WASAPI (if running Win10), WDM and finally MME driver modes in that order. Some get acceptable results with ASIO4All. If you choose to go that route, make sure to uninstall the RealTek ASIO driver as no device should have more than one ASIO driver installed. When adding different audio devices keep in mind there is a restriction imposed by ASIO that only one I/O driver at a time may be used by the DAW. Things like USB headphones and microphones are separate devices each with their own driver. Driver modes other than ASIO do not impose this limitation. Also ASIO4All while it looks like an ASIO driver to the DAW is actually a wrapper for WDM drivers. Its control software has provisions for aggregating multiple drivers for different devices.

The Command Center program takes up around 100MB. It is the best way to install the last version of SONAR along with the other products with Command Center installers. Chances are these installers are the files taking up the GBs of space in C:\ProgramData\Cakewalk\Command Center\Downloads Backup or copy these files to a safe place and delete them from the system drive. Then restore them as needed on this machine or your next one to save time when (re)installing these products.

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

While installing on a non-system drive is allowed and there may be multiple versions installed; installing multiple versions on multiple drives is not allowed. The installers are suppose to prevent this but I have seen cases where a couple of versions were installed on different drives and it causes some strange problems.