• SONAR
  • AAS Ultra Analog VA2 crashing Cake
2018/08/02 01:07:51
35mm
I'm not sure when this problem started because I have only been using Cake for mixing older projects recorded with Sonar, but tonight I decided to launch Cake just to have a bit of a play and I decided Ultra Analog would be fun, so I dragged it in and created a simple inst track, but as soon as I do Cake crashes every time. I never had any problems with UA in Sonar or other DAWs. This only happens with UA so far. I have tried reinstalling UA but to no avail. Any ideas?
 
BTW it's the 64bit version that is crashing Cake.
2018/08/02 06:02:24
promidi
I am not having this issue with 64bit Ultra Analog VA2 and Cakewalk by Bandlab

Which version (numerically) of Ultra Analog VA2 do you have?  The latest is 2.2.1
2018/08/02 19:19:32
35mm
I have v2.2.1. It's working fine in other DAWs. Have not tested in Sonar yet, crashes Cake every time I add it as simple instrument track.
2018/08/02 19:42:27
scook
FWIW
Just installed AAS UA VA-2 v2.2.1
No problem adding the VST2 or VST3 to a project in CbB 2018.07 on Win10 Home.
2018/08/02 21:58:24
Sidroe
I just went thru 5 excruciating days of the same symptoms with VB3!!! The culprit turned out to be a corrupt or interrupted Windows 10 update that was installed the 25th of July!!!
I would take a look at that. Simply go to settings and check your update history in Windows Update. You can uninstall that update and let Windows Update reinstall it. It straightened VB3 out for me.
Can't make any promises.
2018/08/02 22:10:04
Brando
scook
.....AAS UA VA-2 v2.2.1
No problem adding the VST2 or VST3 to a project in CbB 2018.07 on Win10 Home.

Same here, with Windows 10 Pro. UA 64 bit.
2018/08/02 22:12:51
35mm
Hmm, the latest Cake update seems to have fixed the issue. 
2018/08/02 22:29:21
scook
VST2 and VST3 work here in the previous CbB release (2018.6.0.14) too.
2018/08/02 22:29:21
scook
VST2 and VST3 work here in the previous CbB release (2018.6.0.14) too.
2018/08/03 10:45:13
pwalpwal
Sidroe
I just went thru 5 excruciating days of the same symptoms with VB3!!! The culprit turned out to be a corrupt or interrupted Windows 10 update that was installed the 25th of July!!!
I would take a look at that. Simply go to settings and check your update history in Windows Update. You can uninstall that update and let Windows Update reinstall it. It straightened VB3 out for me.
Can't make any promises.

what's the KB number of the update, please?
and how did you figure it out, trial and error?
i wonder, is it the same update that broke the ni controller stuff?
/tia
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account