Sound Recording Voicemeeter device not connecting after reboot
Posted: Mon Mar 26, 2018 5:29 pm
I'm a new Voicemeeter user and installed it mostly to solve a problem with Windows 7 audio that’s been bugging me for years. But I found that the same Windows problem exists with VM.
From my desktop located in my upstairs office I run streaming audio, mostly SiriusXM, from a browser. That audio is output to the Realtek speakers at the desktop and through a Bluetooth device input (that mimics headphones) attached to the home AV system downstairs. From the AV system it is sent to the rest of the house and outside to the rest of my property via a personal FM station. It all works well together.
I'm getting up in age and don't like to climb stairs any more often than I must, so I control the two outputs and the streaming browser via a remote desktop app on my smart phone. I need to be able to remotely mute the two outputs independently of each other and Voicemeeter is really nice for this because next to the small browser player window on the desktop I put a couple of macro buttons to mute hardware and virtual outputs. I have the Realtek speakers connected to the Hardware Out A1. The BT is connected to the Virtual Out by way of the Sound Control, Recording tab, Voicemeeter Output device. It all works well until I have to reboot, and this is the same problem I had before VM when I was using the Stereo Mix device on the Sound Recording tab to connect the BT device. The problem was then and is now that when I reboot if I don't remember to first disable the Stereo Mix device (then) or the VoiceMeeter Output device (now) (or if it is an unexpected reboot) I cannot make either work to the BT device after the reboot is done; hence, another reboot has to be taken after first disabling the output device. Yes, it is a Windows problem, but I thought for a while that Voicemeeter was not affected. It is.
So bottom line, if I reboot Windows 7 without first disabling Voicemeeter output on the Sound Recording tab I can't get it to work to the BT output again. It's a big pain in the butt rebooting my system because of a lot of server functions it is providing, so I don't want to do it any more than I have to.
The best solution would be a [FEATURE REQUEST!!] capability to mute hardware outputs A1 and A2 separately. But in the meantime, any ideas about how to make VM virtual sound output to function across reboots without first disabling?
Great product, BTW. The streaming stuff sounds better now than it did pre-VM. I was getting lots of clipping noise on mostly piano music before and it is now gone.
From my desktop located in my upstairs office I run streaming audio, mostly SiriusXM, from a browser. That audio is output to the Realtek speakers at the desktop and through a Bluetooth device input (that mimics headphones) attached to the home AV system downstairs. From the AV system it is sent to the rest of the house and outside to the rest of my property via a personal FM station. It all works well together.
I'm getting up in age and don't like to climb stairs any more often than I must, so I control the two outputs and the streaming browser via a remote desktop app on my smart phone. I need to be able to remotely mute the two outputs independently of each other and Voicemeeter is really nice for this because next to the small browser player window on the desktop I put a couple of macro buttons to mute hardware and virtual outputs. I have the Realtek speakers connected to the Hardware Out A1. The BT is connected to the Virtual Out by way of the Sound Control, Recording tab, Voicemeeter Output device. It all works well until I have to reboot, and this is the same problem I had before VM when I was using the Stereo Mix device on the Sound Recording tab to connect the BT device. The problem was then and is now that when I reboot if I don't remember to first disable the Stereo Mix device (then) or the VoiceMeeter Output device (now) (or if it is an unexpected reboot) I cannot make either work to the BT device after the reboot is done; hence, another reboot has to be taken after first disabling the output device. Yes, it is a Windows problem, but I thought for a while that Voicemeeter was not affected. It is.
So bottom line, if I reboot Windows 7 without first disabling Voicemeeter output on the Sound Recording tab I can't get it to work to the BT output again. It's a big pain in the butt rebooting my system because of a lot of server functions it is providing, so I don't want to do it any more than I have to.
The best solution would be a [FEATURE REQUEST!!] capability to mute hardware outputs A1 and A2 separately. But in the meantime, any ideas about how to make VM virtual sound output to function across reboots without first disabling?
Great product, BTW. The streaming stuff sounds better now than it did pre-VM. I was getting lots of clipping noise on mostly piano music before and it is now gone.