Promidi

One command that I know will categorically crash Cakewalk by Bandlab is the Editslide and Editslide40 command. Therefore if you wish to move the temporal position of a MIDI event, you have to directly edit the Event.Time parameter instead of the above commands. There are some behavioural differences in some commands as well. For instance, in CbB, An EditPaste or EditPaste40 command, without arguments, will perform the paste unconditionally, without a dialogue box. In earlier versions, An EditPaste or EditPaste40 command without arguments will bring up a dialogue box. Adding parameters to these particular (paste cut copy) commands in CbB can result in a crash. Also, any CAL scripts that use time parameters will only work correctly is your Preferences | Project | Clock > Ticks per quarter note is set to 960. Any other value will result in CAL commands that have time arguments not being executed correctly. For instance, the Insert command won't place the event at the specified time. You just have to be aware of these idiosyncrasies when writing CAL scripts for CbB.

Within 24 hours of sending AAS a support email, I received a reply with the hotfixes for all of their synths. On my system (configured as per signature), Chromophone 3.1.0 Hotfix 1 VST3 allowed me to load multiple instances in CbB 2021.4.Build 170. Prior to this hotfix (Chromophone 3.1.0), I was unable to do this (Even through jBridge) It should be noted that, on my system, the links pointed to on my first post in this thread are still pre hotfix. That is with the FF cache cleared.

On the Focusrite Beta drivers page there is a Beta driver for the Focusrite Scarlett 2i2. The latest BETA driver is version is 4.87.4 In the notes for this version, Cakewalk by Bandlab is specifically mentioned: “Fixed an issue that could cause a crash in Cakewalk by Bandlab” Maybe give these a go This is at http://beta.focusrite.com/ (CTRL + F > "Focusrite USB2 Drivers 4.87.4" without quotes)

I also received a (non canned) reply regarding the multiple instances in Cakewalk issue. So AAS are definitely looking into it.

I have found this also. If, after coping your MIDI clip, you open the paste dialogue , then select "Paste as new clips" before pasting, the resultant clip will not be shortened.

Has anyone actually sent an email off to AAS support? (I have)

See: https://www.cakewalk.com/Documentation?product=SONAR&language=3&help=INI_Files.4.html Scroll down or CTRL + F > "EnablePluginCancelButton" (without quotes)

This requires full Kontakt. (The only instrument that works with the free Kontakt Player is SampleTekk Black, that comes with a license)

Here is my experience on my PC which is configured as per my signature. I have iLok licence manager version 5.3.2 Build 3375 64bit installed. As of 12 May 2021, this is the latest version. I installed Loom II successfully (which does have a built in iLok licence manger in the installer). I did not reboot then. After that had completed, I checked my “Programs and Features” . “Bonjour” was installed (Which installs with the iLok manager). iLok licence manger itself was not installed. To make sure, I opened up the iLok licence manger, make sure it was still the latest. It was. I uninstalled “Bonjour” - this does not need to be installed or present for iLok licence manger to validate iLok licences. I rebooted the PC and it rebooted correctly. I tried using a plugin that I know requires iLok to work. All worked fine.

From the OP "I tried Command Centre but it wouldn't let me in"

What you need to do is find and install an appropriate VST effect - like a wah wah effect plugin. Then add that effect into the track's FX rack See: http://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Mixing.24.html

Do you have IK Multimedia's Orchestral Percussion - which has a specific “Orchestral Castanets”

Which version of Cakewalk? Which version of Windows? What have you tried so far?

MIne's still in the workshop wait for parts....

It's what happens when an OP assumes we are all in possession of a working crystal ball.

One other thing I noticed is this. When I checked the Windows Application Event viewer, There actually were errors that showed up pertaining to the VSThost's loading of Chromophone 3. So even though the plugin loaded in VSThost, it still triggered an error event there as well. So this looks like it still could be an AAS issue.

In response to this thread I did a few tests. I have the latest AAS synths installed with CbB 2021.4 Build 145 and my hardware configuration is as per my signature. Here are the results I could load only one instance of Chromophone 3 VST3 - the second instance load attempt resulted in Cakewalk locking up (no error message) I could load only two instances of Chromophone 3 VST2 - the third instance as above. I got the same result in the latest Sonar Platinum, so it does not look like it's not an issue with the new Cakewalk update. I was able to load multiple instances of Chromophone 3 VST2 and VST3 in another host (VSTHost). So it looks like it’s a historical Cakewalk issue. For the VST2 and VST3 AAS plugins, in their respective plugin properties, I checked the option "Load using jBridge wrapper" (I have the paid version) After doing this, I noted the following: I still could only load two instances of Chromophone 3 VST3 I could load five instances of Chromophone 3 VST2. Having being able to do that, I configured each instance with a different patch (ones I created). I recorded a two measure performance on each track. All tracks played correctly - each with their respective patches. After this I loaded another five more instances of Chromophone 3 VST2. That is, I ended up with ten instances of Chromophone 3 VST2 in this test. The five tracks still played correctly. Conclusion: Until this is sorted - either by Cakewalk or AAS, I believe the current workaround is to use the VST2 versions with jBridge Wrapper. Has someone reported this to Cakewalk support yet?

I do this every time with UVI stuff. The portal is slower than direct download (on my PC anyway)

You are going to get plenty of folk on here say "Works fine here" You have provided no information ("an error crash" tells us nothing) and yet you asked: "Do you have any solution" - not going to happen until you provide much more information.

Cakewalk Support will probably tell you the same thing.....

That CPU is below minimum spec (Clock speed is too low) See: https://help.cakewalk.com/hc/en-us/articles/360021857753-What-are-the-minimum-requirements-for-using-Cakewalk-by-BandLab-

What are your PC specifications (Including the iteration if the i5 CPU)? I have a system as per my signature and I was able to load 6 Spitfire Originals instruments and it did not miss a beat. See: my reply on

Are you running a fully Patched Windows 10 PC (That is, all updates installed)? Have you visually confirmed that all of your hardware drivers are up to date? (Do this using manufacturer's websites rather than by using Windows updates) - do this after installing any Windows updates. My PC is as per my signature and I have never had this issue with any version of Cakewalk to date.

I can confirm that Loop Construction View, Surround Panner, Sysx View, and Video View have always been present. I have also configured some keybindings specifically for the Sysx View which I have used for quite a while now. One thing to note is that is you do use a lot of keybindings and you use workspaces, your workspace will load its own keybindings. Personally, I deselect “Keyboard shortcuts” under “Load From Workspace”in the workspace manager for the workspaces that I use.

Yes See: https://discuss.cakewalk.com/index.php?/topic/28721-current-release-202104/