Windows 10 and MixVibes with Control Pro 2

[DJDogbone]

I have been DJing with Mixvibes for the past 2 years and I've found it to be quite good. I will say I've experiencing issues with extended periods of VJing (mixing mixing music videos) in that after a couple of hours, the system becomes unstable

Also, I started doing a podcast called The Second Wav for about 28 weeks now. It's been great for the most part. I'm running Windows 10 and I'm beginning to experience issues since the latest OS update 10/24/16. My MixVibes Control Pro 2 doesn't always connect with the software or if it does, only 1/2 of the audio mapping is there. I have to re-map it.

On top of that, I've also experienced the left side of the controller not cuing with the jog wheel. that has been an on-going problem since the change from .10 to .11

Anyone else experiencing these issues?

[Team@Mixvibes]

Up!

Out of curiosity, have you tried using the software with another MIDI controller? Also, did you update the software?

[daniel clark]

not sure whats going on with your set up,,just did a pre hurricane party warm up using the control pro2 and win ten,,thre hours non stop/ didnt have a flaw,, have you tried using another MIDI controller,,
maybe some screen shots and a little bit more details,,

[RoJeC]

Daniel: Wish you can plug in after the hurricane and continue the next party without constructing a new house to get you an outlet.

Dogbone, you may have to check if Win didn't replace drivers by 'better ones'.
For feedback purposes please be aware that audio and MIDI are totally independent and non related protocols (audio uses drivers, MIDI communicates without drivers).
Unless you have a major hardware breakdown in your controller (e.g. 'mainboard') it are different issues to resolve.

Removing the MIDI and Audio from the win hardware for the mixtrack and then reconnecting might do the job (please be a little patient as the controller is class compliant so needs some time to send the proper info to your PC). Always start Cross after the controller is hooked up AND installed/activated by the OS. Also be aware that using a different USB port results in partial reinstall of the controller, so is seen as a different device by the OS (and so by Cross)