scook

I mentioned the latency issue in my original post. When mixing a direct signal with the return signal from the DAW normally one does not use input echo for the "live" tracks. This is because there will always be some delay from the DAW because the signal is buffered going into and coming from the DAW by the audio interface driver. When running as ASIO driver this buffer is set by software supplied by the interface manufacturer. Chances are even at the smallest buffer setting the delay will be noticeable when listening to the direct and return signal on the live track. In short, if you want to listen to the live track affected by plug-ins expect a slight delay and turn direct monitoring off.

May need to provide a little information about your setup. If you hear the original signal and the signal from the DAW there is some device mixing these two signals.

FWIW, I just loaded up SD2, SD3 and EZD in CbB 26.01.0.34. All three work OK here. Can't offer any suggestions based on the info provided.

Email service from the old Cakewalk servers was shutdown when Gibson shutdown the old company. To regain access to your old Cakewalk account email support@cakewalk.com

The image looks OK. The plug-in is in the FX Rack and it appears there are IRs in the the plug-in. Whether the plug-in or IRs produce the sound you are looking for is another matter. Try different IRs. Could turn on the QuadCurve EQ and roll off the highs. It may be placed before or after the Cab.

To monitor effects while playing the input echo button must be enabled. This is the button to the right of the record button in track 1 just above the FX rack. When monitoring through the DAW (this is what the input echo does) there may be some delay (often called latency) in hearing the signal. This delay is caused by the audio interface buffers and plug-in delay compensation needed to keep the tracks in sync.

The crash file could be in either %AppData%\Cakewalk\Cakewalk Core\Minidumps or %AppData%\Cakewalk\Cakewalk Core\Minidumps\Plugins. If you are not sure which to send, clear out the folder(s) and generate a fresh dump. Since it appears to happen often, this may be the best way because you will know exactly which plug-in was in use at the time. Once you have the dump file, zip it and upload it to a file hosting service like Google Drive or OneDrive and PM Noel a link to the file.

Closing the BandLab Assistant UI does not shutdown the program. This is typical of programs that have a UI and run in the background. To shutdown BA, click the gear in the upper-left of the UI then click the quit button on the settings page.

I don't believe there were any drum maps published at Toontrack for EZD2 kits but there were some for the original EZD, I found a link to some EZD maps on the old Cakewalk forum Resources and Utilities page. Basic drum maps are pretty easy to create especially using the Ins2map utility also listed on the Resources and Utilities page. This tool is available from http://dis.sesseler.de/ in the Cakewalk SONAR section.

For now, these are accessible using the instrument track inspector - input gain is on the audio tab, velocity trim and MIDI FX Rack are on the MIDI tab

Chances are the VSTScanPath in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Cakewalk VST does not point to the scanner. By default this should be "C:\Program Files\Cakewalk\Shared Utilities\VstScan.exe" - the fully qualified name of the VST scanner. It may be repaired by hold the CTRL+SHIFT keys while opening Cakewalk. If that does not work, you could try editing the registry and fix the value by hand (assuming you can find vstscan.exe) If that does not work, uninstall and reinstall Cakewalk.

May be due to the Workspace setting. Here is an explanation of how shortcuts are handled in workspaces (Note: at the time workspaces were called lenses)

This looks like an error cause by a 32bit plug-in made with Synthedit trying to access a protected area of the disk or registry. This is not part of Cakewalk. It is a plug-in you added. The best solution is find a replacement for the plug-in. Sometimes running the DAW as administrator one time and loading the plug-in resolves the problem because the plug-in creates what it needs on the disk allowing the plug-in to run without admin after the first run. Some Synthedit programs need access to the disk all the time. In these cases, installing the plug-in where user access is unrestricted is the better solution. Running the DAW as administrator solves the issue too albeit not the best idea.

Hi Grant. How did you solve that problem? I in Audio Devices have selected the input and output of Roland UA-33 TRI-CAPTURE. But in the Mode Driver section of MIDI / Playback and Recording, I have selected MME and it does not offer me another option. Greetings, Antonio ASIO is an audio standard. It will not show up in the MIDI driver mode drop down. The only choices in this drop down are MME and UWP. Some devices do not support UWP and it requires Windows 10. The audio driver setting affects "MIDI latency" because the audio driver buffer is where the delay is between hitting a key on the controller and HEARING the result.

All versions of 64bit SONAR and CbB use the same "Cakewalk Content" folder. The path is stored in ContentDir in HKEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software. I have no idea how the SONAR "Cakewalk Content" was moved to from the C drive but it seems like it was done without updating the registry or use of a directory junction. Cakewalk Command Center has a function to move Cakewalk Content but it updates the registry. What ever you did to move SONAR "Cakewalk Content" should work for CbB "Cakewalk Content."

All versions of 64bit SONAR and CbB share some registry entries. When CbB is installed, if these entries exist, the values are displayed but may not be changed. Any paths in preferences may be changed either using preferences or directory junctions. Some registry entries may be changed either using regedit or directory junctions.

You could try but I do not believe the registry entries BA uses are removed when uninstalling CbB or BA. IOW, unless you manually clean up the registry simply uninstalling and reinstalling CbB and BA will not solve your problem. That said, the easier path going forward is registry edit proposed in my first post if you cannot install X1. This may be a good time to contact support@cakewalk.com. They may have a better answer.

Missing features like the Event List View are usually the result of the Workspace setting. Use another workspace or set it to None.

IIIRC Guitar Pro adds a lot of optional data to its MIDI exports. Check the program's export options. Also, if you are using SI Drums, some of this extra data may shut down the synth. Once this synth reads the extra data, it will no longer make a sound until the project is restarted. Here are a couple ways to handle this in CbB: Remove the unneeded data using the Event List View. Usually removing everything before the first note is sufficient. Enable Do not intercept NRPNs in the plug-in properties. Here is an image showing SI Bass but it is the same for SI Drums.

No, the advanced install option something the X1 installer has. What this allows is installation of any of the plug-ins bundled with X1 without actually installing the X1 DAW. This works for everything except V-Vocal which is part of the core X1 install The actual DAW must be installed to get V-Vocal. If you choose to install the 64bit X1 DAW (to get V-Vocal or to have it as a backup to CbB), you need to uninstall CbB before installing X1 and reinstall it after X1 because SONAR and CbB share quite a few files. To insure the shared files are current, CbB must be installed last.

Here are the plug-ins bundled with CbB. If the SI dlls are not installed you can either try reinstalling using the registry edit mentioned above or use the X1 installer. If you prefer not installing the X1 DAW, run the X1 installer, selected 64bit, select advanced install, then pick the plug-ins to install. Many more plug-ins were bundled with most versions of SONAR. This is why BandLab recommends installing 64bit SONAR. If the 64bit version of X1 is not installed, consider uninstalling CbB, installing X1 then reinstall CbB. Make sure the paths are correct in VST Preferences To see what the scanner is doing, run a VST Reset with Generate Scan Log enabled from VST Preferences and review the log.

My guess is this is being handled like all ASIO drivers. The DAW supports one I/O driver at a time. This is the ASIO standard. To switch ASIO drivers, deselected all current I/O settings then pick the one to use.

First make sure the plug-ins did not get installed. By default, the support files for these plug-ins are stored in folders under C:\Program Files\Cakewalk\Studio Instruments. By default, the dlls for the plug-ins are in the SI-Bass Guitar, SI-Drum Kit, SI-Electric Piano and SI-String Section folders under C:\Program Files\Cakewalk\Vstplugins. If an item is checked and grayed out, BandLab Assistant found a record that it has already installed the item. These records are stored in KEY_LOCAL_MACHINE\SOFTWARE\Cakewalk Music Software\Cakewalk\Installers I cannot tell you the record ID because I did not install the suite using BA. It should be pretty clear by looking at the info in the records. Removing the appropriate record will remove the check mark and enable the install option BA. That said, the SI Suite plug-ins have not changed since 20811 and were bundled with every version of SONAR X1 (except for LE if there was an X1 LE). BandLab recommends installing your most recent 64bit version of SONAR prior to installing CbB to gain access to all the content bundled with SONAR.

The document index is often useful

My post must have been made before the release of 2019.09. There were some changes to the transport operations. Refer to this thread and the what's new section in the documentation http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=NewFeatures.21.html