scook

The registration info should be in your NI account.

Soft synth audio recording

Yes, starting with SONAR X3. On 64bit Windows, 32 and 64bit DX plug-ins are registered in different locations. If fact all the 32bit software registry entries are kept separately under WOW6432Node. Both 32 and 64bit versions of old Cakewalk DAWs may be installed on the same machine. It has been that way since the introduction of 64bit SONAR. Both the software and registry entries are stored in different locations. What they will share are Cakewalk Content, the user directory and ProgramData. Folders are created for each product but the data in the folders are not 32/64bit specific. If this is a 32bit X-series version of SONAR, you should be using preferences to perform plug-in scanning operations. That said, when the scanner options are disabled it most often means the registry entry for the scanner is bad or missing. Running a full-personalization which overwrites the files in the user directory also attempts to restore the registry entry for the scanner. To perform a full-personalization depends on which version of SONAR is running for X3 and older hold down SHIFT+CTRL while opening the DAW for SONAR newer than X3 hold down the CTRL while opening the DAW This will present a dialog about personalization. Use the dialog to confirm running personalization. If this does not work, re-install the DAW. The fact that all VSTs are missing and the scanner entry may be missing means something happened to the registry. Possibly a registry cleaner was run and accidently removed the entries.

No, the instruments and FXs provided in BandLab only run in the BandLab app. There are thousands of free and paid plug-ins available for Cakewalk by BandLab. Here are a couple of threads to get you started

This is not good advice. I replied to your thread and use of ASIO4All. There is a real possibility the generic drivers are preventing the factory driver from working correctly.

As a rule, USB microphones work like any other audio interface. This means they provide a way to monitor the signal being recorded. To hear both the signal being recorded and other data from the DAW at the same time, the track(s) being recorded must have input echo enabled. Input echo button is just right of the record button in the track header. Working with a real ASIO driver usually means recording and monitoring happens on the same device because ASIO is limited to one driver at a time. Since ASIO4All is not a real ASIO driver but wraps WDM drivers, it is possible to record using one driver and playback using a different one. Of course, this is only possible because WDM supports it. ASIO4All brings nothing to the party but another software layer. CbB supports WDM directly. Win10 and 11 are known to perform better using the WASAPI modes. Bottom line, ASIO4All is not recommended. It appears Zoom provides an ASIO driver and if this is the case and not simply a rebadged generic driver, this is the best choice for the device. I see Zoom also bundles a copy of Cubase LE. This too may install a generic ASIO driver. There should be at most one ASIO driver installed for any device. There is a real possibility there are at least 3 ASIO drivers installed for the H2n, the factory driver, ASIO4ALL and the "Generic Low Latency" driver. This can result in performance issues with the factory supplied driver just like this user was having

no

I answered in your thread

This error can occur when "Controlled folder access" is enabled in Windows Defender.

I believe jBridge may be used to load 64bit plug-ins into 32bit hosts.

Could just set the interleave to mono but I prefer to bounce the track using the Split Mono channel format then throw away the empty track and set the pan on the good track as needed.

Did you select a clip to edit before running RX9 from the menu? The RX9 editor does not load in CbB. CbB launches RX9 with a copy of the selected clip as an argument on its command line. Upon closing RX9, CbB reloads the clip into the project.

Edit is read only and populated from existing Tools entries based on the Show Defaults drop down. The Edit drop down would be empty if Show Defaults is set to No and no user entries were found in the registry.

Trying to launch RX9 or any WaveEditor type without first selecting a clip will disable the tool. First select a clip then launch the tool. Here is my RX9 setup in CbB Tools Yours should look similar.

You are welcome. Nobody in this thread works for BandLab.

Chage the driver mode to ASIO and verify the driver is selected in Preferences > Audio > Devices MIDI Driver mode has nothing to do with audio but may determine whether or not MIDI data is received from the MIDI side of the interface.

That should work

An interface should have at most one driver in HKEY_LOCAL_MACHINE\SOFTWARE\ASIO Since generic drivers can work with any connected device, there are 4 ASIO drivers installed for the Komplete Determine which of the Komplete entries is the newest and remove all the rest. May want to export the Komplete driver before deleting it just in case the driver you select does not work. If it does not work replace it with the other Komplete driver.

That is the MIDI driver mode NOT the audio driver and has no effect on audio playback. The audio driver mode is in Preferences > Audio > Playback and Recording Yes, it bundles a generic low latency driver and, like all other generic ASIO drivers, is known to interfere with factory supplied ASIO drivers. Either uninstall it or remove its entry from HKEY_LOCAL_MACHINE\SOFTWARE\ASIO In the registry. Use regedit to remove the generic low latency driver and any others except for the Komplete interface.

Re-install the ASIO driver https://support.native-instruments.com/hc/en-us/articles/360001194217-Installing-the-ASIO-Driver-for-KOMPLETE-AUDIO-1-2-6-MK2-Windows- Make sure it is the only ASIO driver in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\ASIO

Either testers did not have the error (one user in this thread reported EZD3 runs OK) or they did and failed to report it or they reported the problem and Toontrack released the product anyway. I am sure there is more than one bug on the to-do list for EZD3 and probably more than one bug that crashes the plug-in. Chances are there are more bugs yet to be reported.

As best I can tell from the three threads created by the OP, there are issues with 2 VST3 plug-ins: EZ Drummer 3 and Session Drummer 3. This was compounded by the plug-in browser appearing to have VST3 plug-ins "greyed out" with icons that looked like they were disconnected suggesting the plug-ins were disabled. Toontrack has already acknowledged issues with both plug-ins on their forum and the plug-in browser is properly displaying the plug-ins based on the active theme.

WRT EZD3 there is a thread on the Toontrack forum https://www.toontrack.com/forums/topic/ezd3-crash-on-loading-vst-into-cakewalk-by-bandlab/ with a post from one of the devs

There is a thread about this on the Toontrack forum https://www.toontrack.com/forums/topic/ezd3-crash-on-loading-vst-into-cakewalk-by-bandlab/ with a post from a Toontrack dev

It's a new plug-in and Toontrack only recently starting publishing VST3 plug-ins. While not definitive, these are pretty good indications Toontrack may need to address the issue. I have not seen the error messages generated by EZD3 but the one in this thread generated by SD3 was from the plug-in.