It sounds like a Cubase problem then... " I haven't upgraded to 8 or even to 7.5 because of all the problems users were reporting at the time." No VST can cause a DAW to do what you described... How exactly do you think Loom managed to make Cubase start looking for dlls that weren't VSTs, and where was it looking? And as for BBFG, you are another moaner and of course you would claim the same as Wagtunes.wagtunes wrote: I'm using Cubase 7.07. I haven't upgraded to 8 or even to 7.5 because of all the problems users were reporting at the time and I had projects that I had to finish. And since my Cubase was very stable as long as I didn't use 32 bit plugs (I'm on Windows 7 64 bit) there was no point in upgrading and I won't until I absolutely have to.
To answer your other question, you can believe whatever you want. I installed AIR Loom, which I really loved the sound of not to mention how versatile it was, and after making some edit to a patch I received an error message the kind I'd never seen in Cubase. It was a big white box and something about critical error. I don't remember it exactly.
I then shut down Cubase and when I went to restart it, the thing it does upon starting, verifying VSTS, started verifying DLLs that were not VSTs and the system just went completely nuts. I could not get Cubase to start up clean after that so I had to reinstall. It was a total nightmare. I never want to go through that again.
So believe whatever you want. I really don't care.
Which commercial VSTs are causing DAWs to crash, and are never fixed?
Your problems were caused by Cubase having bugs in it, and what has Loom got to do with Falcon? Why are you even writing such nonsense on this thread? So there's no demo, and you don't like it, and then you want to spread FUD about Falcon (and Loom). Ridiculous.

