Hi everyone, new one here to report a very strange bug happening with voicemeeter potato - a bit linked to that one : viewtopic.php?p=5356&sid=92da15bde184fb ... 11f5#p5356
But with some specifities :
I have a usb sharing hub, plugged in two computers with 4 devices plugged on it : mouse / keyboard / logitech camera (mic + cam) / work headset (speaker + mic)
It seems that voicemeeter locks my camera (the video part) although I don't have it registered anywhere as an input or output device. I don't even have any device from this hub registered on voicemeeter. I use my Rode microphone which is plugged with a Komplete audio soundcard.
The interesting part is : If I plug my camera directly on my computer, bypassing the usb hub, voicemeeter and the camera can work together, the video part is now accessible. If i shutdown voicemeeter, the camera works too through the hub or not.
Any idea how I could solve this issue ?
Thanks !
(I also posted the message on discord, waiting for this forum validation, sorry for the doublon)
Weird locking camera problem with Voicemeeter potato
-
- Site Admin
- Posts: 2133
- Joined: Sun Jan 17, 2010 12:01 pm
Re: Weird locking camera problem with Voicemeeter potato
Maybe the problem is more on the USB stack (the link with Voicemeeter is that it is using other USB devices, possibly in conflict at O/S level).
i see no other explanation for the moment.
i see no other explanation for the moment.
Re: Weird locking camera problem with Voicemeeter potato
That was the right answer, good job to you ! The right clue at the right time 
All my devices (external soundcard included) are plugged through a PCI USB extension. In some way, the whole extension was locked by Voicemeeter. I moved the external soundcard on a free usb port I have directly on my motherboard, and the problem is gone.
All my devices (external soundcard included) are plugged through a PCI USB extension. In some way, the whole extension was locked by Voicemeeter. I moved the external soundcard on a free usb port I have directly on my motherboard, and the problem is gone.