So I own Cubase 10 pro and I’m testing Cubase 11 prior to buying the upgrade.
Cubase 10 worked fine with Falcon but falcon is a VST2 plugin it seems. Cubase 11 has decided that it must blacklist Falcon every time Cubase loads and that when you reactivate it and put it into a project, cubase needs to crash.
What is wrong? Why is Falcon and Cubase 11 such a bad bad idea? I can create crash dump files all day if anyone at Steinberg wants to see them.
I have had no luck. Maybe I should switch to bitwig as those guys know how to support popular VSTs, and if a vst has a bug in bitwig, it takes out one track not the whole DAW crashing.
thread title is weird. Why would there be a deep personal hatred?? A little bit sensationalist. Try, Cubase 11 and Falcon gets blacklisted / causes crash
This doesn’t really help you, but I had a similar experience with a 64bit piano (Truepiano) plugin.
I had been using this plugin with CB 6.5 64bit on a Win10 desktop PC and a laptop with absolutely no problem.
I upgraded both PC and laptop to CB 10.5. The plugin worked fine on the desktop. However, on the laptop, CB 10.5 would freeze (Cubase is not responding), requiring a forced stop.
In my case it would appear to be a conflict between CB, plugin and hardware. Despite a lot of time spent trying to resolve the issue, I never got to the bottom of it.
Yes. UVI Workstation do NOT work on CUBASE 11!!! Personally om going over to hardware again. im SOOO tired that Pugins not loger supported or dont work anymore. whit DAW updates!