Community Forums Archive

Go Back

Subject:Finally some good news!
Posted by: jeepman83706
Date:2/10/2003 8:57:00 PM

Well, after ditching the MidiSport USB Midi piece of shit because of all the problems it was giving me i.e. crashing and crap like that, I got an Edirol USB Midi Interface (thank you for the suggestion coolout!!!) and everything works fine and dandy! Now I can finally concentrate on making some kick ass music!

Subject:RE: Finally some good news!
Reply by: coolout
Date:2/10/2003 9:04:31 PM

glad i could be of service

Subject:RE: Finally some good news!
Reply by: midihead
Date:2/11/2003 12:01:27 PM

What was the problem with your Midisport? I've got one too and Acid keeps locking up, giving exception errors, etc. I ditched my M-Audio card for an Aardvark LX6 and that seemed to give me better latency, but the lockups still occur.

Can you give me specifics as to what problems you were having so I can see if they match mine? I wonder if it's my Midisport.



Subject:RE: Finally some good news!
Reply by: jeepman83706
Date:2/11/2003 12:22:18 PM

So I am running Windows XP and Acid kept crashing when trying to record audio. CuzinB (and everyone else!!) offered great advice. It ended up that the MidiSport drivers just weren't jiving well with my computer. In order to determine what is causing your crashes, CuzinB offered this advice:
Windows XP includes a registry value that you can use to save stack traces that enable you to identify the problem driver. Use Registry Editor (Regedt32.exe) to view the following registry key:

HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

Add the following registry value, and then restart your computer:

Value Name: TrackLockedPages
Value Type: REG_DWORD
Value Data: 1
Radix: hexadecimal

After you make this change, Windows saves stack traces so that you can identify the problem driver. There is no other way to determine which driver is neglecting to clean up the I/O operations. After you enable this flag, if the driver commits the error again, you see the following error message:


Parameter 1 - The calling address in the driver that locked the pages
Parameter 2 - The caller of the calling address in the driver that locked the pages
Parameter 3 - A pointer to the MDL containing the locked pages
Parameter 4 - The problem driver's name (Unicode string)

The problem driver's name is listed on the blue "Stop" screen and is available for dumping again as the fourth parameter in the "Stop" data.

After you identify and update or remove the problem driver, you should remove the TrackLockedPages value from the registry.

You can also try downloading the beta drivers for MidiSport. Nothing worked for me so I returned it, bought an Edirol USB Midi Interface, and haven't had problems with that at all.

Hope that helps. If you have more technical questions, I would direct them to CuzinB since he originally told me how to track the problem files:)

Subject:RE: Finally some good news!
Reply by: Vocalpoint
Date:2/11/2003 1:50:13 PM


I read your bits about your M-Audio issues....I have been using the Delta 66 for 18 months now and I have never had a problem. I did - however have issues with the Midisport awhile back....took it back almost immediately and went back to a standard Soundblaster Live for my MIDI input - it's as solid as a rock.

Also - pound for pound - M-Audio still does some of the best drivers out there. This issue with their MIDISPORT will get cleared up, I am sure.

Cuzin B

Subject:RE: Finally some good news!
Reply by: midihead
Date:2/11/2003 7:20:25 PM

Thanks for the troubleshooting tip! I'll check it out. Based on your post, I went out and picked up an Edirol UM-2 today...time will tell. I don't like the cheap plastic housing of the Edirol like the Midisport which is built like a tank. Midiman definately has a head up on quality of hardware.

CuzinB, I loved my Delta 66...don't get me wrong. It's just that when I was trying to troubleshoot this issue, M-Audio tech support stated that they were aware that the drivers for it and XP weren't bug free yet. Now that I know the Midisport too has issues, I've dumped it also. I don't have time to wait for them to get it right. XP has been out for over a year now. I'll still stick to my statement about how it takes them too long to get the driver issues corrected each time a new OS is born. I've had Midiman/M-Audio products since before Windows 98 came out and remember problems not getting resolved until almost a year after the release of '98, ME, 2000, and now XP. Time is money.

Subject:RE: Finally some good news!
Reply by: L25
Date:2/11/2003 11:00:55 PM

are you using current drivers

the beta is dated 2-6-2003

Subject:RE: Finally some good news!
Reply by: jeepman83706
Date:2/12/2003 8:57:41 AM


Hopefully since I suggested the Edirol, it works for you!!! (Crossing my fingers) :)

Subject:RE: Finally some good news!
Reply by: SonyJennL
Date:2/12/2003 12:08:07 PM

Sorry to pop into the thread so late.

I did a significant amount of testing with the MIDISport 2x2 on a WindowsXP system and I found it to work quite well. We've also test the Aardvark cards and found their drivers to be quite fussy. They crash often... especially on recording so maybe your problem isn't with the MIDISport.

You say that you are crashing on audio record. My bet would be on your soundcard rather than your MIDI interface.

I'll keep checking back. Let me know how it goes.


Subject:RE: Finally some good news!
Reply by: jeepman83706
Date:2/12/2003 1:27:47 PM

You know I would have thought that too, Jenn. But everytime I tracked the file that was crashing the computer (using the Regedt32.exe command to track problem drivers), it always came up as the Midisport drivers. I returned it, bought an Edirol, installed it, and everything works fine. The guy at the music store I bought the Midisport from said that a lot of people have returned those bc of similar problems.

Subject:RE: Finally some good news!
Reply by: midihead
Date:2/12/2003 7:42:57 PM


Jeepman is right. I got rid of all my M-Audio/Midiman products and everything is cool. The Edirol works great! Thanks! I've also not had any problems with the Aardvark LX6 fact the ASIO latency kicks the snot out of the Delta 66. Just as a note about the crashes that happen upon hitting "stop" after usually occurred when trying to record the track while a MIDI track is playing my Virus. I actually spoke with Sonic Foundry tech support who confirmed Jeepman's claims about Midiman's Midisport being suspect. He stated that ANY USB Midi port could potentially be problematic and suggested a PCI-based model. Allthough I've not had problems yet with the USB-based Edirol, time may tell otherwise...we shall see. He said to avoid MOTU, as he's gotten a lot of calls about their products causing problems.

Just in case you're wondering about my system specs, here they are:

Intel Pentium 4 1.9 GHz
Intel D850MV Motherboard
NVidia G-Force 2MX video card
Aardvark LX6 Pro sound card
Edirol UM-2 midi interface
Segate Barricuda UDMA 18 gig primary hard drive for OS
Segate Cheetah 10,000 RPM 18 gig Ultra SCSI II hard drive for recording
Western Digital UDMA 120 gig hard drive for sample library

No network connection...all networking services shut off
Optimised for audio...all graphical shite turned off
Latest bios update, XP SP1, All the latest drivers


Subject:RE: Finally some good news!
Reply by: SonyJennL
Date:2/14/2003 12:51:04 PM

Quick update-

M-Audio does have a bug in their beta drivers causing the audio problems you describe. They are aware of this.

Go Back