Ok thanks. I will do it.
KT66 is correct.
If you are lucky and the midiman is one of the class-compliant ones, it will work with our in-box driver.
If that doesn’t do it, then I can only suggest working around it with other devices right now. We’re investigating to see if there’s anything we can do for this old m-audio driver.
Pete
Microsoft
1 Like
Ok, I just deinstalled the driver provided by M-Audio and restarted my PC but it’s not detecting the device anymore.
Also another problem which now appeared three times since yesterday morning. I have Realphones Systemwide-driver installed to be able to frequency correct my headphones. Suddenly (probably since the Windows Update) sporadically it doesn’t load the Realphones Systemwide driver anymore (it doesn’t appear right below in the status bar). When this happens I have no system sound anymore even if it says in the system sound menu, that Realphones System-Wide is selected. I need to restart my PC to be able to get it running again. Very annoying.
Regarding Cubase. Whenever I load Cubase now, no matter if it was closing properly (with showing the Hub before) or not, it was always gives me now a Hub where I can’t see my latest project I was working on but some projects which I worded on a couple of days ago.
Cheers Paddy
Seems like it’s not class-compliant then. Always hit and miss with those.
You’ll want to reinstall the midiman driver.
I’m not sure what else is happening with the PC and your headphones. Our MIDI stack is completely separated from the audio system. It’s possible something else in the update caused issues there, but I haven’t heard anything along those lines with the recent updates.
Pete
Microsoft
1 Like