Could it be scope & dualcore fix as well?

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
Stige
Posts: 260
Joined: Sun May 25, 2003 4:00 pm
Location: Finland

Post by Stige »

Hi

I was browsing uad-1 forums and found this. There has been lots of problems with uad-1 and x2 systems, as well as with scope too. I don't own dualcore system, but I'm hoping I will someday. That's why I feel lots of interest for seeing audio hardware working with it.
Anyway, here is the quote from original post:
With big help of UA support, my system finaly working fine!
Read carefully this message, and try that!
Your life will be changing!

One of our users reports that he has been able to get UAD to work with nForce 4 and an X2 processor. We have not confirmed this fix yet, but here is what he had to say:

Actually the whole issue boils down to how the way the UAD hardware
driver functions in a multi cpu environment.
The fix I used is to limit the interrupt to one cpu by telling the
kernel it to route the right way.
http://support.microsoft.com/default.as ... -us;252867
If you would allow both cpu's it goes wrong because timing issues. And
you end up getting garbled sound.
Follow the interrupt filter instructions and use it to add a filter for
the UAD dsp driver.
Reboot and enjoy a fine working system WITH the UAD.

In addition you can update the kernel for multiprocessors.
http://support.microsoft.com/?id=896256

And the AMD CPU driver.
http://www.amd.com/us-en/Processors/Tec ... 18,00.html
What do you think. Could it help with scope problems?
Shayne White
Posts: 1454
Joined: Tue Dec 11, 2001 4:00 pm
Location: California
Contact:

Post by Shayne White »

That interrupt hotfix only applies to Windows 2000, and I don't know if it works for XP. I've tried entering the /intaffinity setting into boot.ini to force all interrupts to one processor, and that didn't fix anything. :sad:
User avatar
valis
Posts: 7681
Joined: Sun Sep 23, 2001 4:00 pm
Location: West Coast USA
Contact:

Post by valis »

I've been running Scope on dual cpu machines fine since 3.01 (a or c can't recall) so I would have to say that SMP in general isn't affecting Scope anymore (only Vorb has proven to be an exception). Before that I tried using that tool to affix the driver's affinity to a single cpu, and I had mixed luck. It's been my impression that the problems that Scope experiences on Nforce4 are related to the PCIe implemenation, although since I don't own a system I can't say for sure. Certainly noone can stop you from trying that tool to see what results it yields for you. :smile:
vipal
Posts: 61
Joined: Wed Nov 23, 2005 4:00 pm
Location: amsterdam

Post by vipal »

with me uad and asus p5ld2 dualcore worked fine. had a lot of other problems though but not with uad
User avatar
tlaskows
Posts: 1512
Joined: Fri May 20, 2005 4:00 pm
Location: Ontario, Canada
Contact:

Post by tlaskows »

This must be something specific to the dual core/motherboard combo. I've been running Scope on a dual CPU computer (Athlon MP 2800) without any problems.

Tom
Post Reply