Midisport 2x2 Anniversary Edition SOLVED!!!

Page: < 12 Showing page 2 of 2
Author
wormser
Max Output Level: -71 dBFS
  • Total Posts : 984
  • Joined: 2007/11/18 11:26:55
  • Status: offline
Re:Midisport 2x2 Anniversary Edition 2011/03/07 12:50:10 (permalink)
Glad you got it fixed!

Like I said, the M-audio driver is a mess.

FWIW I don't think the original Midisport is supported naively under Windows 7 64 although with all the patches and SP1 that might not be the case anymore.

Thanks for posting the fix!

Windows 8 x64
Intel i7 950 3.06ghz 6 GB DDR3 1333(1066) OCZ memory
Gigabyte X58A-UD3R v.2.0
Delta 66.
Seagate 1.0tb drives x4 OS, Audio, VST, Backup Stuff. 
Mackie MCU Pro Latest.
Faderport.
Sonar X2, PreSonus 2.x, Reaper.
 
#31
stratman70
Max Output Level: -45 dBFS
  • Total Posts : 3044
  • Joined: 2006/09/12 20:34:12
  • Location: Earth
  • Status: offline
Re:Midisport 2x2 Anniversary Edition 2011/03/07 21:31:31 (permalink)
Hawky


SOLVED!

FINALLY, the Midisport 2x2 ANNIVERSARY Edition works everytime on my Windows 7-64 bit machine.

1. With the Device plugged into the USB port bring up the latest M-Audio driver file 6_1_2 and click on it

2. Navigate to the UNINSTALL driver window and run this to remove existing driver

3. Remove the USB cable and plug back in

4. Windows 7 will find it's own driver and load this to start working

5. Start SONAR X1 and it should now show up in Preferences dialog box

So, the M-Audio driver is NOT needed to make this work on my WINDOW 7-64 bit machine

I reset the machine several times and it worked everytime.  Also, the Merge button is pressed in. 

I hope this helps ...

Hawky

Amazing Hawky-Obviously the instructions mean absolutely nothing-That's refreshing-Cool. Had to try three times but got it.
Thanks -I am not going to ask what made you pick those specific steps, because "who cares :-)
Great job man-Made my night.
Thanks
Frank (Stratman)

 
 
#32
RageoPari
Max Output Level: -88 dBFS
  • Total Posts : 139
  • Joined: 2003/12/10 21:22:27
  • Location: Villa Park (Chicago Suburb)
  • Status: offline
Re:Midisport 2x2 Anniversary Edition 2011/03/07 23:18:42 (permalink)
Hawky


SOLVED!

FINALLY, the Midisport 2x2 ANNIVERSARY Edition works everytime on my Windows 7-64 bit machine.

1. With the Device plugged into the USB port bring up the latest M-Audio driver file 6_1_2 and click on it

2. Navigate to the UNINSTALL driver window and run this to remove existing driver

3. Remove the USB cable and plug back in

4. Windows 7 will find it's own driver and load this to start working

5. Start SONAR X1 and it should now show up in Preferences dialog box

So, the M-Audio driver is NOT needed to make this work on my WINDOW 7-64 bit machine

I reset the machine several times and it worked everytime.  Also, the Merge button is pressed in. 

I hope this helps ...

Hawky
I realize I'm late to the party but I wanted to say something to share information.
Last October I installed Windows 7 64 bit and I own 2 midisport 2x2 so I loaded the 64 bit drivers. They worked with no problem...untill I rebooted and recieved the BSOD. 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. So I shut down, disconnected the mididsports and restarted.
The system came back up and offered to search for a reason why it blue sreened but it couldn't find anything. I reconnected the midisports and started up Sonar. Everything worked fine. So I loaded the next driver, rebooted but before the system went through the POST I disconnected the midiports. The OS started and everything was fine. I reconnected the midisports and started Sonar. Again, everything was fine. Everything worked.
Of course one day I forgot to disconnect the midisports when I rebooted and got the BSOD again.  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.
As I wasn't using the 2nd midisport, I didn't reconnect it. Now here's the wierd part.
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. Weird, huh?
So, if I have one midisport connected, no problems whatsoever. Leave both connected BSOD, everytime.
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.
#33
Fog
Max Output Level: 0 dBFS
  • Total Posts : 12302
  • Joined: 2008/02/27 21:53:35
  • Location: UK
  • Status: offline
Re:Midisport 2x2 Anniversary Edition 2011/03/07 23:31:19 (permalink)
daveny5



M-Audio's MIDISPORT drivers are a clusterf**k.



Not really. Just follow the instructions and it works fine. Problem is a lot of people don't have time to read the instructions and then wonder why it doesn't work.


or in m-audio / avid's case.. they simply don't write drivers for win 7 that actually work .. (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. I got told the usual "unplug" "reinstall" 3 times, like I'm green to all this stuff. So no , not "always" user error.

 I moved to another company and they may think they are the biggest, but when their sales get affected they'll hopefully get the hint.

do I think they could have written new drivers for the old midi interfaces? probably, but heck why not make users buy new interfaces.


post edited by Fog - 2011/03/07 23:33:04
#34
wormser
Max Output Level: -71 dBFS
  • Total Posts : 984
  • Joined: 2007/11/18 11:26:55
  • Status: offline
Re:Midisport 2x2 Anniversary Edition 2011/03/08 14:50:44 (permalink)
Fog


daveny5



M-Audio's MIDISPORT drivers are a clusterf**k.



Not really. Just follow the instructions and it works fine. Problem is a lot of people don't have time to read the instructions and then wonder why it doesn't work.


or in m-audio / avid's case.. they simply don't write drivers for win 7 that actually work .. (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. I got told the usual "unplug" "reinstall" 3 times, like I'm green to all this stuff. So no , not "always" user error.

I moved to another company and they may think they are the biggest, but when their sales get affected they'll hopefully get the hint.

do I think they could have written new drivers for the old midi interfaces? probably, but heck why not make users buy new interfaces.


And that's exactly what I did.
Buy a new interface, and not an M-Audio brand.

Don't get me wrong I've always had good luck with the company and my Delta 66 and Delta 1010 are still working fine.
Since Windows 7 though, they really dropped the ball. Actually since Vista to be technically correct. I refuse to purchase any more of their products especially when there are other options with better support. I'm hoping maybe they will turn around now that ProTools works with any hardware but I'm suspicious.



Windows 8 x64
Intel i7 950 3.06ghz 6 GB DDR3 1333(1066) OCZ memory
Gigabyte X58A-UD3R v.2.0
Delta 66.
Seagate 1.0tb drives x4 OS, Audio, VST, Backup Stuff. 
Mackie MCU Pro Latest.
Faderport.
Sonar X2, PreSonus 2.x, Reaper.
 
#35
Page: < 12 Showing page 2 of 2
Jump to:
© 2024 APG vNext Commercial Version 5.1