Steve Moddelmog

Interesting idea. I'll give it a try and report back.

I updated my NVidia drivers but the problem persists. I seem to be ok with Chromaphone 2 now, so it's not a "crash," per se -- If I'm willing to wait long enough (several minutes) and use of 36GB of memory, I can use the VA-3 VST3. I have been distracted the past several days looking after my new granddaughter so the parents could have a long weekend getaway, but I will try to get support from AAS today or tomorrow. A new version of the AAS plugins was made available since the issue started for me (from 3.1.1 to 3.1.2 for VA-3), but it did not fix the problem. One thing I'm pretty sure of is that the problem surfaced shortly after the Windows update that "fixed" the Windows search issue. I have read that people have had issues with all sorts of things, including sound devices, as a result of that update. If I were really energetic, I would uninstall the update and see if it made a difference. Since I can use the VST2, there seems to be not much reason to go to that trouble for what may be a dead end.

There have been some recent updates, but they didn't solve my problem. I'm going to contact AAS directly but have been too busy to put it in writing. I doubt if they would appreciate me just providing a link to this topic. I've got Lounge Lizard but haven't used it lately. I'll give it a try and see what happens.

One more thing I want to reiterate - none of this happens with project sample rate set at 44.1 - only at 48000 or higher. At 44.1, memory usage is normal when inserting Ultra Analog VA-3, and I produce sound hitting a key on my MIDI keyboard as soon as I insert the synth.

Thanks. Just did it.

There are a lot of dumps over the past few days while I've been fooling around with this. None are in the Plugins subfolder of MiniDumps. How do I send them to you? Thanks.

Revo Pro is an uninstaller utility. Do you mean by inserting Ultra Analog VA-3? Yes, it happens just by creating a projecting and inserting Ultra Analog VA-3 (Ultra Analog VA-3 loads a default preset when you insert it). If I then look at task manager without doing anything else, I watch the memory usage slowing creep up to 36GB, and until it reaches that, hitting a note on my MIDI keyboard does not produce a sound.

Saw a post about changing the Thread Scheduling Model with the introduction of an "aggressive" option, so I decided to try Chromaphone 2 and Ulatra Analog VA-3 VTS3s with it set a 3. Both crashed. Setting at 0, 1, or 2 allowed me to run Chromaphone 2 as a VST3, but not Ultra Analog VA-3. It crashes under all settings. Still very frustrated, as this was working fine two weeks ago. And it seems odd that I can open projects created January 15 or prior that use the VA-3 VST3 with no problem - no spike in memory usage - but cannot insert a new instance.

OK, stranger still... I uninstalled all of my AAS stuff that had VST3 versions using Revo Pro. Rebooted and reinstalled all. Chromaphone 2 worked again with sample rate of 48000 - good start. I guess the key was uninstalling with Revo Pro, which got rid of more stuff than a simple uninstall in Windows. However, Ultra Analog VA-3 still seemed to hang Cakewalk. I left a "new project" where I had merely inserted Ultra Analog in a project with 48000 sample rate open for about 6 hours while I was out at appointments. Seemingly in a hung status. When I came back, I touched a key on my MIDI keyboard and Ultra Analog responded with what I now recognize as its default preset when you open it. I double clicked and was able to operate my way through the VST's GUI - selected new patches, edited them, etc. Then I tried closing the project and it appeared to hang. After 30 seconds or so I opened task manager, and Cakewalk was using 25GB of memory (I have 48!). I watched the memory usage slowly decline to around 370MB, I think, and then the project closed. So I tried starting a new project (sample rate of 48000) and again the memory usage slowly (about 30MB per second, I think) increased until it leveled off at 36GB. Until then, there was no sound when I hit a key on the keyboard, but at 36GB I again got sound, could change and edit presets, etc.) Here's a screenshot of task manager at the point when the VST finally worked - what in the world is going on? (By the way, I can still open a project I created January 15, before I started having these issues, with no problems and Task Manager reports about 2.4GB memory usage.) Spo

Should have left well enough alone. I tried rolling back my Focusrite drivers to the previous version. That did no good, but when I updated back to the current version, I lost Chromaphone 2 again for projects that use a 48000 sample rate. As before, a different error message altogether in the Windows error log from the one for VA-3. Thanks for pointing out the VST2 "workaround." But I wish this would work properly.

I guess I'm lucky that they work with 44.1 sample rate, that Chromaphone 2 works fine with 48000 sample rate, and that both worked at first with 48000 sample rate, and that I can still run projects that were created with 48000 and contained VA-3 back when it was not a problem. I will try excluding the VST3 and see what happens. Wondering what your audio interface is. Mine is Focusrite 2i4.

Driving me crazy: I bought AAS Ultra Analog VA-3 and Chromaphone 2 a month or two ago. I already had Ultra Analog VA-2 and the original Chromaphone. My default sampling rate for new projects is 48000. As you'll see below, I was able to use the new VSTs in projects whose sampling rate was 48000. Day before yesterday, I installed the January early access release of Cakewalk. I started a new project and when I inserted VA-3 as a new synth (with MIDI track), Cakewalk froze. I had to kill the task. Tried again. Cakewalk froze again. I thought it must be an issue with the early release, so I uninstalled Cakewalk and re-installed the December release from Bandlab Assistant. Still had the problem. After killing the task several times, I tried inserting Chromaphone 2. Project froze. So I uninstalled both VA-3 and Chromaphone 2 using Revo Pro. Re-booted and reinstalled. Still had the problem. So I opened a new project and set the sampling rate at 44.1. I was able to insert both VSTs without crashing Cakewalk. Since then, I can now use a project sampling rate of 48000 with Chromaphone 2 without crashing Cakewalk, but not VA-3. EXCEPT - I can open projects I started a few weeks ago that used 48000 with VA-3 and they open and play fine. I now have no problems with new projects if I set the project sampling rate to 44.1. Looking at Windows Application logs, the error almost always says "The program Cakewalk.exe version 25.12.0.26 stopped interacting with Windows and was closed." The "Hang type" is "Cross-thread." System has 2 Xeon processors so 24 threads altogether, if that makes any difference. However, a few of the errors are different and start with "Faulting application name: Cakewalk.exe, version: 25.12.0.26, time stamp: 0x5e02bb3f / Faulting module name: KERNELBASE.dll, version: 10.0.18362.535, time stamp: 0x50cc8d5a." None of the error messages mention the VSTs. Just to be clear, I am back to running the December release. I've run out of ideas to fix, except just to accept that my project sampling rate needs to be 44.1 if I want to use these VSTs. Any ideas?

I don't suppose there's any way to make "give all keystrokes to plug-in" the default behavior?

Ah, thanks for that! But I've been using Sonar / Cakewalk for over 15 years and have certainly saved VST sounds. How is it that I am just discovering this?

I bought AAS's Ultra Analog VA-3 yesterday. Today I edited a patch and was trying to save it using VA-3's "Save As" setting. When I tried to type a new name, any key that is mapped to a Cakewalk function (most of them!) executed that function instead of typing in VA-3's "Save Sound / Name" box. For example, if I want a "D" in my new patch name, the Cakewalk console pops up instead of entering a "D" as the first letter of the Name in the dialog box. Any ideas on how to make this work right?

Acronis for local backup, iDrive to back up files and folders. iDrive saves multiple versions of files, and I have it set to backup every night. It has saved me many times.

When I run it, I can see which version of Kontakt, and Kontakt shows up as "Kontakt," not "K -" as in the one you show. For example, here's one that shows I used Kontakt 5.

Actually, I think Projectscope will tell you what version is used in your project. See the link here in the old forum... http://forum.cakewalk.com/ProjectScope-helps-find-CWPs-and-keeps-them-organized-updated-to-Producer-Edition-m3218609.aspx?high=projectscope

The problem with Native Instruments is that each major update is a different VST, so you have to keep all versions on your system for compatibility with "old" projects (which may just be a few weeks old if a new major NI release has been installed). Keep re-installing previous versions of Kontakt until you find the one you used.

Using LX49 with no problems, other than my forgetfulness form time to time. You're following the instructions in the file Impact_LX_with_Cakewalk_Sonar.pdf file, right?

Ah, got it. Thanks again.

That fixed it. Thanks. What unexpected things might happen now that I have that box unchecked?

Is anyone using any of the Kontakt Play Series synths from NI such as "Analog Dreams?" I'm having an issue in Bandlab Cakewalk (and in SPLAT) with them. Select a patch. Create some MIDI input. Hit Play. Cakewalk plays the track one time. If you try to play it again, the track is silent, and the only way to get another "play" out of it is to select a different patch, then re-select the patch you actually want. I have to do this every single time. Do NOT have this issue in FL Studio and I haven't seen it on the NI forums, so I'm assuming it is unique to Cakelwalk / Sonar.

If you just click on the row (note name, or if you're using drum maps, drum name) that you want to change, it will select all of that entire row. You can then change the velocity on all of them at once without leaving Piano Roll.