VSTLive just crashed while I was adding new audio files to a song freezing, quiting (lost unsaveds)
I’m checking every time - when crash happens - the folder (windows C:\Users\felician\Documents\Steinberg\CrashDumps)
but it is empty, all the time empty. Facing with a few crash-quits in a week, when using app, but can’t find any generated crashdump for sending. Already clicked once Help/Clean user data. Is there a location I’m missing?
Hi @Spork, no worry I’m saving quite often! Unfortunatelly still have crashes, thankfully less and less week by week. But immediatelly after I never find any CrashDump file in location quoted above to send you for further inestigation.
So I used to send problems in the past that i could reproduce and screen record to You, as I couldn’t find CrashDumps in crash situations. And they usually didn’t happen again so I could continue setlist tasks.
If there is any workaround for crashdump generation, do not hesitate to let me know
Oh! I’m sorry also… I know, there was an answer/reply about, but search magnifyer couldn’t help me out:
how do I save default splash screen settings (I mean “splash screen” at opening VSTLive)?
You mean the Hub (with net messages at the left side)? Those are local settings, they are automatically saved when you exit, and loaded when you start over, along with Connections… etc that you did in between (local settings).
There are two types of problems, for one, crashes (bail to desktop), but also freezes (program doesn’t react anymore). Crashes should always create crashdumps, freezes cannot create them, because…well, it’s frozen. Which type is it in your case? And most of all: if you can ever reproduce a crash, please let us know.
As narrowing in my head: exiting crashes are mostly when drag’n’drop files (and app starts generating .peak files under the hood). When I’m too fast and clicking as thinking didn’t pull file to track correctly… app can crash with “hard-exit”.
Other case happened a few times, when changed font copy pasted text in “NOTES” view. Also caused “hard-exit”.
These are not reproducable right afterj. But I promise, I will write all details next time when such happens.
Nothing. Default settings when not applied (new project) are ignored, also, they try to provide ports whenever possible to ensure you have sound, midi input etc, so (nc) doesn’t apply.
If you set ports as you do in your video, and then new project and save, it will save your changes in the new project.
Put differently: hub defaults apply to “New Project” only.
to be honest, I’m not a windows guy, but using win laptop for gigs as only Asus Zenbook Duo had two screens on a laptop when purchased and I really liked the idea
I checked now with a simple “save to…” test, it seems, VSTLive has permission write data into the folder:
thank you! I’ve figured it out. Creating a “DUMMY” (virtual) MIDI port, let’s me use 2nd MIDI IN pos# “empty/un-utilised” untill I connect my HUI. This avoids VSTLive automatically load the first avaiable device in alphabet (for me: loopMIDI) to #1/#2<nc>'d MIDI-INs automatically (that duplicated the usage of my “loopMIDI” port, as it has already a MIDIIN as “loopMIDI” next row in my project file. (fortunately VSTLive is not “filling automatically up” <nc>'d OUTs).
once we will figure it out, no problem. Just as some kind of prove, I purchased the app last autumn and no crashdump was generated since (there are lot’s of things fixed now, but no doubt, inbetween there were “some” crashes while doing this and that )