(◣_◢) VST Live Crashes 💥 Every Time ! (◣_◢) *SOLVED*

Hi all,

  1. I’ve been working on a Live Show for a few weeks, and as of this morning, I’m getting constant and consistent crashes :collision:.
  2. Tested this on two separate setups and have 100% reproducable crashes: VST Live 3.0.19.124 is in my Main-Desktop (where I prepare everything)
    VST Live 3.0.30.157 is my Live-Laptop

I have a 3 setlists with 25 songs total so far (this makes up almost 2/3 of my live show) when I get to after song 20, when I add a few songs the whole VST Live project becomes unstable.

Set 1 (9 songs)
Set 2 (9 songs)
Set 3 - added about 4 songs so far

Adding songs to set 3 , have 4-5 songs there so far.

When attempting to go to a song (Ti Sou Kana) and while in TRACKS mode, the whole thing crashes :collision:.
If I’m in mixer mode I can switch songs, setlists, whatever, and it doesn’t crash at all, but if I switch to TRACKS mode and click on this song it’s GAME OVER (メ﹏メ).

But when in TRACKS mode it crashes :collision: every time when I move around song in the setlist. On both systems tested!

No Stacks, No External Plugins, No live instruments, No live inputs, no live automation, just wav file playback and two tracks of MIDI patch changes.

  1. I have removed the seemingly offending song (Ti Sou Kana) from Set 3 and the whole thing seems a lot more stable. I archive the song on Cubase after flattening all the tracks and made sure there was nothing odd about it. Reimported it to VST Live. Same Problem :collision:.

  2. Took an absolutely empty new session imported the song. Kept one empty song so I can switch back and forth. As soon as I went back to (Ti Sou Kana) in TRACKS mode WHAM :collision:BAM :collision:(Thank you Maam) :collision: Crash-ola Grande :collision:

I have uploaded the offending project file (zip) and a few crash dumps in Dropbox in case someone has any good ideas ?

I’m a bit worried :thinking: about stability.
⛐ ⛐ ⛐

FYI: VST Live 3.0.19.124 is in my Main-Desktop (where I prepare everything)
VST Live 3.0.30.157 is my Live-Laptop

Both PCs crash the exact same way! See .dmp files below from both machines!

VST Live Version 3.0.19 2026.4.24 8.46.17.642.dmp (1.2 MB)

VST Live Version 3.0.30 2026.4.24 8.13.35.463.dmp (1.0 MB)

VST Live Version 3.0.30 2026.4.23 16.25.10.978.dmp (978.3 KB)

VST Live Version 3.0.19 2026.4.24 8.57.20.404.dmp (1.0 MB)

Dropbox Link with Cubase original session and VST Live exported session:

UPDATE: I can now confirm the tempo track of (Ti Sou Kana) is at least part of the crash. It seems Cubase saves some of the tempo information even after I DELETED the tempo track and exported to VST Live. Only after rebuilding the cubase session from wav files (no tempo track, no meter track, no midi files), then exporting, does the VST live not crash when importing this.

Even importing the original tempo file (Import tracks from project) to the clean cubase session and re-exporting to VST Live, caused a crash! Woa Deleting the tempo file, and reexporting to VST live caused the crash again. It seems the Cubase session must have never ever seen this tempo track from hell. ⎛⎝( ` ᢍ ´ )⎠⎞ᵐᵘʰᵃʰᵃ

SOLVED:
I stripped everything from the Cubase Session (Ti Sou Kana) and rebuilt a whole new project using wave files and recreating the tempo from scratch. This fixed the problem.
tested on two separate computers and no crashes

I believe I used Cubase Tempo detection for this song (which sucks btw). It likely introduced some artifacts in the tempo track that I could not find. Probably hidden somewhere the cubase session as well. I suggest that if you want to avoid this, do not use Cubase tempo detection for VST live destined tracks.
It’s not a great fix but it beats a crashing VST Live session!

Hi! I’m an user only, but I’m not brave enough to open your attachments (and not suggesting to anyone else for now)


The dump files are named differently, also filesizes are generally much more smaller (few hundreeds kilobytes)

please make sure, you just attach a single dmp file itself.

Hello @YannEA,

I’ve downloaded that one. All Crash.Logs point to VST Live 3.0.19, can you please update to the latest Pre-Release and check if it still crash for you? You can download the latest installer here.

Then, can you please check if you have some more Crash-Logs in this folder?
C:\Users\YourUserName\Documents\Steinberg\CrashDumps

One more thing: Your Zip folder contains a MediaProject (from Cubase?). I can import it to the latest VST Live and run it. Should this project trigger the crash on my side as well?

See you,
Michael.

Working on project few weeks, but crashes started only this morning. So what was done to your computer this morning? Updated Windows, installed software that uses and updates Windows libraries?

I’m also only user, but have little suggestion - open your project and Save Archive to new folder and rename old folder. Test it and tell us if it crashes the same way or not.

No problem. You just made me realize I was grabbing some other sort of .dmp file !
I found the proper ones here: D:\Yanni’s Documents\Steinberg\CrashDumps

So I reuploaded the .dmp to the original post

⋆.˚✮𝕋𝕙𝕒𝕟𝕜 𝕪𝕠𝕦✮˚.⋆

Hey Arthur,

Thanks for chiming in! I had already archived the project, moved it to different computer (Live-Laptop), different OS (Win 10), latest VST Live 3.0.30.157 (my main computer has VST Live 3.0.19.124) and had already done what you suggested! I also updated the original post with some additional info and .dmp files

Crashes every time on both systems without fail. BAM

¯\_(ツ)_/¯

It’s THAT easy !

Hi Michael.

Thanks for chiming in!

This is how to reproduce the crash on my end :

I took an absolutely empty new session VST Live session and FILE > IMPORT > IMPORT MEDIA SESSION

Ti Sou ‘Kana Kai M’ Egatelipses 2 - George Dalaras-07 (archived).vlsprj

Kept one empty song (the default).
Switch to TRACKS view mode
As soon as I went back to Ti Sou Kana in TRACKS mode WHAM :collision:BAM :collision:(Thank you Maam) Crash-ola Grande. (If I’m in MIXER mode, no crash)

If I save the new project session with both songs (Empty + “Ti Sou Kana”) before the crash, the session can no longer ever be opened once closed or crashed.
VST live crashes after it loads that new .vlprj and shuts down immediately.

VST Live 3.0.19.124 is in my Main-Desktop (where I prepare everything)
VST Live 3.0.30.157 is my Live-Laptop

Both crash the exact same way! See updated .dmp files on original post from both machines!

¯\_(ツ)_/¯

SOLVED:
I stripped everything from the Cubase Session (Ti Sou Kana) and rebuilt a whole new Cubase project file using wave files and recreating the tempo from scratch. This was then exported to VST LIve and fixed the problem.

I have tested and confirmed this on two separate computers and no crashes.
(Win 11) VST Live 3.0.19.124 is in my Main-Desktop (where I prepare everything)
(win 10) VST Live 3.0.30.157 is my Live-Laptop

I believe I used Cubase Tempo detection for this song (which sucks btw). It likely introduced some artifacts (and possibly additional non tempo data) in the tempo track that I could not find. Probably tempo info is also hidden somewhere the cubase session itself for time stretching etc.
I suggest that if you want to avoid this crash, do not use Cubase tempo detection for VST live destined tracks.
It’s not a great fix but it beats a crashing VST Live session!

I exported tens of songs I’m that used cubase tempo detection to build a tempo track, no problems

… do you still have the original cubase project? That one which will crash VST Live? Can I get the *.cpr file? I only need that one.

Thank you,
Michael

Yes sir, you can find that Cubase session in the original Dropbox link in my first post.

Thank you!!!