I regret to say that I’m probably going to abandon VST Live2. I gave the product a lot of chances because I like Steinberg products, being a heavy Cubase user. I never have any serious problems with Cubase. Except, for me, VST Live is unusable in a real-life stage situation. It lacks stability and reliability not to say it doesn’t works at all. I’ve bet everything on VST Live for my next show. I might not be able to do it because the software isn’t functional. I’ll have to cancel it if the next update doesn’t solve my problems. The CPU increases with every song change until it crashes. I’ve wasted an incredible amount of time and weeks just trying to troubleshoot the system, time I don’t have to practice and make my music. I spend 90% of my time trying to find twists to make the software run and to post my problems on the forum. I’ve tried several options, like splitting my project into several 10-song pieces. It doesn’t work because when I try to open a new setlist, the software closes for no reason. Sometimes I have to reboot to be able to open the software again. It’s bug after bug after bug. I don’t demand an heavy task on the software, just playing my backing tracks, sing along scrolling the lyrics while playing guitar . Nothing more. But it doesn’t work. I regret to say this is one of the worst experiences I’ve had with any software in any category. I don’t say this to troll or bash the development team, I just share frankly my experience with all the respect due to the team. The priority for a live software is stability and reliability. I feel like VST Live was developed too quickly without prioritizing stability. I don’t have the time for another solution. It’s maybe too late for my next show, which I’ll have to cancel if the next update doesn’t solve my problems. I’m extremely disappointed because I had high hopes for this very promising software. But for me it doesn’t work. Regards.
OK, apparently there are big differences between Windows and MacOS. My projects consist of 10-30 songs. I use backing tracks, a video track (4k), and 3-6 layers, all without any problems. Of course, each VST plugin has its own CPU requirements, but everything works quite well.
Hi,
unfortunately I have to agree, that VST Live is not really ready and stable. I did also my first steps with it, because of a little gig in the near future. All songs are ready in Cubase (only 5-6 midi-tracks, some chords and lyrics, that’s all) and I did an export to VST Live. That worked with the first song as expected, but the whole program acts sometimes very slow. And it crashes a lot. For example, when a project is open and I want to open another project, it crashes everytime. I had never so much crashes with software from Steinberg (and I work a lot with Cubase, Dorico, Wavelab).
As described in another thread, my second song has after the import wrong midi-notes. They are very long or are incorrect comparing to cubase. That was also when only importing the midi-file or also by drag&drop direct from cubase. Don’t know where the fault is. I tried it with the official release and also now with the last pre-release. My problems were not gone.
Just my impression, it is still not ready to trust on it for a live-show. The idea behind is great and I will definitely be a part of VST Live and I hope for big updates in the future. But for now, I have to look for another alternative, which fit my little needs for this little gig.
And one big wish for the future is the support for android-tablets or android-phones. Such like it is with other brands.
I also have to agree with you boys… I’ve been using VST Live since v1 and now v2. Many times I got frustrating with bugs and bugs… and waiting for new versions in order to get stability and reliability. It is rare as for example Cubase is a very reliable software and stable, I don’t know why a new software from Steinberg is so buggy from the beggining…
… could you please check the following folders for Crash log reports.
Win : C:\Users\YourUsername\Documents\Steinberg\CrashDumps
macOS : /Users/Your_Username/Library/Logs/Diagnos.
If you find files names with vstlive, please drop them here.
Hi,
unfortunately, there are no crash logs created. I reproduced the crash again. I loaded a project and want to open another project and than without any warning, the window is closed.
By the way, I have also the problem, that I have to move the slider of the volume at the quick controls to hear the midi-track everytime again. I saved the project with volume set to 0, but when I open the project again, the volume is set to -120 and I have to move the volume up to hear the music. Why is this not saved? Or where is the fault?
this is their mail support@mercuriall.com
this is a site Mercuriall Audio Software
They just released an update, I’ve never had any crashes from their ampbox before,
I’ll double check now, maybe VST Life somehow remembered the previous version of their program, I’ll try to delete everything and clean it out in the appdata,
I used ampbox in Cubase the other day and I didn’t have a single crash with it
I also had a massive crash yesterday. Since we have a gig this weekend, I wanted to test the setup. During a certain song (playing multiple layers), at a certain point, VST Live completely crashed. When something like that happens in live performance, it’s very embarrassing. vstlive_2025-06-10-180725_MacBook-Pro-von-Juri-434.cpu_resource.diag.zip (5,1 KB)
in short, I reinstalled vst life, deleting all the tails in AppData, I’ve been running it for half an hour now, not a single crash, the new version, although the crash file is there, but the program did not close, everything was fine
this is their mail support@mercuriall.com
this is a site Mercuriall Audio Software\
Hi,
just to be honest, since yesterday VST Life does not really crash anymore, while I worked with it. I just did a little tweak with my nivdia-card (powermizer-tool). I did it more for cubase, but perhaps it affects also VST Live in a positive way. Or it is just luck. Who knows.
But what causes still a crash without creating a crash-log is when a project is open and I want to open another project. That is still the same. And what is more annoying, that the import from cubase causes wrong midi-notes. Please look for this problem. Thanks.
