Constantly rescanning my MIDI Controller

[SamIchi]

I got a M-audio Trigger Finger, and I constantly have to rescan the device. If I don't use it for a minute or so, I have to rescan it. Last night I was using it for a long time and it just stopped. SO I rescanned like I always did, and then it stopped working again within 10 secs. So another rescan and the same thing. I just quit after that. I was using GarageBand. I'm still a noob to digital audio, so maybe I'm missing something.

[Badecator]

I'm having the EXACT same problem, and have been for months. I have a MacBook Pro 2.2. It's like the Trigger Finger or AMS timeout and stops sending/receiving midi. I read that someone who had a similar problem just changed the USB cable. It didn't work for me. Of the 3 cables I have, one of them works intermittently, and the other two not at all; the non-working two work fine for everything else. Maybe it's a length issue? If the cable is too long, there's power loss? I dunno. HELP!

[SamIchi]

http://www.m-audio.com/?do=support.faq&ID=c5456566aab7a574edd81d89b3a62784

Searching through the M-Audio forum I found a thread that lead to this. I'll post to help out if anyone was looking for an answer. I guess it has something to do with intel, and the USB ports.

Use a hub and it should work properly. I don't know why I never tried it myself.