problem with m-audio trigger finger

[deep9]

My pc : Asus p5b Intel E6600 2Gb ram Video Asus EN 7600 1 Pulsar II.
When i try to install m-audio controller (class compilant driver) windows xp sp2 don't recognize the hardware; i try in every usb port but don't work...so i bought a pci to usb 4 ports and seems to works but from the pulsar os the message was: " Can't find file 17 check the installation manual..." and the pulsar disappear from device manager of windows till i unplugged the usb adaptor . A friend of mine have the same pc configuration but with motu 896 and the m-audio works.
Please if someone could help me....

[siriusbliss]

Scope doesn't work with USB MIDI ports. Doesn't even SEE the USB stuff.
I have the same problem with padKontrol. No stupid USB works with Scope.

So....I'm going to have to go back and try MIDI-OX to route the USB junk into Scopes' MIDI input port and trick Scope into seeing the USB as MIDI..

Problem is, last time I tried this, it crashed my system.

I don't know of any other way to get USB junk into Scope.

STUPID useless USB...

Greg

[deep9]

i used trigger finger for the last 2 years with pulsar II but with other pc with Intel mobo 925 chipset with no problem at all, so it's very strange....

[valis]

My pc : Asus p5b Intel E6600 2Gb ram Video Asus EN 7600 1 Pulsar II.
When i try to install m-audio controller (class compilant driver) windows xp sp2 don't recognize the hardware; i try in every usb port but don't work...so i bought a pci to usb 4 ports and seems to works but from the pulsar os the message was: " Can't find file 17 check the installation manual..." and the pulsar disappear from device manager of windows till i unplugged the usb adaptor . A friend of mine have the same pc configuration but with motu 896 and the m-audio works.
Please if someone could help me....

Sounds to me like you either have an irq conflict (check in device manager) or you've run into the 10 device limit on WinXP:
http://www.rme-audio.com/english/faq/10entrye.htm

If you plug a usb device into different usb ports, windows loads a device entry for EACH PORT that you've used, even if it isn't the current one used. Windows can't "see" the driver that was loaded for a different usb port, this is why it installs a new one for each port that you use. M-audio has a tool they call MidiFixUtil.EXE which can help check for duplicated entries of its drivers, but you'll first need to find the uninstaller for your device (for my midisport usb midi interface it's called MidisportUninstaller.exe).

[valis]

Scope doesn't work with USB MIDI ports. Doesn't even SEE the USB stuff.
I have the same problem with padKontrol. No stupid USB works with Scope.

So....I'm going to have to go back and try MIDI-OX to route the USB junk into Scopes' MIDI input port and trick Scope into seeing the USB as MIDI..

Problem is, last time I tried this, it crashed my system.

I don't know of any other way to get USB junk into Scope.

STUPID useless USB...

Greg

Scope can only see its own hardware and software inputs, so to get a different device routed into scope you'll need to use a sequencer or midi-ox. The issue here is that Scope isn't intended to be used instead of a sequencer, but rather WITH a sequencer, which is what you would normally route midi and audio signals with.

If you're experiencing lockups when you route a midi device to scope that's most often a problem with Active sensing (which can be filtered out both in midi-ox and in most sequencers when you route midi to scope's drivers).