Good news: Fix for nForce4 + X2 + 2xUAD-1

[DARKO]

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

 

[jcat]

That's some good and usefull info. Shame UA couldn't work this out, but at least it's resolved now...

Nice one!

=D>



Cheers,

jcat

 

[Akis]

Could someone check if this one fixes the MSI K8N Neo2 (nForce 3) issues, too?

 

[sj_digriz]

Yeah, that would be nice to check on the K8N...but i can't do it until this weekend.

 

[SaxMan]

Good news indeed! Will try this after work :lol: :lol: :lol:

 

[vksf01]

so, does anyone know if this will help with the stuttering problems that others (like me) have had with the v4 drivers on non NForce boards? I have a tyan 2885 that cannot use the v4 drivers without stuttering.

also, i wonder if, now that they're aware of this, whether UAD is going to address this in v4.2

 

[Tungsten]

Since this is a UAD & Multi-CPU system issue wouldn't it be the smae problem on all multi-processor systems?


ie. I'm having extreme crackling problems with my UADs in a Asus A8V Deluxe with AMD X2 4400.

 

[ampvoodoo]

I hope someone can confirm this fix. I just bought 2 cards one being an ultrapack tried to load them and my pc wont even boot with the cards installed (Nforce4). The retailer advised me it would work with my system but now says I cant return them because they are open. Its a crock.

 

[Tungsten]

Anybody notice that the IntFiltr tool mentioned in original post is for Windows 2000 (not XP)?

 

[Joey123]

Could someone check if this one fixes the MSI K8N Neo2 (nForce 3) issues, too?

Gents i have my UAD in the box and got my RA number today - I tried the above fixes and it made it so the computer wouldn't boot when the UAD was in any PCI slot.

I tried a lot of combinations of moving some devices to the 2nd processor and like I said, for some reason the computer won't boot with the UAD card. I'll try a few more times tonight - never let it be said I didn't try every option I could.

X64 4400+, 2 G Corsair RAM, SATAs, Neo2 nForce3 Platinum etc.

 

[SaxMan]

I tried this fix, been working on it several hours now.
I select the UAD DSP card in the config utility infiltr.exe,
& get the message 100% of the time Unable to add/remove filter driver.
So it seems I will not be able to set the interrupt filter to 1 processor.



I get the following message when a UAD-1 plugin is loaded into one of my sessions: \"The audio device bufferunderflowed. If this occurs frequently, try decreasing the H/W buffer size in the playback enginepanel or remove other devices from the audio firewire bus (-6085)\"

 

[franYo]

The filter should be applied to UAD-1 DSP card, not the UAD-1 Powered Plugins driver. Applying the filter to PP driver might lead to problems, at least that has been my experience. Ghosting your system partition before doing this kind of stuff is always a good idea.


Franjo

 

[SaxMan]

The filter should be applied to UAD-1 DSP card, not the UAD-1 Powered Plugins driver. Applying the filter to PP driver might lead to problems, at least that has been my experience. Ghosting your system partition before doing this kind of stuff is always a good idea.


Franjo

Have you been able to get this fix to work? If so details PLEASE !!!!!!!!!
:lol:

 

[Joey123]

I tried that - the new Interrupt Filter from MS dated 2003 and

applied to UAD-1 DSP card, not the UAD-1 Powered Plugins driver.

Bad still, computer won't boot with UAD card in any slot.

Sweetwater thinks my UAD card is defective but I dunno - have to send it back today and that's the end of it.

The UAD's Precision Multiband is the most beautiful piece of audio code ever - I've heard it all and that is the best. I'll miss that

I'll try UAD again if there's a different incarnation someday, not the same PCI card though, never again - I wasted a crucial week and I don't like wasting time.

 

[ampvoodoo]

I doubt its the card. They said the same thing about mine so I tried it in another system no problem. I agree with the waist of time and money at this point. While spending hours on the phone trying to get my uads working I had to relaod all my drivers for 4 echo cards and reconfigure everything only to find it didnt work and go back to the same config I had before I started. What a Joke. I really love my UA hardware La2a and 1176 but I will never buy another UA software product again unless they do proven RnD beforehand. Its ridiculous that my system is compatible with every other piece of software and hardware out there but not with UA.

 

[sj_digriz]

Ok, I just spent the last hour with that utility and all it does on Windows XP Pro is disable whichever device you assign it to. So, it doesn't do anything constructive.

However, during the process I disabled my Delta1010 by adding a filter. This forced it to the AC'97 chip on the Mobo for sound. GUESS WHAT!!!! No garbled output from the UAD-1s.

I'm trying to figure out a way to troubleshoot this now. Maybe there is hope after all.

 

[JoeP]

It was posted on the RME newsgroup that the affinity filter posted in this thread will not work with XP. There's a newer version that's part of the Windows 2003 resource kit that works with XP. You can grab that from http://www.microsoft.com/downloads/...69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en. I've installed that one with partial success. The pops and clicks are completely gone using the onboard firewire on my MSI Neo4 Platinum board with 2 UAD-1's and a fireface. The only problem is I get stuttering dropouts whenever a UAD's GUI is onscreen. Closing the GUI gets rid of the dropouts. Makes it kind of hard to make adjustments. I tried setting my graphic card's affinity to a different CPU from the UAD's, but that made no difference. It seems real promising, so I'm not giving up yet. Its definite progress.

 

[SaxMan]

JoeP If you are ever in Atlanta look me up I owe you a few cold one's.
These new files work on my system, I got a buffer under run error, but hen I
remembered I had only oneRTAS processor chosen, change it to 2, up the samples to 512, so far I've gotten My 1176 & pultec running :lol: :lol:

 

[sj_digriz]

It was posted on the RME newsgroup that the affinity filter posted in this thread will not work with XP. There's a newer version that's part of the Windows 2003 resource kit that works with XP. You can grab that from http://www.microsoft.com/downloads/...69-57ff-4ae7-96ee-b18c4790cffd&displaylang=en. I've installed that one with partial success. The pops and clicks are completely gone using the onboard firewire on my MSI Neo4 Platinum board with 2 UAD-1's and a fireface. The only problem is I get stuttering dropouts whenever a UAD's GUI is onscreen. Closing the GUI gets rid of the dropouts. Makes it kind of hard to make adjustments. I tried setting my graphic card's affinity to a different CPU from the UAD's, but that made no difference. It seems real promising, so I'm not giving up yet. Its definite progress.

I am using the 2003 Resource Kit version. It works, just whatever card I apply a filter to is inoperative.

 

[franYo]

The filter should be applied to UAD-1 DSP card, not the UAD-1 Powered Plugins driver. Applying the filter to PP driver might lead to problems, at least that has been my experience. Ghosting your system partition before doing this kind of stuff is always a good idea.


Franjo

Have you been able to get this fix to work? If so details PLEASE !!!!!!!!!
:lol:

I don't suffer from this problem since I run a FW audio interface on a PCI Express FW card, however, out of curiousity I put in my old Terratec EWX 24/96 PCI card and applied the filter and I had no pops/clicks with my test project, 12 sine wave audio tracks with 24 UAD plugins active, UAD meter at 95%. I did get an occasional very slight pop when lots of plugin windows were open though. However, I don't think these would even be audible with normal audio material (sine waves are very good for detecting pops/clicks).

Franjo