Pinpointing the windows default midi driver
Pinpointing the windows default midi driver Posted on: 15.03.2010 by Rex Cirne Hi guys, so I've been suffering the wonders of driver related problems with the VCI-100 on a Windows Vista machine that I'm yet to solve. It essentially boils down to windows being unable to identify that the device needs to talk with the generic plug and play drivers (which is my understanding anyway...) and instead is looking for some kind of custom driver install package that isn't there. People have concluded this problem coming from things like weird filtering by Logitech Webcam drivers and a host of other mess.Now what I was hoping this fine community could help me with is for those of you who have got a VCI-100 and are using it with a Windows based machine if you could tell me what the name (and hopefully) the location of the driver that it's using is. The hope being that I can then point my VCI-100 at that driver manually and all will be well (key word hope). So if you have a working VCI-100 on a windows machine, what is the driver it's using? You'll need to navigate to device manager (via control panel) and find the VCI-100 in there. It should have mention of what driver it's associated with. Could you note for me what that is, and what Windows OS your using (XP, Vista, 32/64bit etc.). Thanks a million to everyone who can help. I've been looking at my shiny non working VCI for far too long | |
Rex Cirne 15.03.2010 | Hi guys, so I've been suffering the wonders of driver related problems with the VCI-100 on a Windows Vista machine that I'm yet to solve. It essentially boils down to windows being unable to identify that the device needs to talk with the generic plug and play drivers (which is my understanding anyway...) and instead is looking for some kind of custom driver install package that isn't there. People have concluded this problem coming from things like weird filtering by Logitech Webcam drivers and a host of other mess. Now what I was hoping this fine community could help me with is for those of you who have got a VCI-100 and are using it with a Windows based machine if you could tell me what the name (and hopefully) the location of the driver that it's using is. The hope being that I can then point my VCI-100 at that driver manually and all will be well (key word hope). So if you have a working VCI-100 on a windows machine, what is the driver it's using? You'll need to navigate to device manager (via control panel) and find the VCI-100 in there. It should have mention of what driver it's associated with. Could you note for me what that is, and what Windows OS your using (XP, Vista, 32/64bit etc.). Thanks a million to everyone who can help. I've been looking at my shiny non working VCI for far too long |
Rex Cirne 19.03.2010 | Seriously anyone? There are how many users on this community using a VCI-100 on a Windows machine? This would really help me try to fix this problem i've been sitting on for about a month, it will only take two seconds. |
Rex Cirne 15.03.2010 | Thanks for your reply. Specifically what do you see in device manager though (perhaps even a screen shot)? Because through the convoluted menu system I will need to point the device at a specific driver. I.e. "Universal Serial Bus controllers > Digidesign > Digidesign Mbox 2 Firmware (updater version 8.0.1.510)" Or "Sound, video and game controllers > Microsoft > High Definition Audio Device" So I need to know it by name as far as device manager hierarchy is concerned. The file location is unfortunately seemingly not helpful (as simply auto pointing the wizard at that directory doesn't help due to whatever driver conflict I have. Even if it's staring at the exact folder where usbaudio.sys is it doesn't know that it's looking for it). |
robert chanda 15.03.2010 | Windows MIDI support is embedded in the standard audio drivers (a layout which comes from the USB specifications) so "usbaudio.sys" is the generic class driver for USB Audi devices, and included inside that class are the USB-MIDI devices. |
<< Back to DJ TechTools' VCI-100 FAQReply