scook

In Cakewalk there is no concept of a VST MIDI effect. Still effects can send and receive MIDI data. The scanner determines the plug-in type and while this may be manually overridden it is not necessary. The VST2/3 drop down above the plug-in UI has switches to enable MIDI input and output. By default, synths always have MIDI input enabled. For those capable of sending MIDI data, MIDI output is enabled by default otherwise it is disabled. For effects, these options are turned off by default and depending on the plug-in's features may be disabled. There is no way to pass MIDI data from one VST effect to directly another so, even if one puts VST MIDI effects in an FX chain, the MIDI data would not flow from one plug-in to another. With very few exceptions, to send MIDI data to a plug-in requires an instrument or MIDI track. Plug-ins with "Enable MIDI input" enabled appear in MIDI track output drop downs. Plug-ins with "Enable MIDI output" enabled appear in instrument and MIDI track input drop downs. Even if a synth does not create audio an audio track is required. When using VST plug-ins such as MIDI sequencers, they must be added using an instrument track or audio+MIDI track pair.

Check the size of the audio files. Often this error is the result of trying to import zero length files.

Yes, Waves side-chain support requires their VST3 plug-ins.

The add-ons may be downloaded and installed at any time. While the full Melodyne times out causing the editor to stop working, monophonic audio to MIDI and tempo track creation continue to work after the trial period.

There is no way to directly route MIDI data to an audio track. It must be routed to something that can interpret the MIDI data. To make a plug-in available in a MIDI track output drop down select "Enable MIDI Input" in the VST2/3 drop down above the plug-in UI. This should be enabled by default for synth plug-ins.

At least until the next revision to the dll.

Which driver modes have you tried? Do not install the Realtek ASIO driver. Does Windows see the chip?

Are the plug-ins in the VST3 folder on the D drive. This is a non-standard location for VST3 plug-ins and may not work.

Not trusting my memory any more tonight, I reviewed the code. Guess I could take my own advice and read the Launchpad pdf. It has a section about this issue. From the "Cakewalk Launchpad.pdf" CbB 2019.09 is the first version requiring a dll using the format CW130Auto-{version number},dll Anything older than 2019.09 can use bucwa.dll. Thanks for pressing for clarification. Sorry for the confusion.

The default location for CbB (Cakewalk by BandLab) is C:\Program Files\Cakewalk\Cakewalk Core Does CbB load the project OK? Were there any error messages during CbB install?

I have X2, X3, Platinum and several versions of CbB installed on the same Win10 machine. This has nothing to do with beat detection, it is the 32bit plug-in bridge software. It is loaded only when 64bit SONAR/CbB encounter 32bit plug-ins in a project. While I do open X3 regularly for testing purposes; I do not recall testing 32bit plug-ins in it. Just tried loading a 32bit plug-in, shutdown X3 saving the project and restarted X3. All worked OK. Installing CbB acts like an upgrade to 64bit SONAR. This means, the CbB and all of its data are in separate folders EXCEPT for the "shared" folders. These folders are updated with backward compatible files. BitBridge is in one of the "shared" folders. It is the shared folders and registry entries that make it necessary to install CbB on the same drive as SONAR. Is it possible that CbB and X3 are on different drives? On a related note, it may be time to stop using 32bit plug-ins in new projects.

Yeah, it comes with a dll for the legacy CbB through Nov 2019 and has special logic to handle those versions of CbB. Anything from Dec 2019 to now, it relies on building the catalog of versioned dlls based on what it finds in shared utility folder. It may be the case that Dec 2019 to current may be able to use the current dll. I have not tested it. If the dll has not been changed in time frame it should work just like it did in 2018-Nov2019. If it does work, one could manually populate the "sub" folder under the Lauchpad install folder with the necessary dlls. I don't actually check the dlls in this folder but rely on file names. All the files but the included legacy dll use the naming convention CW130Auto-{version number},dll

Does this mean that an older version of CbB will result in automation failure if run using the current version of CW130Auto.dll? Or is it backward compatible? Actually, what I posted was backwards. Running old versions of the DAW using the new dll in late 2019 was the problem. IOW, the new dll broke backward compatibility. Sorry for the confusion.

CW130Auto.dll in shared utilities is version specific. It was unchanged from the first release until late 2019 so any CbB during that time could use any version of the dll. Trying to use a newer version of CbB with a 2019 or older version of the dll results in automation failure. Since the dll is versioned with the main program and subject to change without notice copying the program folder only is unreliable. Even before the change to CW130Auto.dll there was always a risk involved in not copying the shared utilities folder. The thing is, while the program runs fine from any folder; there can only be one shared utilities folder. Fortunately, the current practice of providing a rollback option with every new release make the risk of a bad plug-in manager or scanner very low. To facilitate having multiple versions of CbB available online, Launchpad keeps versions of CW130Auto.dll for each version of CbB installed and makes sure the appropriate dll is available in the shared utilities folder.

The interface has an ASIO driver https://www.roland.com/us/products/rubix44/downloads/ It should be installed and the ASIO driver mode should be used in CbB the video is from https://www.roland.com/us/rtv/quick_start/rubix_series_quick_start/trJ6cPmOlqw/

When someone reports volume problems with MIDI on stopping the CbB transport, the first thing it calls to mind is the Zero Controllers When Play Stops setting.

I got the info from a book.

yes, if you have no other interface to try

could see if the PC sound chip fails the same way

This covers installing SONAR and CbB The key is to know what needs to be installed in order and what happens if they are not. The condensed version is advanced install using minimal installation of X2+X2a to get V-Vocal (there is an video in the thread about this) install at least the Platinum program install CbB That is it for the items to install in order. Installing out of order usually means the most recent version of shared utilities is overwritten. The quick fix is uninstall and reinstall CbB. At your leisure and in no particular order run the Platinum plug-in installers and use the advanced install option for X3 and older as needed to pick up plug-ins as needed.

yes, I updated LaunchPad in Dec. 2019 to keep track of the extra dll.

Unfortunately that thread is a little out of date. Changes to CbB late in 2019 made it no longer enough to simply copy the Cakewalk Core program folder and use it along side the current release.

From http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.27.html

If you need a tester, I'll be glad to help BTW, I created a drum map for default 808 kit. It is in the preset section of my Google page for CbB

I cannot speak for most people but my custom build DAW came with the Realtek chip disabled. All Windows audio runs through the same interface CbB uses.