Promidi

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-

Here is one thing I can think of. If you inadvertently choose a clip background colour that is similar to your waveform colour, the waveform outline will allow you to still see the waveform clearly. That being said, it’s optional and can be switched off if you don’t feel you need it..

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

Do your projects contain lots of automation? Under “High resolution plug-in automation improvements” it mentions that “Plug-in automation envelopes were previously being decimated at a uniform 50 msec interval” This has been changed to 5 milliseconds The decimation interval can be changed via the audio configuration (Preferences | Audio | configuration File) property AutomationDecimationMsec (2-30) in preferences.

Is this after installing build 145 and then heading to Preferences | File | initialisation file and adding the option ExceptionHandlingSeverity and setting it to a value of 5 and then restarting CbB? To go back to the default setting, delete this value (the actual default value is currently 7)

Thanks for this quick update. On my PC, these issue are now resolved with Build 145.

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/

With CbB 2021.4 Build 144, try the Category drop down. On mine, Track View is missing. On Build 125, it’s there.

Confirmed here as well. I do actually have some custom keybindings that I had under the Track-View Category that still work. Ripple Edit. This is even when Workspaces is set to none I have lodged a support ticket.

Thanks for confirming this and for that extra detail. The snapping of the aim assist, in the PRV, worked as expected when measure 1:01 is visible. I have lodged a support ticket with Cakewalk support.

I was able the rearrange the entire folder, with contents, by dragging ....without having to collapse the folder.

Strictly as a test, do you get the same issue with Insight 2 (You can try the trial version)

Hi guys I am on CbB 2021.4 Build 144. I have my global snap set to 1/16 and snap behaviour set to “Snap to”. My PRV snap override is turned off. Aim assist is enabled with the “Show Aim Assist Time” time display is enabled. This issue only happens in the PRV. In track view, it’s fine. When the mouse pointer is over anything but the PRV ruler, the Aim Assist line snaps to the correct location. However, when the mouse pointer is over the time PRV’s ruler, the Aim Assist line itself is actually offset to where it should be. The Aim Assist Time as displayed is correct. Also, the time of the next action (note placement) is also correct. ie the note gets placed where the Aim Assist should be. I did not notice this happening when checking the ER Can someone please verify this for me. My next move is a Cakewalk support ticket, but I just wanted to see of anyone else is experiencing this issue.

More info needed.