How's your IRQ?

[Rock_Artist]

We have here the ASUS P4P800SE.

It has 5 PCIs... (1/5 share same IRQ)

Looking under the IRQ list I see the following:
1-18 - system related -> agp, usb, board bridge & stuff

20-21 HD Core + HD DSP
22-23 HD Accel + HD DSP

Now the Marvel Yukon Onboard 1Gbps share IRQ 21 or so with the HD &
the Intel USB2 controller share IRQ 23 with the Accel.

In addition any slot I put the Firewire cards (I need 2 - 1 for Mojo, 1 for perpherials <- not used that much)

they decide to get on the HD IRQs.


Now since we use APIC/ACPI we aren't allowed changing IRQs and Windows keep giving me the same IRQs.

So why does it bother me?

because...

When I start having "high DSP usage" with high edit density and all of that with the Mojo playing back the DV25 parts from the Avid AAF the system video playback choke and drop frames.

I wonder how your rig manage with the IRQs?
How bad is it the have the USB2 (snif snif - what about using USB2.0 HDs) and the HD cards on sharing the IRQ.

Also is there anything beyond 23 IRQs? if so why our rig cannot use it.

So if anyone have any clues about the mystaries of IRQ & Pro Tools it'd be great!

(Now what about those MacIntels and IRQ this is also interesting)










(The following is for those who might be after solutions on the DUC)

Trying to solve the problem with changing the PCIs slots
didn't help much.

The only thing that made it all work together seems to be:

1. Enabling Hyperthreading (without it we seem to get the Buffer Underrun for video, disabling the video playback stop just get vide out of sync)

2. Changing the playback engine to smaller DSPs usage (1 DSP mixer instead of 3 DSP)

Slot order:
0 AGP
1 HD Core
2 HD Accel
3 FW (for Mojo)
4 FW (for additional Hard-Drives & hardware)

[nikki-k]

Shared IRQ's should not be an issue. With ACPI, those days *should* be gone. I have shared IRQ's, but no issues running full track counts with HD Accel for all rates.

You mention Mojo, and a single processor motherboard; I was under the impression Mojo had a dual CPU (not simply HT, or dual core) requirement...no?