Any chance there is documentation of what VST instrument/effect plugins are known problems in Cubase? The opposite (if available) would be perhaps even more helpful, namely a list of known good VSTs, in case a defect is discovered.
This is perhaps a problem for Steinberg to track accurately, but it would be extremely helpful to understand what VST bug(s) have been confirmed to cause issues with Cubase (or any other host, for that matter).
Info like Cubase version, VST identifier and version, nature of the failure, etc. would be extremely helpful!
Even more helpful (though perhaps too difficult) would be an underlying infrastructure that could isolate VST(s) by quarantine, rather than allow them to crash the whole application. This approach would likely introduce some additional overhead real-time constraints, but the effort could perhaps help with a more stable core product.
Probably not reasonable for Steinberg to regression test ALL VSTs, but at least a discovery list found during debugging or acceptance testing would be helpful.
the idea is charming, but you’re asking for a lot. There’s thousands of plugins to keep track of.
Plus there are just too many variables to decide blame, and then developers would be on a list, which, on the internet would essentially be a “black list” and would hurt their sales - even after they fix the problem.
There are demos for a reason though, so just try what catches your ear/eye and put it through its paces.
Nonsense!
Whenever bugs are discovered that are attributed to VST during debugging could easily be logged.
I’m not asking for a comprehensive list of every VST (and said as much). That would perhaps be “charming”, and well beyond the scope for any manufacturer.
I guess we can take your comment as a vote to not bother.
I’m not sure which part is nonsense.
There’s too many variables, what works today, might not tomorrow. Not to mention, you have a wide variable of user hardware, tweaks to their system, Windows updates turned off for too long, recent Windows updates breaking things, apple breaking things, etc.
You can already send crash logs directly to tech support via the safe boot screen.
No body wants to advertise their problems or feel like they haven’t been taken off a list fast enough, etc, etc. It would be very bad relations and business between Steinberg/VST and 3rd party developers.
The best thing a user can do, is their own research - search for other users of the plugin/brand and see what they say, ask them, and look at the company - how active are they, how often do they release updates… and demo. If a plugin doesn’t crash in 30 days after extensive use… it’s probably just as stable as any other plugin