Fast Track Pro & ASUS Laptop

[Bit Putty]

Hi all,

I was browsing about this eve for some answers to the following problem and seen that you have a dedicated M-Audio specific forum (Ace!)

So I hope that you may be able to shed some light on the matter. :confused:

I recently purchased an M-Audio Fast Track Pro interface for use with my Laptop (Asus A6000 - USB 2.0 x 4)

It has been working even though the applet original stated 'not connected'. But to my displeasing, when using in conjunction with Reason it has finally decided to give up the ghost.

After installing the drivers first and restarting the laptop, plugged in the interface and turned it on I was greeted with the applet in the system tray. After double clicking to invoke it informed me that no device was connected.
The applet on shows the 'Panel Version' - firmware is listed as (n/a)

I followed the usual route of updating to most recent drivers and still - the problem arises.

Basically, I have been led to believe it could be an 'IRQ Resource Sharing' problem by the UK M-Audio Hardware support.

The only annoying thing is that, this is the only USB device plugged into and has ever been plugged into the system (as I am aware there is a 10 device limit! - Sound on Sound article http://www.soundonsound.com/sos/mar05/articles/pcmusician.htm
)

I did take the liberty of testing the device on the other workstation and to my amazment - installed first time and gives ' connected' in the applet. This also displays the firmware version and runs perfectly so I know the interface is not at fault.

I have had a fair bit of experience in setting up studio systems and various hardware problems over the years so if anyone has any tips on 'IRQ Resource Sharing' - Fire Away
bP

[Bit Putty]

So, I've now restored the laptop 4 times, usually i work with an USB optical mouse in the port so I thought, Hmm, could be using resources.

Still no joy. Last test scenario

1. Laptop Restore
2. Restart.
3. M-Audio Driver Install.
4. Disabled the internal modem and network card as these share the same bus.
5. Restarted
6. Connected the Fast Track, Switched on!
7. Found New Hardware - Loaded the driver.
8. Control applet still gives 'not connected'

However, windows sound schemes do playback through the fast track but when the ASIO driver is selected in Traktor 2.5, I get glitches and drop outs then the card stops working all together.

Hmmmmmmm!

Any ideas?

:mad: :confused: :(

[David Muniz]

The problem is not the amount of USB devices on the USB bus. This is not what an IRQ resource issue is.

Think of IRQ's as pipelines of resources to different components of your computers. The analogy I like to use is this: imagine taking a hot shower, then someone turns the hot water in the kitchen on. Because the "pipeline" is shared between the kitchen and the shower, there is less hot water for the shower and you get a blast of cold water.

That's a way of thinking about how IRQ resources work on your computer.

If the UK tech support team told you it was an IRQ resource conflict, you'll have to either disable devices that are not in use and sharing the IRQ resource or disable all devices you are not using in the BIOS and reinstall windows.

The best bet is to contact their tech support team again and ask them to help you reallocate your IRQ resources.

Thanks
D

[Bit Putty]

Ok chaps, I've just had success.

I see what you mean in your analogy of an IRQ Resource David (Thanks!)

I'm of the old school in my understanding of IRQ's back in the DOS era, and hadn't grapsed a good understanding on the new approach.:o

What you said about the number of USB devices though did actually get me into thinking about the modern/newer laptops and how they are supplied with more built in peripherals (Like webcams, card readers, IR Ports, Wireless network cards......), and it was combination of all four that were choking my system.

Hence why I could see no resource conflicts (Viewing 'Resources by type' also gave no indication as each has a separate IRQ without conflicts)

Anyway, to solve the problem I've created a new hardware profile from a copy of the one currently on the laptop. Then disabled the Webcam (which is internallly connected to the USB bus), IR-Port, Card Readers and the Wireless network card)

Now when I switch on I can choose an 'Audio' hardware profile, when I activate the M-Audio tray applet I get the 'connected' atatus.

Time to install some programs now,:D

Thanks again!

bP

[sobesalsa]

Could you tell me how you have setup your Fasttrack in the Traktor environment.... My direct question goes toward the monitor setup... Currently I have 1/2 to my main output to my mixer and 3/4 out to my headphones... I currently have RCA to inline/coupler to my headphones. Ive kept reading about playing around with the mix knob and directing 3/4 to go out through the headphone jack on front of the Fasttrack interface... Are you using this setup?.

-E

[David Muniz]

Just to be clear, Sobe, we're talking about the Fast Track Pro, not the Fast Track. Two different devices, and since you mention outputs 3/4, then I'm assuming you mean Fast Track PRO.

All you have to do to hear the 3/4 output via the headphone jack is to press the A/B button on the FastTrack Pro. This flips the signal from 1/2 to 3/4.

[gimbal]

This disabling all the unnecessary piece of hardware at an alternative hardware profile reduced the frequency of the problems. However, they still persist despite occuring less frequently.
I think it is somehow related to the usage, because it mostly happens
1-when the cpu is used extensively
2-when the computer is doing some graphical calculations (therefore it is related to the nVidia graphics card I think). I work with processing (a java platform for mostly visuals) and I can't listen to music at the same time.

when I am working on ableton live with Arturia's analog modelling plugins, such as Arp2600 or Moog Modular, both have extensively complicated GUI's and cpu usage, I usually get the fast track dead within 10 seconds. But if I don't open the plugin interface, it plays nicely without a problem (not always).

So this is more input to the problem, I have the same configuration with bit putty and the very same errors. Ah the warm feeling of emphaty....

cheers
Ali