I am writing to report a critical issue I experienced during a live performance using VST Live 2.2.118.
The Problem: During the live set, all tracks suddenly went into “Mute” status automatically. I was not touching the mixer interface, nor were there any incoming MIDI messages that should have triggered this. I lost all audio completely. I managed to restore the audio only by clicking the “S” (Solo) button in the top-right corner of the Mixer.
Setup Context:
Version: 2.2.118. I have been using this specific version because it has always been perfectly stable in my previous concerts, so I avoided updating to prevent potential instabilities during live performances.
Hardware: Yamaha MODX7 (I am using only VST Live, no other software is running).
Usage: I use VST Live structured in “Parts,” loading plugins such as Kontakt and HALion Sonic within them.
Actions/Shortcuts: I have checked my “Actions and Shortcuts” configuration, and there are no mappings for Mute or Solo, so it is not a conflict with external MIDI commands.
My Observations: This is the fourth concert I have performed using this exact setup and I have never had any issues before today. Since I could restore the audio by clicking the “S” button, it seems the software entered a “Solo” or “Mute” state internally. Given that I have no external triggers, I suspect this is a bug related to the internal routing or interdependency between Tracks, Layers, and the Mixer.
My Questions to the Developers:
Has anyone else reported a similar behavior in version 2.2.118? Is there a known bug where the “Solo” or “Mute” state can be triggered automatically by internal engine processes, especially when using configurations based on Parts with plugins like Kontakt and HALion Sonic?
Is it highly recommended to update to version 2.2.120 to fix this specific Mixer behavior, or is there any known risk? I have been very cautious about updating due to the stability I experienced so far, but now I am concerned about the reliability of my next performances.
Any advice on how to troubleshoot this would be greatly appreciated.
Hi! I haven’t met with such. But what I can tell you is that you can install both versions (most recent 2.2.120) and the last one. First rename existing app file to… what it is… then install the recent one and rename that too. So you can test, torture both one by one.
That was my thought, too. One day I had some papers on my desk behind my mouse and as I pushed it forward it clicked a mousebutton … needed a few minutes to realize what happened.
I can guarantee you that no one touched the notebook as it was on the modx7 during a concert and no one touched the keyboard of the notebook, it is a new model and has never given any problems it is perfect in everything, my second job is to do technical assistance on Windows and so I know what I’m saying, its only and exclusively for the live and then put back in the bag and the keyboard is perfect, something similar had happened other times with another project a month ago if I’m not mistaken, I want to reopen the project that appeared to me to see if it will do it again, anyway thanks
I purchased and updated to version 3 vst live since in version 2 there will no longer be weekly updates and here too I have the same problem, as you can see in this video the problem persists, I would like to point out that I have not memorized mute and only in the parts it almost never sounds, but unfortunately still surprisingly I find myself with this problem as you can see in the video vstlive is not connected to any midi keyboard or other so an external command is excluded, it is isolated but when I change the parts sometimes it goes into mute, if in the future it happens in a live as it happened to me, I organized myself and solved it by associating (global part mute) so I restore the sounds with a button on my modx7 but I would like it not to happen
I just noticed that on your third part the global mute icon in the upper right corner is always active. From watching your video it‘s not quite clear what‘s causing this. Maybe it‘s got something to do with your problem. So, my question is: why is that mute button lit?
Thanks for replying, Kai. I don’t even know why it does this. What worries me is that it could happen at any time by changing the parts, and I’d like to understand why and where the problem lies. The button lit up on its own, as you can see, by simply changing the parts, with the mouse or whatever method you use to change them.
Guys, @francescomidi
Can I have this one song project to click parts on my laptop if can reproduce? @Kai_Schwirzke did u get this already, could u repro too?
Additional question @francescomidi : could you check that no SOLO/MUTE is active in TRACKS view? Last year experienced that permanently using SOLO certain tracks in TRACK view caused issues, so dropped using SOLO permanently, therefore I’m not up to date regarding, but had this idea in my mind. (of course still SOLOing sometimes but only temporary for quickly checking a track)
Hi, the computer isn’t connected to anything; I’m just using VSTs. I’d certainly be happy to share my project privately, but how do I go about it? I’m just using presets with Kontakt 8, HALion, and Nexus 5.
But if they are designed to be used muted, then why should we do without them? At this point, I think it needs to be checked by the developers. Anyway, this issue has been very unstable lately, as I said before, during a live my whole setup changed by itself.
…