scook

There is a link to the User Reference PDF at the top of this forum BTW, the current pdf does include 2021.04

Which ones? Just like the old website, the old Cakewalk tutorials are products of the old company. AFAIK, no videos officially released by BandLab show any old Cakewalk DAWs.

It is easier to perform the initial install with an internet connection using BandLab Assistant. Once installed, the machine not connected to the internet may be re-activated using the machine with internet access using a method similar to the Platinum process. Update installers using the in-app update on the connected machine are easily copied between machines.

Of course, sometimes answers are for the benefit of the forum and not the poster. There are now 3+ years of "New Features" not integrated into the help. It may be reorganization time.

The dropout toast message should have additional information for diagnosing the problem. There is a process described in this post for "What if the application hangs but doesn't crash?"

As long as there has been a web-based help system, this system has always been the source of the most recent information. The pdf is produced by reformatting this data. This file is updated as time permits. For the most current information use the web.

Add another bus to the project Change the bus name as needed Open metronome settings in preferences and set the audio metronome drop down to the new bus

ASIO4All is not an ASIO driver. It is a wrapper for WDM drivers intended for use with programs that require ASIO. CbB does not require ASIO, it can use WASAPI and WDM drivers directly. When most users recommend using ASIO, they are not talking about ASIO4All. They are referring to a manufacturer supplied ASIO driver for the audio interface, As a rule, a manufacturer supplied ASIO driver performs better than Windows drivers (WASAPI and WDM). The exception being Realtek. Their ASIO driver is not very good. When using the internal sound chip on Win10, WASAPI is the best choice. When using an audio interface designed for DAW use, the first choice is the manufacturers ASIO driver. If the manufacture does not supply an ASIO driver or if they use ASIO4All, avoid the interface. Focusrite supplies ASIO drivers for their interfaces.

notes browser

This is a problem. Vstscan.exe is not designed to run from the command line. It should always be run from preferences.

If images identified in the post I linked were modified the theme should work. There was no indication in the thread what was done other than opening and resaving the theme. This does nothing to correct image sizes. New images must be added to the theme. the current images must be resized with an image editor or the images removed so that the theme uses the Mercury images.

The images in the user theme must be modified to their new size. This may be done by using the images from Tungsten, any user theme that has already been updated or removing the images allowing the theme to use the Mercury images. Maybe this post may make more sense now It did not seem to be very well received when originally posted.

When testing make sure CbB session starts up loading Mercury or Tungsten. If the custom theme is loaded first, swapping to Mercury or Tungsten will still have image size problems. After changing from a custom theme to Mercury or Tungsten shut down and restart CbB.

Not my experience at all. I have applied every update since CbB was released, some several times using the rollback installers. Not once has it been necessary to perform a clean install or reconfigure CbB. Also, I do not run CbB as administrator, never have.

Have not seen a report like this in some time. If you are manually running the scanner make sure to run it from preferences Also regardless of how the scanner is setup to run make sure "Scan in Sandbox" is enabled. And keep the two rescan options just above the "Scan in Box" unchecked. If it continues to hang, temporarily move the offending dll(s) out of the scan path until a scan runs to completion, then restore them and run one more scan.

I render all region FX clips in the session they are created in. If you are concerned Install 4 Go through the old projects and render the clips. Then apply the upgrade to 5. If you want a path to undo, always work on a copy of the track.

The audio driver mode, WASAPI or ASIO has nothing to do with MIDI. When using ASIO4All, the audio drivers presented to the DAW are defined in the ASIO4All software.

This is the reason I recommend skipping Assistant. The Melodyne feature matrix is here

There can only be one version of Melodyne plug-ins installed on a PC at a time. The standalone Melodyne programs reside in their own folders so multiple versions of these may be on the same PC. You can use the trial of 5 if you wish and re-install 4 if you elect not to purchase 5. FYI, there is a Melodyne sale going on through Jun 30 I could not find any info about a free upgrade from Melodyne 4 Essential other than a grace period for those who registered after Mar 1 2020). Purchasing an upgrade to Assistant is the cheapest solution ATM. The resellers in the link above have better prices than Celemony. If it is in the budget, Editor is a better solution. It provides all the detection algorithms. The product comparison chart is here My reading of the information quoted in the post suggested, re-installing 4 should put everything back as it was. That said, I have not tried going back to version 4 from 5. This may be a question for Celemony support.

As a rule, when a user has a licensed version of Melodyne, they should use the version of Melodyne available in their Celemony account. Unlike SONAR X3 Studio/Producer and Professional/Platinum, CbB does not include a license for Melodyne. In fact Cakewalk only supplied one Melodyne license for each full version of their DAW. Upgrades from X3 did not include a second license. Users were expected to download Melodyne from their Celemony account. CbB includes a time-limited trial version. You can use the trial version and see if you want to purchase the upgrade or install the licensed version Melodyne from your Celemony account.

While I generally leave the drop down at the default "Automatic Background Scan" the Scan and Reset buttons have always been available regardless of the setting. One thing that will disable the Scan and Reset buttons is a bad VSTScanPath entry in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST VSTScanPath should contain the fully qualified name of the VstScan.exe. The default VSTScanPath entry is C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe IIRC, this is one of the registry values restored when running a full personalization (to run hold down the CTRL key while starting CbB) or manually update the registry. Other issues in @Olaf's post may be related to a bad install too. They may be fixed with a simple uninstall/re-install; if that fails, a clean install. When running a clean install be aware step 9 may remove 3rd party plug-ins. Backup/copy the Vstplugins folders to prevent data loss. @Milton Sica unless you have intentionally added VST plug-ins to "C:\Program Files\Cakewalk\Shared Plugins" (not recommended) this should not be in the scan path. No Cakewalk DAW or CbB install VST plug-ins into that path. Everything in there is DX format. Also it is a good practice to leave the two rescan options under the scan frequency drop down deselected (the default setting). To deselected them change the scan frequency to "Manual Scan", uncheck both options then restore the scan frequency.

Yes, VST2 plug-in binaries have a dll extention; VST3 plug-in binaries have a vst3 extension. Files with any other extension are not scanned by the VST plug-in scanner.

Or click-drag on the timeline

It is possible to extend the range of SI-Bass with a little modification to the sfz files.

All the plug-ins mentioned here are not effects like the ampsim TH-U, they are synths. Like most synths, these bass plug-ins use MIDI for input not the audio from a guitar.