scook

Yes, it is. Dragging MIDI into CbB is an import function. CbB Import strips tempo data from MIDI files. Opening MIDI files preserves MIDI tempo data. MIDI file save and export include MIDI data. Not sure how the other DAW works but it should be easy to see if a MIDI file contains tempo by opening the file in CbB, playing the file or view the data using MIDICSV

The instructions ask that the project and steps to create the drop out be mailed to support@cakewalk.com May want to include info about the OS, buffer settings from the mixing latency section of preferences, audio interface make and model, driver mode from preferences and driver version number

There is "no clear solution" because the problem is system dependent. Something on the PC is preventing the DAW from creating files. Some possibilities are hardware failure, permissions, disk compression, antivirus or antimalware software. Make sure the project audio folder is not compressed and the permissions are open. Make sure the antivirus/antimalware software is current. If the problem goes away when the AV software is disabled, add CbB to the program's whitelist. Some have reported ByteFence antimalware being installed surreptitiously. Consider deleting this software.

All the AddOns are optional. Here is an image of BandLab Assistant showing the "Install Addon..." menu option. None are installed by default. Once installed, the options are disabled in BandLab Assistant.

On startup, CbB checks the registry for audio drivers. When it does a bug in some versions of Yamaha ASIO drivers cause them to launch their update process which fails throwing messages like the one in the OP.

Panic button is in the transport module http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=ControlBar.06.html

Use Waves v12 plug-ins?

There is only one way user layouts are deleted in CbB, by clicking the delete button next to the Save button in the upper right of the Plug-in Manager.

The tmp files in the layout folder are created by the "Sort by" layouts supplied with the DAW and are built on the fly as needed. User created layouts have a .pgl extension. The "Sort by Category" modifications are stored in %appdata%\Cakewalk\library\library.db

Orphaned envelopes used to be pretty common when deleting plug-ins that were automated. To remove, SHIFT-click the automation envelope then right click and delete using the context menu.

The custom plug-in layout path is specified in preferences The default location is "%appdata%\Cakewalk\Cakewalk Core\Plug-in Menu Layouts"

Nothing has changed since this thread. The key is to know what needs to be installed in order. What happens when these are installed out of order. And how to fix an out of order install. Assuming you have the SONAR Platinum/Producer series, 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. Then, at your leisure and in no particular order, run the Platinum plug-in installers and use the advanced install option for X3 and older to pick up plug-ins as needed. There is a spreadsheet linked in the thread containing the SONAR plug-in bundle history.

Run a VST reset from preferences. Avoid running the scanner from the Plug-in Manager. If the plug-in(s) still show up in the "Registered Plug-ins" column, clicking on them reveals their fully qualified file names at the bottom of the Plug-in Manager.

If I'm not mistaken, you have to run CbB as admin for some of these older plugins. After registration both of these plug-ins run without elevated privileges. The only other 64bit Cakewalk plug-in that needed admin access was Pentagon I and the registry mod to eliminate this requirement has been published several times.

Could be easy to test by creating custom track and automation lane buttons in the theme editor.

The help menu has links to several pages in http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=toc.html A pdf version of the help is available here The web-based help is updated with every release. The pdf is updated less frequently.

If you need the yamaha driver look for an update. If not uninstall it.

The custom plug-in layouts are stored on disk in the folder specified in Plug-in Layouts preferences Make a copy of the folder and/or use different names to save the new layouts.

"Do not intercept NRPNs" should work as long as it is enabled before the plug-in attempts to play any data. Once the offending data streams through the plug-in, the sfz engine is shut down for the session. The only way to reset the sfz engine is restart the project or reload the plug-in.

WRT muting SI plug-ins see Crashing may be data related too but I can't say without working with the clips myself. The Event List View may help. Compare the clips with some that work.

The gain knob and volume slider do the exact same thing at different places in the signal flow. Which one to use depends on where one wants to adjust the level. As noted above Cakewalk records the signal at its track inputs. Plug-ins added to a track come after the input. Understanding the signal flow is important.

TTS-1 is a 16 in X 4 out synth. There are several ways to create a project with 1 instance of TTS-1 using all its I/O. After adding the synth to a project, add 15 additional MIDI tracks. Set the output of each track to TTS-1 and specify the MIDI channel in all the tracks. Now there are 16 channels set up, one for each TTS-1 input. Assign the instruments on each track (or in TTS-1 on each channel) as you have done in the past when using one track. If you want to send the 16 channels to more than one output add up to 3 more audio tracks set the inputs on the audio tracks to the additional TTS-1 outputs open TTS-1 and assign the channels in TTS-1 to the different outputs by clicking on System then Option like this

File size is covered in the documentation http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=AudioPerformance.16.html But they don't both to document sample rates above 96kHz.