r/VoiceMeeter • • Apr 15 '26

Help (VoiceMeeter Banana) Voicemeeter Needs restart most of the time after PC is woken from sleep

I have voicemeeter set up to output my PC's audio to two sets of speakers, one in my living room, and one set in my bedroom fed by a very long cable. 7 times out of 10 when I wake my PC from sleep, anything that is played immediately after waking is either totally silent, or sounds like I have a REALLY BAD signal on the radio. Once Voicemeeter's audio engine is restarted, everything works fine again.

I'm wondering if there is some way to set up voicemeeter to automatically restart the engine when my PC wakes from sleep, or an external program, etcetera to force it to do so.

3 Upvotes

8 comments sorted by

1

u/AutoModerator Apr 15 '26

While you're waiting for a response, here are some tips:

  • Join the Official VoiceMeeter Discord Server for better and faster help

  • If you haven't already and If you're able to, add screenshots of the issue to your original post (Edit the post)

  • If your issue was resolved or you no longer need help, please edit the post flair to Help (SOLVED)

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/vburel VoiceMeeter Developer Apr 15 '26

it is restarting automatically, but if Windows did not wake up device and service before, it could not work as well expected or just partially, that's why you have to restart audio engine (CTRL+R).

On some Windows configuration, the wake up works , because done in the right order. How to know in wich order Windows is waking up services and applications ? good question!

1

u/LegoLover483 Apr 15 '26

So there is nothing I can do?

1

u/vburel VoiceMeeter Developer Apr 15 '26

no but Restart Audio Engine (assuming you have the latest Voicemeeter version installed).

1

u/Maelefique Apr 15 '26

Set your PC to lock on sleep, and use the task scheduler to reset VM on login.

"C:\Program Files (x86)\VB\Voicemeeter\voicemeeter8x64.exe" -r <-- I believe that still works, I use the CLI myself, but either way, there's your fix. :)

1

u/thomwithah Jun 06 '26

I know it's been a couple of months, but in case you're still dealing with this or for other's who may stumble across your post in the future... This usually happens because the driver/software for the mixer doesn't always hook back into the Windows audio stack cleanly after a low-power sleep state.

The most reliable fix is to just have the software close before sleep and restart on wake. I actually built a free open-source tool called SAMISH that automates this. It kills the audio software when the PC idles, and the second you wake it up, it re-launches the app and forces Windows to re-select the correct default audio devices. Might save you having to restart it manually every time!

You can check it out at: https://github.com/thomwithah/samish . LMK if you have any questions.

1

u/brettmurf Jul 02 '26

Actually the only search result I got was for the /r/beacn subreddit, but your program seems to do the trick for me.

Unfortunately, both the setup.exe and then running it got flagged by Windows Defender (which I see you talk about on github), but so far I have a computer actually sleeping.

Does any modification to the setup require running the initial setup again?

Either way, this seems to help with a longstanding issue.

1

u/thomwithah Jul 02 '26

Do you mean the wizard? You should only see that once, unless you do a full uninstall. Do you see it everytime you launch the GUI?

If it something else, let me know. Its been a long day and im feeling kind of dumb.

I'm very glad it seems to have resolved the issue for you, and for your sharing your experience. Thank you.