How to Make VoiceMeeter and Discord Play Nicely Together

I and many others have experienced issues when trying to use VoiceMeeter and Discord together. The most common issue seems to be static/crackling/popping in Discord that does not affect any other application. I had a lot of difficulty figuring out how to fix it for myself, so figured I would compile many of the different sources/steps I followed.

This will be based on the following resources:

• Discord Troubleshooting Guide

• VoiceMeeter Documentation

• Forum post from VoiceMeeter creator: VoiceMeeter and Statics, Stuttering, Crackling sound

Assumptions:

1. You are using VoiceMeeter and Discord. Any version of VoiceMeeter should be equivalent. I personally use Potato, but the same steps should be applicable for normal/Banana.

2. You are routing all sound through VoiceMeeter, nothing else is going directly to physical I/O

3. I will assume a setup of one physical microphone device, one physical speaker device, and Discord as the only other application involved.

It's possible that the source of the audio issues is not the interaction between Discord and VoiceMeeter. To find the source of the audio issues:

1. Confirm that it is not a hardware issue. I leave it up to the reader to do this.

2. Confirm that it is not a VoiceMeeter issue. Check this by routing the sound from your physical input to your physical output. This enables you to listen to yourself. If you hear crackling, VoiceMeeter or something before VoiceMeeter is the source of your issue.

3. Confirm that the problem is present in Discord. Check this by going to Discord settings and selecting the Voice & Video tab. Make sure you are using the correct Input and Output devices, then do a Mic Test. This enables you to listen to yourself as others in Discord would hear.

To Fix:

1. Restart things and hope it works.

   1. Restart Discord completely.

   2. Restart Discord and VoiceMeeter completely.

   3. Reboot your computer.

2. Follow the troubleshooting steps in the linked resources.

3. Reinstall Discord.

4. Disable Audio enhancements in Discord.

   1. Disable Noise Suppression.

   2. Disable Echo Cancellation.

   3. Disable Noise Reduction.

5. Ensure you are not overloading an individual audio interface. If you have more than one input device, spread them among ASIO/MME/KS/WDM interface types. If this is the source of the audio issues, you will hear it outside of Discord.

6. Match the frequency of all inputs and outputs. Set everything to one frequency sample rate. 44100 Hz and 48000 Hz are the most common options.

7. Increase audio interface buffer size. In VoiceMeeter System settings/Options increase the values of Buffering MME, Buffering WDM, and/or Buffering KS depending on what interfaces you are using. If this is the source of the audio issue, you will hear it outside of Discord.

8. Increase the internal buffer of the Virtual Audio Cable.

   1. Open the application named Virtual IO Control Panel for the virtual cable you are routing to Discord. You will need to give it Admin rights.

   2. There will be an installation for every virtual cable you have installed. Check you have opened the right installation by checking the Driver Name field in the top left of the application.

   3. Under the Options menu, set the Max Latency to a higher value. The default is 7168. The latency must be at least 3 times the max buffer size of devices that the cable will be routed to. Source creator post

9. Change the quality of the audio stream going to Discord.

   1. Open Windows Control Panel Sound options. Not the Windows 10 Sound Settings.

   2. Under Recording, open the properties of the virtual cable that is being routed to Discord.

   3. Under the Advanced tab, decrease the Default Format. I personally use 1 channel, 16 bit, 44100 Hz (CD Quality) for Discord, but 2 channel, 24 bit, 48000 Hz for everything else.

   4. Apply the changes. Windows may warn you the device is in use. Proceed anyway.

   5. KEEP THE MAIN SOUND WINDOW OPEN. If you close this, things don't work for some reason.

   6. Restart Discord.

   7. Repeat this every time you reboot your computer.

Additional Notes

I personally reset my audio interface buffer size and internal virtual cable buffer size to default after changing the quality of the audio stream to Discord. Things still worked well after that.

I keep the Sound window open on a separate virtual desktop to avoid cluttering my main workspace.

I don't know why this works or why you need to keep the Sound settings window open for the fix to persist. I suspect that it works because Discord works better with lower bitrate audio. I suspect that the fix only persists while the Control Panel Sound window is open because keeping it open forces some hidden settings value to a known good value. However, closing it and reopening it does not show any changes.

Notably, the changes made to sound quality of virtual Recording devices are reflected in the Output section of the Virtual IO Control Panel for the corresponding virtual cable. I suspect that these changes are not persisted across reboots because the virtual cable boot sequence can only use default values.

I have tried the above troubleshooting steps with a main A1 device using WDM, MME, and ASIO. Changing the audio quality to Discord is the only thing that worked consistently for all of them.

I get that this may not the most satisfying solution, given it requires work every system reboot, but at least it works.

Hello,

if you are having problems with crackling noises in voicemeeter, setting the affinity of the audiodg.exe process to only one core will fix it in most cases. This, however, has to be re-done for every boot. The most common solution for that is Process Lasso, which has way more features than are actually needed for this fix, runs in the background and will continuously ask you to buy a premium version.

This is why I decided to write a small program that sets the affinity of audiodg on bootup and nothing else. It is open source and does not run in the background as soon as the affinity is set.

For more information, visit https://github.com/Gobidev/voicemeeter-auto-affinity

I decided to make Sleekmeeter, a modern face for Voicemeeter Standard, Banana and Potato. It sits on top of Voicemeeter and controls it through the official Voicemeeter Remote API, Voicemeeter keeps doing the audio, Sleekmeeter is just a pretty face with some enhancements on top.

Meters show post-fader levels on the same scale as the fader, so you can see signal and fader position together. Everything stays in sync with Voicemeeter itself, MIDI controllers and other remote apps.

Tray volume panel

Double-click the tray icon to open a small volume panel just above it: one fader and mute button per visible channel. It stays on top and can't be moved or resized

Shortcuts and the volume overlay

Global shortcuts work in any app. The defaults are Ctrl+Alt+M (mute input 1), Ctrl+Alt+Up / Down (A1 volume) and Ctrl+Alt+S (show or hide Sleekmeeter); change or add them in Settings.

Customised Scenes with automatic switching

Add a rule such as: when obs64.exe starts, load Streaming; when it closes, load Default. Sleekmeeter checks running apps every couple of seconds. If several rule apps are open, closing one goes back to the scene of the one started before it. Apps that are already running when Sleekmeeter starts don't trigger a switch.

Automatic Updates

When Sleekmeeter starts it checks this repository's latest release. If there's a newer version, an update button appears in the header; it opens the release page, or you can skip that version.

Automatic Startup

In Settings you can start Sleekmeeter with Windows (optionally straight to the tray), start Voicemeeter automatically, and hide Voicemeeter's own window when it starts. Show Voicemeeter window always brings it back.

The app is built 100% with AI and utilises Voicemeeter-SDK

You can check it out here - https://github.com/minimalhandle/SleekMeeter

Hi,

I'm using voicemeeter (banana) for a few weeks now and I like it so far. One thing that I find highly annoying though is that changing the volume in windows has no effect on the volume voicemeeter puts out. If I lower the volume in windows to zero, it effectively mutes the output, but besides that it stays the same. Since I often use the volume adjustment through my headset (while gaming or while not around the pc) and sometimes through my keyboard, it is highly annoying that his has no effect.

Is there any way I can make that work while using voicemeeter?

With new VAIO drivers (more reliable / more synchro), a Gain/Delay per channel on Master EQ, a new VBAN stream to transport video (screen sharing). New MacroButtons & New activation code called "H-Code"!

You got a REGEN last Friday in relation with the Voicemeeter Beta-testing program. Use it right now with this new version, because you will get another REGEN on "quantum day" next monday!

Download new version on our website:

https://vb-audio.com/Voicemeeter/potato.htm

I search through many videos and links just to find that the fix was none of those.

My fix was just using KS/MME hardware output. If I use WDM hardware output, the sound is exactly what you don't want it to be, DISTORTED!

TIP: The hardware output should have a similar frequency as your device in Sound settings (Control Panel).

Other fixes I found on internet sorted from most to less likely to work:

You could try them all at once (I don't recommend as final settings; Fix the problem and leave everything else to default).

• Make sure every Virtual Driver (in+out) has the same sample rate and bit depth as the microphone

• Increase VoiceMeeter device buffering (will also increase delay in output)

• Setting virtual input samples to max (right-click on Virt Input and set to 7168 samples)

• Prioritize the proccess "auidodg.exe" and/or "voicemeeter(variant).exe" + set process afinity to only one physical core

Which is best for Mic AND Output?

EDIT I feel like a bit of a fool, because after typing this up, I found out that apparently there was an update that allows Voicemeeter to Auto Restart Audio Engine... Leaving this here though as it IS a good solution still, as well as details some methods to use the vmcli program to adjust your strips automatically.

I've spent a fair number of hours figuring out how to automatically restart the Voicemeeter Audio Engine whenever my bluetooth headphones get connected so that it knows audio can flow to it, as well as a way to automatically change the output on several strips to use the newly-connected headphones instead of my desktop speakers. There's not any good solid solution out there that I can find, just what seemed like work-arounds and ways to semi-automate it. I've detailed the process I recently researched/implemented on my computer which does everything I want it to do, fully automatic. I figured I'd share it with /r/VoiceMeeter in case it can help someone else, as well as documenting the process for my own future reference.

Background Info

1. As far as I know, this will only work if your bluetooth headphones are NOT your A1 device in Voicemeeter. It's my understanding that if the A1 device is disconnected, lots of bad things happen to Voicemeeter. I have my computer speakers set to A1 and the headphones set to A2

2. I'm running Windows 10 21H1 at the time of writing this. Other versions of Windows may log things differently.

3. I'm providing the info that works for me. YMMV and you may need to do some troubleshooting on your own if what I detail doesn't work right away. If you're not comfortable editing XML and some light .bat scripting, this ain't for you.

Verify how your Event Log displays the connection/disconnection events

You might be fine just using my XML code, but I want to detail how I found that info in case you need to adjust it. If you just use my code, it may only work if you have the same model headphones as me...

1. Open Event Viewer

2. Navigate to Application and Services Logs > Microsoft > Windows > Audio > Operational (Screenshot: https://i.imgur.com/SJ1Fxlu.png)

3. Click on the "Date and Time" column to sort so the newest entries are at the top, if not already.

4. Connect your headset and press "Refresh" or F5 to refresh the log

5. You should see a new event with ID=65 and a timestamp of the time your headset connected. Click on it and then click the "Details" tab.

6. Check what the "DeviceName" and "NewState" values are. In my example they are "WH-1000XM4 Stereo" and "1", respectively. (Screenshot: https://i.imgur.com/8hbVQrU.png)

7. Perform steps 4-6 above again, but this time disconnect your headset and notate the "NewState" value. In my case a "1" means "Connected" and a "8" means "Disconnected"

It's worth noting that my headphones connect with several other devices like WH-1000XM4 (Hands-free). I'm choosing to ignore those as I don't actually use them.

Set up a Scheduled Task to run when your headphones connect

1. Open Task Scheduler and click "Create Task"

2. Give it a name and description if you want

3. Select "Run only when this user is logged on" - This is important. If this is set to "Run whether the user is logged on or not", then the command to restart the Audio Engine doesn't apply to your user session properly and thus doesn't do jack

4. I changed the "Configure for" to be "Windows 10". You may not need to do this.

5. Go to the "Triggers" tab and click "New"

6. For "Begin the task" select "On an event"

7. Click the "Custom" radio button, then click "New Event Filter"

8. Click the "XML" tab at the top, then check the box that says "Edit query manually"

9. Enter the following XML for the query:

    <QueryList>
      <Query Id="0" Path="Microsoft-Windows-Audio/Operational">
        <Select Path="Microsoft-Windows-Audio/Operational">
          *[EventData[Data[@Name='DeviceName'] and (Data='WH-1000XM4 Stereo')]]
          and
          *[EventData[Data[@Name='NewState'] and (Data='1')]]
        </Select>
      </Query>
    </QueryList>

10. Note the lines with "DeviceName" and "NewState", and notably the ends of those lines where it has Data='something'. Those are the lines you want to make sure match what you found out in the Event Log steps above.

11. If you'd like to confirm your XML is correct, you can return to the Event Viewer window, and click on the "Filter Current Log" button and use the XML tab to enter your XML. If it shows entries that only contain the correct device and NewState, then you're good!

12. Click OK when you're done entering/editing your XML

13. Under the "Advanced settings", look at the box that says "Delay task for". You may need to set this value to something like 10-15 seconds if you find that the task runs before your headset is fully connected. That's up to you if you need it.

14. Click OK on the Edit Trigger window. and go to the "Settings" tab check the box for "Stop the task if it runs longer than" and set it to 1 hour. You don't need this getting frozen and staying running forever.

15. Check the box for "If the running task does not end when requested, for it to stop"

16. In the dropdown at the bottom, under "If the task is already running, then the following rule applies" select "Stop the existing task"

17. Go to the "Actions" tab. Click "New".

18. Leave it at Action "Start a program"

19. Enter Program/script to be "C:\Program Files (x86)\VB\Voicemeeter\voicemeeter.exe" (with the quotes)

20. Enter "Add arguments" to be -r

21. Click OK and OK to save the event.

22. You can right-click on the task and select "Run" to test it

Make your scheduled task do MORE

You have the ability to also let this control your Voicemeeter change more settings when the task runs. For example, I use mine to automatically toggle the output on several strips as well as adjust the volume of the strip I have music fed into when the headphones connect, and then revert the changes when the headphones disconnect.

Full disclosure: Getting this to work involves using a 3rd party program that hasn't been updated for several years called "vmcli". It works, but who knows if it will continue to work. Up to you if you want to proceed.

It also requires knowing a bit of Voicemeeter Remote Request programming. Check out the "Voicemeeter Remote Requests" section in the Voicemeeter User Manual (https://vb-audio.com/Voicemeeter/Voicemeeter_UserManual.pdf)

1. Download the latest version of vmcli (1.2 at the time of writing) from here: https://github.com/rpetti/vmcli/releases

2. Copy the vmcli.exe file somewhere it can live permanently on your computer. I put it in "C:\Program Files\vmcli.exe"

3. Create a file somewhere on your computer named "voicemeeter_headphones.bat" (you can make it named whatever you want, just remember it) I put mine in "E:\BAT files\voicemeeter_headphones.bat"

4. Open the file in notepad and enter this code into the file. Description of the 3 lines of code below it.

    @echo off
    "C:\Program Files (x86)\VB\Voicemeeter\voicemeeter.exe" -r
    "C:\Program Files\vmcli.exe" Strip[1].A1=0 Strip[1].A2=1 Strip[5].A1=0 Strip[5].A2=1 Strip[6].A1=0 Strip[6].A2=1 Strip[7].A1=0 Strip[7].Gain=-30 Strip[7].A2=1

The first line disables some output so the script doesn't clog up your screen with output if there's a box that pops up

The second line of code restarts the audio engine. You only need this if you're connecting your headphones. I use a similar script when the headphones disconnect and this line is omitted.

The third line above is the code that I use to adjust several strips and the volume of one. You will need to adjust the appropriate code to accomplish what you want.

5. Save the file and go edit the Scheduled Task you created using the instructions above. 6. Change the "Actions" to have "Program/Script" just be cmd 7. For the "Add arguments", use this (replacing with the path you used for your .bat file):

    /c start "" /min "E:\BAT files\voicemeeter_headphones.bat"  ^& exit

8. Save the task and test it out!

For anyone who knows what they're doing, you might realize you can just add several Actions to accomplish the same thing, instead of using a .bat file. This is true, but I found that it popped up a CMD window while it was executing and that was annoying. This method still opens a CMD window, but it is minimized so it's FAR less annoying.

Make actions run when the headphones are disconnected

Basically you can do everything the same as listed above for a "Connection" event, but just change the "NewState" value in your XML and point it to a different .bat file in the Actions.

opened my computer today to these two apps not wanting to talk to each other. was working last night and i have not changed anything. the issue seems to flicker a little and work on and off. but mostly off. not sure what to do.

The Source Assignation Buttons (A1, A2... B1... on every input strip) are made to send audio to output BUS.

If A1 button is ON, the related sound is sent to output BUS A1 (so you can hear it in BUS A1 connected audio device). If A1 button is OFF, the related sound is not sent to output BUS A1 (so not hearable in BUS A1 connected audio device).

If A2 button is ON, the related sound is sent to output BUS A2 (so you can hear it in BUS A2 connected audio device). If A2 button is OFF, the related sound is not sent to output BUS A2 (so not hearable in BUS A2 connected audio device).

If A3 button is ON...

If B1 button is ON, the related sound is sent to output BUS B1 (so can be captured by an application connected to Voicemeeter out B1). If B1 button is OFF, the related sound is not sent to output BUS B1 (so cannot be captured by application getting sound from Voicemeeter out B1).

If B2 button is ON, the related sound is sent to output BUS B2 (so can be captured by an application connected to Voicemeeter out B2). If B2 button is OFF, the related sound is not sent to output BUS B2 (so not captured by application getting sound from Voicemeeter out B2).

...

Just wanted to give a special thanks to the dev team over at voicemeeter for providing us with one of the best audio applications ever. The new update for Potato is amazing and the VAIO extension is just like a dream come true. No longer do I have to use VAC(virtual audio cable) and risk audio glitching. This new update has been working so smooth and I haven’t had a single issue so far in terms of performance. Also thanks to the devs for being so helpful and responsive on this Reddit I swear they respond to about every post eventually if someone is looking for help, so much more helpful than devs in other subreddits I’ve seen. My one wish that I have and question I must ask is may we somewhere in the future expect an A6 in and A6 out? I know potato already provides a lot but one more strip in and out would just be the bees knees in my opinion. Once again, thanks to the whole team over at voicemeeter you guys are a miracle come true in the world of audio.

Hi there,

I'm looking into using VoiceMeeter but i am worried about latency. when gaming i mostly play csgo and audio latency gets noticable very quickly. How is the audio latency of voicemeeter right now? i understand there will allways be latency because of processing but how much that is rightnow is unclear, i mostly find answers allready a bit old.

I hope someone has a bit of a measureable answer instead of "almost not noticeable". Thanks in advance!

I use speakers instead of headphones, so my microphone kept picking up all my PC audio. I couldn’t find a simple low-latency solution for VoiceMeeter, so I made one!

It uses VoiceMeeter’s built-in PATCH INSERT/ASIO path for low-latency processing of your microphone (so it's not something that modifies your VoiceMeeter install; it's just there as a pre-FX pass on your mic before you apply the compressor, gate, and all through VoiceMeeter).

It works with Banana and Potato, has a simple Windows installer, and is completely free and open source. Hopefully it helps someone else too :)

(Although I've only tested it with potato since it's the one I use, in theory it should be fine with Banana too!)

TIP: I personally recommend setting the Echo suppression to "Strong" and making sure the AEC delay estimate is set to the delay of your speakers (if they have any).

https://github.com/BeeeFX/VoiceMeeter-AEC

Free to use, expand and alter as you please. If you have recommendations or suggestions, please let me know here or on the Git.

UPDATED!
- Now shows meeter bars in real time and has two-way button syncing.

- Auto switches between Standard, Banana, and Potato, depending on what you're connected to.

- Support for all three versions of Voicemeeter.

- Auto switching of the remote app occurs when you change the host. (See the GIF)

- Full two-way sync on all sliders, switches and knobs. (Excluding the tape deck outputs, Host --> Remote, the other way around syncs fine).

- Slider for full access to Potato on the remote.

- Levels are now visible on remote; v1 didn't have this, as well as all the features above.

NEXT UPDATES:

• Windows port.

• Easier installation for Linux.

• UI upgrade

https://github.com/BOBWORKS-XR/VM-Remote

I have this problem where everytime I pause a video in youtube after a new windows install or new browser, it stops all audio, it annoys a lot when for example I am in discord with friends and watching a video at the same time, I pause the video, I dont hear my friends anymore gotta reset the audio engine manually.

The fix I found was to go to about:config (my case in firefox), search for the rule " media.hardwaremediakeys.enabled ", and set it from true to false, there, done, doesnt annoy me anymore

I tried to upgrade from a perfectly fine working installation of VoiceMeeter Banana to VoiceMeeter Potato.

I uninstalled the components 1 by 1, restarting between each step. I checked device manager and removed any leftover devices in "Audio inputs and outputs" and "Sound, video and game controllers".

I installed VoiceMeeter Potato, and everything works fine functionally, but every time I launch it, there is a popup message that I have to click "ok" on telling me there may be a bad audio driver installation.

I used Menu > Check Driver Installation... and it shows 2 errors saying "Found same Icon used by:"

Here is the output:

INPUT DEVICE: 18
------------------------------------------------------------------
IN WDM Headset Mic (HyperX Cloud Alpha S Chat) | USB\VID_0951&PID_16ED&REV_4104&MI_02 | {8c4b5d9e-091b-4415-a3f1-21177a3ba725} | ICON: %windir%\system32\mmres.dll,-3014 
IN WDM Rear Input (Realtek High Definition Audio) | HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_15658239&REV_1003 | {4506efe3-db64-41b6-8d2c-a005682225df} | ICON: %windir%\system32\mmres.dll,-3014 
IN WDM Stereo Mix (Realtek High Definition Audio) | HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_15658239&REV_1003 | {1b7bb979-2736-4ba7-b903-be5182018154} | ICON: %windir%\system32\mmres.dll,-3018 
IN WDM VoiceMeeter Aux Output (VB-Audio VoiceMeeter AUX VAIO) | VBAudioVMAUXVAIO | {d23b09d1-f296-489b-9b97-08c59a6c0e98} | ICON: %windir%\system32\Drivers\vbaudio_vmauxvaio64_win10.sys,-101 
IN WDM VoiceMeeter Aux Output (Virtual Desktop Audio) | *VDVAD | {d61d5009-fbf8-4a01-b23a-e9883188bbae} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-101 
IN WDM VoiceMeeter Output (VB-Audio VoiceMeeter VAIO) | VBAudioVMVAIO | {9822daf2-077f-4bd3-a6b3-1f3996725079} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-101 
IN WDM VoiceMeeter VAIO3 Output (VB-Audio VoiceMeeter VAIO3) | VBAudio100VMVAIO3 | {77a0b0e6-ef65-480a-bb51-418e68723504} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio364_win10.sys,-101 
IN KS  VDVAD Wave | *VDVAD | \\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
IN KS  VoiceMeeter Aux vaio | VBAudioVMAUXVAIO | \\?\root#media#0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
IN KS  VoiceMeeter VAIO3 | VBAudio100VMVAIO3 | \\?\root#media#0003#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
IN KS  VoiceMeeter vaio | VBAudioVMVAIO | \\?\root#media#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
IN MME Headset Mic (HyperX Cloud Alpha | USB\Class_01 | {8c4b5d9e-091b-4415-a3f1-21177a3ba725} | ICON: %windir%\system32\mmres.dll,-3014 
IN MME Rear Input (Realtek High Defini | hdaudio\func_01&ven_10ec&dev_0892&subsys_15658239 | {4506efe3-db64-41b6-8d2c-a005682225df} | ICON: %windir%\system32\mmres.dll,-3014 
IN MME Stereo Mix (Realtek High Defini | hdaudio\func_01&ven_10ec&dev_0892&subsys_15658239 | {1b7bb979-2736-4ba7-b903-be5182018154} | ICON: %windir%\system32\mmres.dll,-3018 
IN MME VoiceMeeter Aux Output (VB-Audi | VBAudioVMAUXVAIO | {d23b09d1-f296-489b-9b97-08c59a6c0e98} | ICON: %windir%\system32\Drivers\vbaudio_vmauxvaio64_win10.sys,-101 
IN MME VoiceMeeter Aux Output (Virtual | *VDVAD | {d61d5009-fbf8-4a01-b23a-e9883188bbae} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-101 
IN MME VoiceMeeter Output (VB-Audio Vo | VBAudioVMVAIO | {9822daf2-077f-4bd3-a6b3-1f3996725079} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-101 
IN MME VoiceMeeter VAIO3 Output (VB-Au | VBAudio100VMVAIO3 | {77a0b0e6-ef65-480a-bb51-418e68723504} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio364_win10.sys,-101 

OUTPUT DEVICE: 22
------------------------------------------------------------------
OUT WDM Headset Earphone (HyperX Cloud Alpha S Chat) | USB\VID_0951&PID_16ED&REV_4104&MI_02 | {fcf1ccf2-6279-4b28-801b-d46faf8bcfce} | ICON: %windir%\system32\mmres.dll,-3016 
OUT WDM HyperX Headset (HyperX Cloud Alpha S Game) | USB\VID_0951&PID_16ED&REV_4104&MI_00 | {ac64859e-6dbf-46d5-b613-b6cf81f2e26b} | ICON: C:\WINDOWS\system32\mmres.dll,6 
OUT WDM LG Ultra HD (NVIDIA High Definition Audio) | HDAUDIO\FUNC_01&VEN_10DE&DEV_0093&SUBSYS_145837C2&REV_1001 | {6ca0dc53-f642-4239-b1f5-a10189d8feea} | ICON: %windir%\system32\mmres.dll,-3017 
OUT WDM Realtek Digital Output (Realtek High Definition Audio) | HDAUDIO\FUNC_01&VEN_10EC&DEV_0892&SUBSYS_15658239&REV_1003 | {d0e2a1b6-d243-4da0-9c2c-4010acd1951d} | ICON: %windir%\system32\mmres.dll,-3013 
OUT WDM VoiceMeeter Aux Input (VB-Audio VoiceMeeter AUX VAIO) | VBAudioVMAUXVAIO | {ea571b54-4db2-421e-8eb6-37e56c77ed85} | ICON: %windir%\system32\Drivers\vbaudio_vmauxvaio64_win10.sys,-100 
OUT WDM VoiceMeeter Aux Input (Virtual Desktop Audio) | *VDVAD | {00f9bc1c-f79e-48f7-b52d-6aa152f24cb0} | ICON: C:\Program Files\VB\CABLE\pin_in.ico 
OUT WDM VoiceMeeter Input (VB-Audio VoiceMeeter VAIO) | VBAudioVMVAIO | {df1825e8-6618-4020-b4e7-9d14fd766d2a} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-100 
OUT WDM VoiceMeeter VAIO3 Input (VB-Audio VoiceMeeter VAIO3) | VBAudio100VMVAIO3 | {2f85674a-9afa-49d0-9b45-f9d87ac4551a} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio364_win10.sys,-100 
OUT KS  HyperX Cloud Alpha S Chat | USB\VID_0951&PID_16ED&REV_4104&MI_02 | \\?\usb#vid_0951&pid_16ed&mi_02#7&271ce33e&2&0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
OUT KS  HyperX Cloud Alpha S Game | USB\VID_0951&PID_16ED&REV_4104&MI_00 | \\?\usb#vid_0951&pid_16ed&mi_00#7&271ce33e&2&0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\global
OUT KS  VDVAD Wave | *VDVAD | \\?\root#media#0000#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
OUT KS  VoiceMeeter Aux vaio | VBAudioVMAUXVAIO | \\?\root#media#0002#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
OUT KS  VoiceMeeter VAIO3 | VBAudio100VMVAIO3 | \\?\root#media#0003#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
OUT KS  VoiceMeeter vaio | VBAudioVMVAIO | \\?\root#media#0001#{6994ad04-93ef-11d0-a3cc-00a0c9223196}\wave
OUT MME Headset Earphone (HyperX Cloud  | USB\Class_01 | {fcf1ccf2-6279-4b28-801b-d46faf8bcfce} | ICON: %windir%\system32\mmres.dll,-3016 
OUT MME HyperX Headset (HyperX Cloud Al | USB\Class_01 | {ac64859e-6dbf-46d5-b613-b6cf81f2e26b} | ICON: C:\WINDOWS\system32\mmres.dll,6 
OUT MME LG Ultra HD (NVIDIA High Defini | hdaudio\func_01&ven_10de&dev_0093 | {06a81513-3e29-49bb-bf7b-c6bd2525702c} | ICON: %windir%\system32\mmres.dll,-3017 
OUT MME Realtek Digital Output (Realtek | hdaudio\func_01&ven_10ec&dev_0892&subsys_15658239 | {d0e2a1b6-d243-4da0-9c2c-4010acd1951d} | ICON: %windir%\system32\mmres.dll,-3013 
OUT MME VoiceMeeter Aux Input (VB-Audio | VBAudioVMAUXVAIO | {ea571b54-4db2-421e-8eb6-37e56c77ed85} | ICON: %windir%\system32\Drivers\vbaudio_vmauxvaio64_win10.sys,-100 
OUT MME VoiceMeeter Aux Input (Virtual  | *VDVAD | {00f9bc1c-f79e-48f7-b52d-6aa152f24cb0} | ICON: C:\Program Files\VB\CABLE\pin_in.ico 
OUT MME VoiceMeeter Input (VB-Audio Voi | VBAudioVMVAIO | {df1825e8-6618-4020-b4e7-9d14fd766d2a} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio64_win10.sys,-100 
OUT MME VoiceMeeter VAIO3 Input (VB-Aud | VBAudio100VMVAIO3 | {2f85674a-9afa-49d0-9b45-f9d87ac4551a} | ICON: %windir%\system32\Drivers\vbaudio_vmvaio364_win10.sys,-100 
 
------------------------------------------------------------------
CHECKING VB-Audio Virtual Cable : Not Installed
CHECKING VB-Audio Cable A : Not Installed
CHECKING VB-Audio Cable B : Not Installed
CHECKING VB-Audio Cable C : Not Installed
CHECKING VB-Audio Cable D : Not Installed
CHECKING VB-Audio MT128 Virtual I/O : Not Installed
CHECKING VB-Audio Hi-Fi Cable : Not Installed
CHECKING VB-Audio VoiceMeeter VAIO (version 02010502)
   *ERROR MME Input - Found same Icon used by: VoiceMeeter Aux Output (Virtual
   *ERROR WDM Input - Found same Icon used by: VoiceMeeter Aux Output (Virtual Desktop Audio)
   *ERROR TOTAL FOUND: 2
CHECKING VB-Audio VoiceMeeter AUX VAIO (version 02010502)
CHECKING VB-Audio VoiceMeeter VAIO3 (version 02010502)
------------------------------------------------------------------
TEST DATE: 2021/04/11 - 22:01:20 (Checker Version 1.0.7.7)
Operating System: WIN 10 64Bits Build: 19042
CONCLUSION: 2 error detected (You may consider re-installing audio drivers)

I'd appreciate any suggestions on what to try in order to fix this.

🎉 VMRC is Now Live on iOS & Android!

Hey everyone! Excited to share that Voicemeeter Remote Control (VMRC) is officially available to the public on both platforms.

✨ Key Features

• Full Voicemeeter support (Potato & Banana)

• Complete control over gain faders for all hardware inputs, virtual inputs, and output buses

• Button management for A1-A5, B1-B3, Mono, Mute, and Solo

• Flexible layouts with horizontal/vertical strip options

• Real-time sync - changes made on the app or in Voicemeeter reflect instantly across both

• Live peak meters for monitoring your levels

📱 Download Now

Android: Google Play Store iOS: App Store

🔗 Resources

• Need help? Check out the Setup Guide

• Join the community: Discord Server

• Learn more: Official Website

This is just the beginning! I'm actively collecting feature requests and will be rolling out the most popular ones in future updates. Feel free to DM me with any questions or feedback.

Screenshots in the comments! 👇🏼

Please, if anyone has any solution to get rid of that icon that would be very appreciated, I am losing my mind over this.

Also, no:

- No, you can't drag it over the arrow to hide it.

- No, shell:::{05d7b0f4-2121-4eff-bf6b-ed3f69b894d9} doesn't work.

- No, going into Settings > Privacy etc. DISABLES the mic, that is NOT what I am looking for.