I got told the usual "unplug" "reinstall" 3 times, like I'm green to all this stuff. (ozone keyboard ones that come with free bit crushing effect, even if you don't want it ) they were told and the exact issue, but even the new version 3 months to late doesn't fix the exact same issue. they simply don't write drivers for win 7 that actually work. Problem is a lot of people don't have time to read the instructions and then wonder why it doesn't work. Just follow the instructions and it works fine. M-Audio's MIDISPORT drivers are a clusterf**k. I'm not having any problems and I'm glad to hear your success Hawky, I'm just adding this information so when somebody does a search on this topic they'll find this too. So, if I have one midisport connected, no problems whatsoever. One day I needed to reboot and I again forgot to disconnect the midisport (Remember I only had the one connected this time) but this time it wasn't till I was about to start Sonar that I suddenly remembered that I forgot to disconnect the midisport before the POST, but no BSOD and Sonar started just fine and the midisport worked just fine. I disconnected them again and restarted and, again, after the system came back up and after I reconnected them and opened Sonar all was fine.Īs I wasn't using the 2nd midisport, I didn't reconnect it. Of course one day I forgot to disconnect the midisports when I rebooted and got the BSOD again. I reconnected the midisports and started Sonar. So I loaded the next driver, rebooted but before the system went through the POST I disconnected the midiports. I reconnected the midisports and started up Sonar. The system came back up and offered to search for a reason why it blue sreened but it couldn't find anything. So I shut down, disconnected the mididsports and restarted. As I had just installed the mididsport drivers and I was loading a driver, rebooting, load the next driver, reboot, (Yeah, I've been around the block before :-)) it was pretty easy to know what had caused the Blue Screen. They worked with no problem.untill I rebooted and recieved the BSOD. Last October I installed Windows 7 64 bit and I own 2 midisport 2x2 so I loaded the 64 bit drivers. I realize I'm late to the party but I wanted to say something to share information. I reset the machine several times and it worked everytime. So, the M-Audio driver is NOT needed to make this work on my WINDOW 7-64 bit machine Start SONAR X1 and it should now show up in Preferences dialog box Windows 7 will find it's own driver and load this to start workingĥ. Navigate to the UNINSTALL driver window and run this to remove existing driverĤ. With the Device plugged into the USB port bring up the latest M-Audio driver file 6_1_2 and click on itĢ. In this video, we dive into how to fix pesky audio signal and playback issues when recording & mixing with your M-Track Duo or Solo audio interface! Learn what to do if your computer isn’t recognizing your interface, if it’s behaving erratically, or if you’re not hearing any sound from your interface.FINALLY, the Midisport 2x2 ANNIVERSARY Edition works everytime on my Windows 7-64 bit machine.ġ. Modified on: Tue, 22 Mar, 2022 at 1:28 PM Solution home M-Audio Support M-Audio | Audio and MIDI Interfaces M-Audio | Troubleshooting Audio Signal & Playback With Your Audio Interface
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |