Driver Problem

[Blackbrook]

That's... not really good idea.

Just one between a lot of others

[Support@MixVibes]

I have encountered strange ASIO driver problem with using U-Mix Control Pro. If I select MixVibes ASIO Driver, I see "Please plug in and power on the U-Mix Control Pro soundcard. Waiting..." And that's all, Cross not detecting the U-Mix is connected. I've Tried other version, and here results:
1.6.0 - 1.7.1 = NOT WORKING
1.5.0 and less = Working
I have tried everything! But... That's not helped much. BUT! In ASIO4ALL it's working PERFECT! So... If there any thoughts about that?

OK, I will explain a few things :
- 1.5 could open an asio drivers even if the device wasn't available, this could lead to weird behavior.
- on higher version, we are now checking that something is answering behind the asio.
- the U-Mix Control Pro asio drivers (and sound panel) are looking for a very precise device but by its name (not its ID), so if you're OS can't display the name of the device properly, then the asio drivers/panel won't see the device.
- asio4all doesn't care about who is what and just start to work

Can you please check these ?

umcp_device.JPG

UMCPx64.JPG

UMCP_ID.JPG

[mashuper]

Can you please check these ?

Here you go!


Don't see any problems there

[Support@MixVibes]

If the volume panel of the U-Mix Control Pro doesn't work, this means that there is no access to the audio part by the wished way and something is hacking/blocking the communication to and from the device.
[PC] [WIN XP, VISTA, SEVEN] U-Mix Control Pro 1.0.3 Volume Panel

EDIT :
I see some candidates to what I just said :
- AMD high definition is the HDMI audio output : a user have issue with this an Vfx
- HP webcam splitter : some webcam drivers are trying to use the audio usb as something exclusive.
- virtual audio cable : an other way of hacking communication between drivers and devices

Some can be just de-activated, other need to be uninstalled with their oem drivers because they are messing with the native system behavior.

[mashuper]

If the volume panel of the U-Mix Control Pro doesn't work, this means that there is no access to the audio part by the wished way and something is hacking/blocking the communication to and from the device.
[PC] [WIN XP, VISTA, SEVEN] U-Mix Control Pro 1.0.3 Volume Panel

I have already installed, and reinstalled, and uninstalled EVERYTHING! And there's nothing that blocking my device. I don't really know why this is happening

[Hannes]

Have you checked the Audio as support showed in the pictures?

[mashuper]

Have you checked the Audio as support showed in the pictures?

Yes, and it's ok.

EDIT :
I see some candidates to what I just said :
- AMD high definition is the HDMI audio output : a user have issue with this an Vfx
- HP webcam splitter : some webcam drivers are trying to use the audio usb as something exclusive.
- virtual audio cable : an other way of hacking communication between drivers and devices

Some can be just de-activated, other need to be uninstalled with their oem drivers because they are messing with the native system behavior.

And no. Have just uninstalled all of them and reboot. Results are same. I'm gonna go to friend to try my controller on his PC, maybe it's just system freaking out

[Support@MixVibes]

I have already installed, and reinstalled, and uninstalled EVERYTHING! And there's nothing that blocking my device. I don't really know why this is happening

Yes but you didn't answer : does the audio panel have effect or does it stay dimmed 'Device unplugged' ?

[mashuper]

I have already installed, and reinstalled, and uninstalled EVERYTHING! And there's nothing that blocking my device. I don't really know why this is happening

Yes but you didn't answer : does the audio panel have effect or does it stay dimmed 'Device unplugged' ?

Still dimmed. Just have returned from my friend. And now I can really say that the problem in controller. Because I had same problem at his place

[Support@MixVibes]

Not so shure because it work with asio4all, if it was a hardware issue, it wouldn't work at all.
For me it is a compatibility issue between your system and our drivers.