scook

Applying the rollback before installing the next update also causes BA to download the full installer. To get the current release, apply the last two rollback installers. As noted above, even without running CbB to interrupt the installer there is enough time during a full install to grab a copy of installer before it is deleted. I used to do it this way.

This is correct. You can if you want to. Doing so causes BA to present the install option as if it is a first time install.

Another way to get a clean FX Chain folder is uninstall CbB and re-install. It is nice to have a list for others who started with CbB prior to 2020.08,

https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.38.html

Sure you can. Keep in mind how updates work: If the machine is current, BandLab Assistant downloads and applies an update installer. This is not the full version of CbB. It is very much like the next release's rollback installer. If the machine is not current or an initial install, BandLab Assistant downloads the full ~500MB installer. BandLab Assistant deletes the installer after it is run. It is possible to make a copy of the installer after the download is complete and before the install is complete. Running CbB after initiating the download causes BA to issue a message advising the program is running and must be shutdown to continue. This message is displayed after the download is complete. Take as much time as you want to copy the installer, then shutdown CbB and let the update continue. BA uses %appdata%\bandlab-assistant\Downloads for its temporary installer storage.

When recording on one channel make sure to set the input of the track to the appropriate channel and set the stereo/mono button (a.k.a. track interleave) to mono. Please do not post the same question in multiple places. It will not result in a faster answer. It just makes work for some one else. Thanks.

rollback installers are in the release announcement like this one

Yeah, right on the home page

Looks like the Track View is zoomed way in on the timeline.

Looks like the duplicate track button needs a little work

All I can suggest is review how everything is connected before and after the PC. Feedback is not possible in the DAW without something outside the DAW connecting an output to an input. If audio effects are getting recorded the effects must be in the signal coming from the interface to the DAW.

Well you have one...BandLab. It is the only one I have too but I have not used it much.

Making good progress. I hope you found the modified filter on the Views tab in the theme editor. It helps when looking for changes. Themes are a collection of differences from Mercury, the "theme" in the program resource files. Looking at the mods in Tungsten gives you an idea of what needs to change when creating a dark theme.

It;s all down to signal flow. If the delay is getting recorded and is not getting in the monitors, the signal being monitored is before the delay.

The instructions are in the link above. On the Apps tab in BandLab Assistant, the second item is the installer for Cakewalk by BandLab. Click the install button and BA will download and run the ~500MB installer and active CbB.

Do not confuse BandLab the web-based DAW with Cakewalk by BandLab the DAW build from SONAR Platinum sources. Cakewalk by BandLab and the SONAR X series use the same skylight interface. One big difference is, after X3, the DAW supports themes. The X3 style theme is still there. It is called Mercury and looks a lot like X3 to me Cakewalk by BandLab installs as an upgrade to SONAR. Both DAWs have their own directory, the shared files are updated and backward compatible. All of the content installed with 64bit X3 is usable in CbB. Installation instructions are here The process starts by installing BandLab Assitant.

Really should consider upgrading to Cakewalk by BandLab. X3 is getting a little old (almost 7 years) and it makes no sense to update everything except the software you want to use. Did you install the ASIO driver? The Hotone web page says the device does not require a special driver if running a certain level of Win10 but it may be needed for software released before Win10 such as X3.

I do not use Waves plug-ins but have read enough Waves install threads to know contacting Waves support is the best solution for install problems with their plug-ins. Waves was one of the first manufacturers to support automatic VST2 to VST3 migration. Make sure the VST# migration options are enabled in preferences. Pretty sure the restriction on mixing Waves VST2 and VST3 plug-ins is still in effect. Starting with version 9.6 Waves supports VST3 only in SONAR/CbB.

If you need help figuring out where the audio overlaps and relative track levels a tool like Melda Production's MMultiAnalyzer can help. Like all Melda plug-ins it goes on sale for 50% off at some time through the year.

Glad it worked. Had you mentioned which version of CbB was running before the update it may have triggered my memory about the change but I doubt it. There were discussions about this issue with Toontrack sprinkled throughout the 2020.01 Feedback thread starting with this post.

May want to update the OP and subject since v1.7.1 is out The SurgeEffectsBank now scans OK in CbB

This is the problem. VST2 plug-ins cannot be installed in the VST3 folder. Starting with 2020.01 Cakewalk no longer scans files with a dll extension in C:\Program Files\Common Files\VST3 Moving the Toontrack folder to a different location outside of the dedicated VST3 folder such as C:\Program files\Cakewalk\Vstplugins and scanning it may work. If that fails uninstall and reinstall the plug-in. The installer permits specifying where to put the plug-in. Do not install it or any VST2 plug-ins in C:\Program Files\Common Files\VST3 the scanner will ignore them.

A dotted line indicates automation IS present. The value remains the same as the node on the left side of the dotted line until the jump is made to the node on the right side. Jumps are often used when automating between two states such as toggling between off/on.

A dotted line to the right of a node can indicate either it is the last node on the envelope or the envelop to the right is a jump A dotted line to the left of a node indicates a jump

The actual plug-in ezdrummer.dll should be where ever you installed it. If somehow it was installed in C:\Program Files\Common Files\VST3 the scanner will ignore it. VST2 plug-in cannot be installed in this folder. You could check the exclude list in the Plug-in Manager. To do this, click on VST Instruments (VSTi) in the Plug-in Categories column of the Plug-in Manager. Then click the Show Excluded radio button below the Plug-in Categories column. If the plug-in is there, select it and click the "Enable Plug-in" button. If EZDrummer is not there, make sure the dll is in the scan path (circled in black in the image above). If the dll is in the scan path, open the VstScan.log and VstScanSandbox.log in %appdata%\Cakewalk\Logs and look for info about ezdrummer.dll