scook

Yes it is possible to uninstall but since there is not enough information in these posts to determine the cause of the crashes, it would be best to work with support. If they feel a re-install is needed they will suggest it.

VST3 support was added to SONAR X3. Versions older than X3 do not support VST3 plug-ins.

Also, keep in mind, even with the load balancing option enabled, it may not be used if the latency is set below MinPluginLoadBalancingBufferSamples in AUD.ini. The help goes into some detail about when load balancing is useful.

Dumps sent from inside the program go nowhere. The Cakewalk server that collected dump files was shutdown in Nov. 2017. BandLab does not have an automated process to collect dump files. The current process relies on the user uploading the files not the program Here are the plug-ins included in CbB. BandLab recommends that those who own Platinum leave it installed when installing CbB. This way CbB can take advantage of the plug-ins bundled with Platinum.

Record a little using both the M-Audio Hammer-88 and Akai MPX8 Then open the Event List View and compare the data This may help show the difference between the MIDI sent by the two controllers

Yes, the drum replacer works with audio to replace/reinforce the existing audio or extract MIDI data.

There is no reason to use the drum replacer when working with MIDI drum data. Use the cymbal MIDI data to drive a different synth. Either break out the MIDI data to a different track or use a Drum map to drive AD and what ever is playing the cymbal samples.

Cakewalk lists what the driver reports.

If the interface works outside of Platinum, try renaming %appdata%\Cakewalk\SONAR Platinum\AUD,ini and starting SONAR

Ask Jim again and write down the solution

Yes, it does make sense. Thanks for coming back and adding the resolution. Glad it is working for you now.

Sounds like an activation issue. This is the type of behavior the plug-in shows when trying to run the version bundled with Samplitude. Although that version is locked to Samplitude, it passes the CbB scanner OK but crashes the DAW when loading it into a project.

There is only one preference setting to toggle the Start Screen. If Show Start Screen is enabled, the start screen should launch regardless of the On Startup Load the Default Template setting. When the start screen is running there should be three entries "Cakewalk Start Screen" under "Cakewalk Applications" in the Windows Task Manager. To the OP, it might be interesting to see what support@cakewalk.com has to say about this problem. I have never had any trouble with the program launching but one thing to try is Shutdown CbB Make sure no Cakewalk processes are running in the Window Task Manager Rename the %AppData%\Cakewalk\Cakewalk Core\StartPageCache Start CbB The start screen will recreate the StartPageCache. If the problem was a corrupted cache, this should fix the problem. While waiting for a resolution, you could try Cakewalk Launchpad. It can serve as a start screen replacement albeit not as tightly integrated as the CbB start screen. The program is available on my Google page.

The Cakewalk Command Center required installers written for the application. The Command Center was rolled out in 2015 along with SONAR Artist/Professional/Platinum. Only a few products released prior to 2015 had installers updated for the Command Center. Z3ta+2 and CA-2A were two of them. DAWs released prior to 2015 were not updated. All products with downloadable installers including the ones that show up in the Command Center should be in your old Cakewalk account.

The only data that may be lost are custom settings you may have made.

Try increasing the Playback using nnn Millisecond Buffers setting in preferences from 250 to 500 or 750. Some use much larger values. If that does not fix the problem consider supplying more information such as Hardware details - PC and Audio interface Software details - OS and DAW version info MIDI - whether using a third party MIDI file or entered manually. Project sample rate

Cakewalk bought the source code for Bitbridge. That said, there is a limit to how much time a company can/should spend supporting third party software, in this case 32bit plug-ins, that the manufacturer no longer supports. Bridges were not intended to permanently extend the life of 32bit plug-ins. The main purpose was to allow manufacturers and users time to transition to 64bit. Continued reliance on a few pieces of software that are no longer maintained or supported while updating everything else is not a recipe for success.

This did not happen unless you manually sent the dump to BandLab support. There has been no automatic process since Nov 2017. Sometimes, it is helpful to know if a factory DP preset was used and if so, the name of the preset.

I prefer Drum Maps with the Drum Grid Pane instead of the step sequencer for drum programming.

One way to have all instances of the step sequencer load a custom set of rows is route the MIDI output to a drum map. Alternately copy/paste/unlink the clip to create a second instance with the same row setup then clear the pattern or Save an empty pattern with the step sequencer setup as desired then load the pattern after creating the new clip. This is sometimes referred to as a step sequencer template. A difference between using a drum map and step sequencer templates is drum maps affect the whole track, step sequencer templates affect one instance of the step sequencer.

Sometimes they just need the project file but see what support says.

Yes, the re-save should be a one time event for each project. At least, there is a process to move forward without losing data. Since you are saving them under a different name, it is possible that BandLab may benefit from seeing one of the failing project files. They may be able to address what ever is causing the problem.

The synth rack is a separate view and may be added to the project at any time from the view menu or keyboard shortcut ALT+9. When I open projects in safe mode, the browser is not displayed, keyboard shortcut B will toggle the browser display. Save the project under a different name (you can save it in the same folder if you wish) and see if it will open without running in safe mode.

It is a process of elimination. Assuming Kontakt and Battery are relatively new, they are unlikely the problem as others use them too, Suspect freeware/shareware and 32bit plug-ins first.

Likely a plug-in issue SONAR and CbB check the project to see if it was created by a newer version. If so, the DAW displays a warning message. This does not prevent the older DAW from opening the project but there may be features missing. The only case I know of that prevents a newer project from opening in an older DAW is when the project contains patch points or aux tracks. Older DAWs cannot open these projects at all and there is no warning message displayed. Hang on exit is likely plug-in related. BandLab may be able to identify the plug-in from a hang dump. This thread describes how to created the dump