Unfortunately the random crash at startup from 2.0.24 (fixed in 2.0.26) is back.
Same behavior as in 2.0.24 - VST Live 2 will crash at a random point in its startup sequence, sometimes very early, sometimes while pre-loading parts (at different songs/parts), process cannot be killed and takes a couple of minutes to disappear from task manager. If it manages to start, all works fine.
I am getting something similar. I have reverted to 2.20 due to various stability issues I have been having but even at this version it regularly crashes when trying to load project. It will do this many times but if I keep trying it will eventually load the project ok. It is very strange and try as I might I have not been able to fathom what is different when it does work.
⌠weâve analysed it. @ChKK, can you please disable Multi-Processing? Thatâs the root of your crashes.
⌠@mike_dowey, can you please also disable Multi-Processing.
I needed three start attempts with crashes to get VST Live (2.0.28) up and running. Once started, I disabled multi-processing, saved the project and then was able to start VST Live without any problems 4 times in a row.
Then restarted my PC, tried another start of VST Live from scratch, all fine.
ok 28 seems the solve the project load crash but I have the audio drop out issue again. A few seconds into the beginning of a song there will be a short drop out on the backing track. If I stop and restart the song it doesnât happen the second time through. Do you want me to open a new thread with this?
sometimes same issue.
I doubt it may be caused by
invalid window positions of various components in a multi monitor environment.
It happend all the time after editing on other screen than the âperformanceâ touch screens (3 monitors in use, 2 touch, main screen is not touch and on other GPU)
When I open a project the application crashes. the rpoject is âlostâ, you need to go back to app-backups, pick an older version, then it works.
This happened so far with 2 projects, both with different program versions (last one with 2.0.28, the older I think with 0.22).
it happens (my suspition) after I moved windows around between (3) monitors. and - I think - when I switched on other monitors as well while VST_Live was open. So it might lead to âillegalâ window positions when the project is restarted with other monitor setup. I observe âwindow - relocationâ with other app (MSFS2020) as well when the window spreads on more than one monitor. Looks like an OS issue.
I am not tuning my PC (Intel 14700) regarding kernel usage.
Could you pls send us such a âlostâ project file, just the .vlprj file, nothing else needed, then we can eventually check what went wrong.
Itâs not an OS issue per se. But while VST Live (or any other app) should be able to handle this correctly, it has been known to be prone to errors. But of course weâll check.
Mozart KV544.vlprj (1,4 MB)
here the âlostâ project.
crashes at the end of loading. (I steped back using a working backup and set up a new project, with same instruments)
Instruments: Arturia B3V2, Arturia Mini V4, Groove Agent.
Path to pdf used in viewer: âN:\fertigePDF\Mozart Kirchensonate F KV 244 mini 1-7.pdfâ Mozart Kirchensonate F KV 244 mini 1-7.pdf (3,2 MB)
Thanks for interest.
If the file is damaged, we cannot do anything obviously.
Your project loads fine here, canât find anything wrong. It might be due to plugins, but those are all known to work fine so far. Donât know how to reproduceâŚ
Do you have a system with just one monitor, or can you disable multiple to test?
Also, here is your project just loaded and then saved here, can you open that one? Mozart KV544_resaved.vlprj (1.4 MB)
I just installed 2.0.30.175. Started fine (with multi-processing still disabled).
Reenabled multi-processing and tried to restart VST Live.
I was happy to see that the first restart worked fine and was slightly optimistic that the bug was now fixed.
I quit VST Live, waited a moment for the process to disappear and tried another restart. This time, VST LIVE crashed, unfortunately. Same for the next two attempts.
Once I was able to start VST Live, I disabled multi-processing again. All subsequent starts were fine.
Would you like a copy of one or two of the crash dumps?
I tried it with your resaved version,
on one monitor - crash
without Midi interface âiConnectivity mioXLâ - Project STARTS, NO CRASH. all prior window positions ok⌠I get a notifiction (3 times) that âdevice RME ARC is used by othe applicationâ, but after confirming with ok all is fine. (I have no midi connected via RME interface, just audio)
here the link to sellers description to midi interface (Thomann) iConnectivity mioXL â Thomann Ăsterreich
not so much a niche product, Thomann lists it as âTop Sellerâ
the device has the function to create âvirtualâ midi ports for both 5pin and USB (kind of midi & USB hub with renaming, the assigned names appear in Cubase/VstLive as midi devices).
Sorry for wrong âerror reasonâ.
All projects normally start correctly with this midi interface. I did not any renaming of virtual ports ⌠hmm⌠maybe the following - I will test:
Starting a project VST Live with midi interface âSwitched offâ. and then somehow restarting the midi interface while Live project is open ⌠I will do some tests later the week.
if you are interested to learn more on this midi interface we can do a video chat.
Thanks again!
best regards Christian
That will not work, VST Live does not rescan MIDI yet.
So you can load your project with device off. The message about âused by other applicationâ seems more concerning. Even if you donât use RME MIDI, it registers its MIDI ports.
In âDevices/Connections/MIDIâ, are there any obstacles in the devices listed when you click in the rightmost column? Like ports of different devices (RME, mio) have the same name?