very much agreed: we NEED sandboxing for VST3. My last Friday was an absolute nightmare: could not get my project to open due to a single, corrupted preset in a VST3 instrument.
I swear to god, this software has given me some form of C-PTSD. It’s really hard to get myself to even want to open it sometimes as I imagine what fresh hell might be in store for me.
Steinberg had better reassess, redirect, and refocus on QUALITY above all else, or I fear this company may not finish out the decade with any stance one could interpret as competitive in the field.
AI is going to be thrashing this whole industry in very short order and yes, it is unstoppable. There will be lawsuits galore, but they will not stem the tide; they will not be able to hold off the inevitable for very long.
Steinberg better come correct and stop releasing these buggy nightmare major updates and slow down before they wound themselves in a way they can’t recover from in the face of this nascent technology.
Having a SINGLE VST3 PLUGIN making it impossible to open a project, one that is in fact critical to that project, is not OK. We need to at least be able to get back in and make sure the preset is saved properly along with the entire mixconsole channel before we reinstall it from scratch.
We absolutely need sandboxing and we absolutely need a renewed focus on stability such that certain incompetent Italian developers no longer have it in their power to prevent a Cubase project from loading entirely.
I don’t think a nationality is a race. And anyway, he’s talking about a company.
If someone called me an incompetent English musician, I’d be offended by the word “incompetent”, not “English”, and I’m a touchy fellow, as a certain topic of mine suggests.
I just purchased this VST Scanner called Bypass… it was a $5.00 program and I got .50 off, making it $4.50… This program scans my entire system and gives me a list of ALL of my VST’s, VST 2 & 3, and any other VST’s on my entire computer, in less than 3 seconds!!! Why does Cubase 14, which is much more expensive, take over 30 minutes to find them when I first launch? I have been with Cubase since version 4 but I am getting frustrated and questioning my loyalty. It is not like I have a weak PC either, so that is not the problem…I do not want to spend another month troubleshooting when I could have been making beats…
Well, because it sounds like it’s only finding them and not actually scanning them; there’s a difference, you know. One is actually prepping them for use and verifying they’re going to work OK; the other is just locating them. Am I wrong?
I think that I will have to live with this problem… nothing seems to be working… If I stop the VST2’s problem improves significantly, but I need them too. Thanks…
So, my Cubase 14 is not completing the plugin scan and is stuck at “Scanning VST 3 Plug-ins…”. It is still trying to scan as I write this.
The last entry in this vstscannermaster.log file is:
“Scanning: WaveShell1-VST3 12.7_x64 (2592/2688)”
So, how would I go about getting to the root of the problem with this Waves plugin? As I have mentioned in another thread, on my PC computer, after it has been running for a while, I get this behavior from Cubase.
If WinRT MIDI is taking a while to initialize, are you running in a Windows Insider Canary build of Windows that has the new MIDI stack in it?
I just ran across this thread because of the recent post. Leaving this note here in case it’s relevant to OP’s older post, or to folks using the new MIDI stack over the next few months as it rolls out to retail Windows 11.
The new MIDI stack initializes only when first used, and can take several seconds to spin up. This can be prevented by setting the service to auto-start with Windows. The MIDI SDK download includes a settings app which, when first run, makes it easy to set this up.
Folks can go to About Windows MIDI Services - Windows MIDI Services to learn more. Don’t download and install it right now; wait for the official non-preview release, unless you are a software developer or advanced user and have been following along on our Discord server.
I got reduce enough by deactivating two midi over bluetooth devices and it takes about thirty eight seconds to show the welcome screen. Just try this:
Studio → Studio Setup… → MIDI → Midi Port Setup then uncheck ‘Visible’ and In ‘All Midi Inputs’ every In/Out bluetooth device
Before this setting it took about one minute and twenty seconds to start :-o about 10 seconds Initializing Midi Devices 45 seconds Initializing Chord Pads. Not happy yet. It should take less than 20 seconds.