Page 1 of 1

Trigger Finger MIDI Input problems with Live5.2.1 OS X Intel

Posted: Wed Aug 09, 2006 4:52 pm
by Twisted Textures
Hi, I have been having problems with my Trigger Finger since I bought it recently.

I'm trying to use it with Ableton Live 5.2.1 but the MIDI drops out after about 10 seconds of using it or sometimes doesn't even work at all. The unit is plugged into my computer via USB and I also have a FW410 which takes a MIDI input from an external synthesizer. I have tried using it without the FW410 plugged in but I am still having no joy.

Any help would be greatly appreciated, as I really want to get on with using my Trigger Finger with Live.

Please see my studio profile below.

Cheers,

TT

Posted: Thu Aug 10, 2006 8:37 am
by Twisted Textures
Does anybody have the answer? :cry:

Posted: Thu Aug 10, 2006 10:08 am
by Johnisfaster
this could be a long shot but I've heard some of the new intel macs are having trouble with their usb ports. though I hope thats not the case but if it is then I'm sure you can return it.


prolly something else though...

Posted: Thu Aug 10, 2006 12:26 pm
by Twisted Textures
Thanks Johnifaster,

I'll try it out on my PowerBook and see what happens.

If this is the case I can just take the machine back to work and have it replaced, so that's not a problem.

If anyone else has any ideas though, that would be great.

Cheers,

TT

Posted: Thu Aug 10, 2006 1:15 pm
by Surreal
There is the strong possibility that only ONE port will work properly with the trigger finger...the trick is figuring out which one. the suggestion i posted was for the macbook pro 17...i don't know for the imac

Posted: Thu Aug 10, 2006 1:53 pm
by resonatorman
Hi Mate
I have had a similar problem with an intel iMac, however sometimes I couldn't even get the TF to be recognised. I don't think it's a USB iMac problem per se, as on the OSX Audio site awhile back a few of us were having similar problems & it was happening with all intel macs. PPC macs no problems. I logged this with M-Audio support, they have 'escalated the' issue. I wonder if it will turn out that they may need to release a driver for it? Anyways, their workaround was try running it through a powered USB hub. I have done this & now works OK for me. Hope this helps?
Cheers

Posted: Thu Aug 10, 2006 2:29 pm
by Machinate
use a usb hub in between.