Hello Friday,
we’ve just released Pre-Release 2.2.85, which includes one new feature and one important bug fix.
HUB : New “Dev Updates” secton
We’ve added a dedicated “Dev Updates” area to the HUB to improve communication between the development team and our users.
We also fixed an issue where Shared Layers were not being uploaded correctly, which could lead to significantly increased CPU load.
More here
Have a nice evening,
Michael.
Pre-Release 2.2.85 downloads 2.2.84 instead. Please upload it correctly.
… thank you. The download-links were wrong. Corrected. Refreh the page and try it again,
Thank you,
michael.
Thanks, will test out
“Dev updates” looks good.
VST Live Version 2.2.85 2025.12.5 22.1.6.563.dmp (1,8 МБ)
VST Live Version 2.2.85 2025.12.5 21.59.29.799.dmp (1,8 МБ)
Crash dumps when trying to open another project, as in this thread, haven’t been fixed yet. VST Live Pre-Release 2.2.84 is online - #5 by sergeantt67
It would be better if they wrote and made new instructions available instead of decorating the hub with pictures. It’s not like you’re decorating a Christmas tree… 
Reading the version history is enough…
I understand that if everything worked perfectly, then you could do whatever you wanted, but this looks more like an imitation of vigorous activity instead of real corrections and improvements. Forgive me for my bluntness.
You’d better look at how many open bug threads you have. Most of them aren’t even read, and there are no responses from the developer. Who are they written for? A simple example: Bug in Automation List Editor Position The thread is already two months old, not to mention it hasn’t been fixed, and no one even bothered to read or respond. Or this: Import and export of media projects and dawprojects - #11 by sergeantt67
And there are plenty of such threads. And that’s the main indicator of your work, not some useless updated hub.
Hi @sergeantt67,
thanks for taking the time to write this. I understand your frustration — especially when crashes still occur and it feels like some threads don’t get the attention they deserve. That’s definitely not the experience we want you to have.
Regarding the crash when opening another project: does it happen every time? For example, when you open Project_A first and then load Project_B? Any step or detail that helps us narrow it down is extremely valuable.
About the open or unanswered bug threads: we do follow the reports, but you’re right — we’re not always able to respond everywhere in a timely manner. We’ll try to make our communication more transparent going forward, even if we can’t reply to every single thread immediately.
Regarding the Hub update: I understand that this change may feel frustrating given the existing issues. At the same time, this improvement is an important step for making communication clearer and more structured in the long run.
Thanks again for your openness. Even if the message was tough, it helps us improve both the product and our communication.
See you,
Michael
Thank you!
That’s right, I opened an existing project, made sure multithreading was enabled in the settings, and it hadn’t been reset with the new version. I decided to check for a bug where opening Project B would disable the multithreading setting. VST Live immediately crashed (closed). It even reloaded a couple more times, but it arbitrarily disabled multithreading in the settings.
And that menu wasn’t there after loading…
Then I got tired of experimenting and went back to 2.2.80. , which doesn’t have this bug and everything works, and when switching from project A to project B, multithreading in the settings doesn’t turn off, that is, in this regard, the version works
I will jump in. Yes, almost every time it happens and there is no other step by step instruction than “1) open project_A, 2) open project_B, 3) send crash report” 
I tried many different ways and still didn’t report it because cannot catch the flow. So while devs are working on other bugs, the best way is to close VL and start it and open desired project. It takes maybe 3-5 seconds more and I’m sure, @sergeantt67, you’ll never do that on the stage, right?
I remember my rude presence in Dorico forum (version 4?) when almost a year I tried to explain one simple problem occuring while using JumpBar and devs didn’t understood me (and my poor English maybe) or were busy on other things. After a year they fixed it. It was about “Duplicate to Staff Above” (and Below). So for that year I copied staves or selected notes by hand and see - I’m still alive I’m sure the VST Live devs also will fix this unload/load bug once they had a vision where to shoot and dig.
P.S. This version 2.2.85 contains one fix - “Shared Layer not unloaded” and it was probably due to loading/unloading errors in general, because I tested my big project on both computers and they don’t crash anymore.
Keep doing!
Version 2.2.80 loads the shared layer, and multiprocessing doesn’t disable itself in the settings. It may have some minor bugs, but overall, I consider it one of the most stable versions in the last six months (but that’s just my opinion, and I’m not trying to push it on anyone). Everyone has their own criteria, but I wouldn’t even use 2.2.85 at home, let alone for concerts.
.. can you tell me what is inside those projects? Layer, Stacks? Audio, Midi and DMX-Tracks? Modules like Focus Control, VST Viewer? Video Tracks?
Thank you,
Michael.
Michael, I can just send you a private message and sign them A and B.
… that would be great, thank you.
I agree.
When does the remote by iPad feature will come?
