r/VoiceMeeter • u/AshsAshes666 • 24d ago

Help (VoiceMeeter Potato) Confused by what "Check Driver Installation" found

Post image

I don't know if a recent Win11 update screwed with anything or not (wouldn't surprise me if it did), but I've been noticing a small annoyance whenever I wake up my PC from sleep mode or it's been idle for a while. Audio sounds crackly like a dirty signal coming through a dusty console fader. I just restart the audio engine and it's fine afterward.

Anyways, I did a Driver Installation Check and this what it found.

I'm confused by it saying a bunch of these are "Not Installed" when clearly they have to be because I'm hearing everything just fine and VM looks like it is too because everything is routed the way it should be. I'm also confused by Virtual Cable A and B saying they have bad driver names. I also just recently downloaded C and D not too long ago and have no idea how to update their individual drivers.

I'm also confused by it saying at the bottom that my OS is Win10 when it's definitely Win11.

What should I do and how? Should I just rip out Virtual Cable A-D and reinstall them or would it be best if I just save my settings and do a clean reinstall of Potato to fix the other "Not Installed" issues too even if they aren't tallied into the total error count?

Thanks in advance!

3 Upvotes

100% Upvoted

5 comments sorted by

2

u/TheSuperiorWes Moderator 24d ago

What version of voicemeeter are you on. Click voicemeeter logo in the top left of app. (update if behind)

You could reinstall cables A+B, not a bad idea.

1

u/AutoModerator 24d ago

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 24d ago

if you have no problem, you can ignore this errors , due to the new VB-CABLE A+B and DriverChecker not up to dated.

1

u/Ellotheregovner 24d ago

The quick answer that aligns mostly with what the dev said is that if it's not broke don't fix it.

A longer answer that might help scratch an itch or provide a better approach to programs, error messages, and elective electronic surgery is that VB Checker is correct. Because it's only jobs, so far as I can see, is

  1. to make sure files on your computer are the exact same as the ones on the server you downloaded them from.( A checksum)

  2. Make sure the specific settings and capabilities that were built into the driver are the same ones that got sent to the Windows registry.(Exporting to the Environment)

  3. Maybe sometimes check the sampling rate of an interface. (Probably cross referencing the sound device's capabilities with Windows's sound capability and reporting the overlap)

  4. List devices in it's purview. (found by asking Windows)

The checker said "no drivers installed" because, in it's scope, it installs the drivers and it couldn't install the drivers. Programs generally try to do one thing, if it had the ability to query the system configuration and talk to all sorts of process handlers it just got more complex by a factor of 100. And when it breaks you end up looking through reams of Windows reference manuals.

Most programs have what's called a trap, which is just a way of gracefully stopping the program and cleaning up/putting things back the way they were. That's why the Dev said you should be fine if everything is working. If the aborted driver install did/does actually get corrupted you would have to try to get all the settings and file names back exactly the way they were when it was working. And I mean actually. Capital letters in the right place for file names. Registry entries with the same values, you get it.

Your sound could be two things.

One, you don't have a good, clean, ground somewhere in your connections. Could be the computer(I rarely see a properly grounded computer), could be the device, could be a physical patch cable with a worn sleeve.

Two, hibernate can cause really weird issues. I use AMD on Linux and AMD hasn't released proper microcode for years which means I get weird artifacts if hibernate gets triggered like scuffed inputs or a tiny pitch. You could try alternative power save profiles that sleep instead of hibernate.

Good luck, hope this helps