Latest on the err=21 problem with Sonar?

[guitardood]

Hey Folks,
I've been have a ton of these popping up since upping to 4.1. Config is as follows:
D865PERL-PCI Latency 96
P4 3.2
4GB RAM
2 Raptor SATA Drives
Sony DVD-R/RW
TDK CD-R/RW
AGP-Matrox Parhelia 128MB
Slot1 - EMU 1820m
Slot2 - UAD-1 1
Slot3 - UAD-1 2
Slot4 - Sillicon Image ATA133 Raid Controller w/4 Maxtor 150gig
Slot5 - D-Link 1gig ethernet
Seems the problem starts showing up after running SoundForge7 from Sonar5 to do some fine wave file editing and a lot of starting/stopping playback while working on a specific section. Only fix is to reboot. Also, the UAD-Monitor program show no-cards and can't set any settings after the err=21 occurrs and the only fix is a reboot.

Any help would be greatly appreciated.

Regards,

guitardood

 

[jaydrake]

There hasn't been much said lately. If you really want to get work done, use 4.0 DXI's. Vst's are the root of the err-21 problem.

 

[cAPSLOCK]

I went back to 3.9

 

[vksf01]

same here. 3.9 until they fix the stuttering problem :evil:

I went back to 3.9

 

[guitardood]

(STILL HAVING ERR=21 WILL BUY NO MORE PLUGINS UNTIL THIS IS RESOLVED)

I have to agree with cAPS at this point. I bought the UAD-1 plugs both for their sound quality and to ease the stress on my DAW, not transfer the stress to myself . I've bought every plug so far, but no more. I've gotten quite disheartened that updates only seem to be released when new plugs are available. If anyone at UA is reading this, please resolve this problem.

In the mean time, does anyone know if there a way to go back to 3.9 drivers and still use the 4.1 plugs?

 

[guitardood]

tonight

In the middle of working tonight, err=21 again. This time however, I got the following error from sonar

The instruction at \"0x10d36926\" referenced at \"0x10d36926\". The memory could not be \"read\".

Click on OK to terminate the program
Click on CANCEL to debug the program

Clicked OK and Sonar terminated. UAD-1 cards were still hosed and needed a reboot.

This is really a huge drag

 

[ed_mcg]

There has been discussions between Cakewalk and UAD back at NAMM time, the result is that one or both have to make some changes and that this will take \"some months\" to resolve.

In the mean time, use v3.9 or v4.0 and repeat the mantra

STILL HAVING ERR=21 WILL BUY NO MORE PLUGINS UNTIL THIS IS RESOLVED

 

[jaydrake]

In the mean time, use v3.9 or v4.0 and repeat the mantra

Let me just add \"use v3.9 or v 4.0 DXI versions\". It's the vst's version that causes err 21 in Sonar.

 

[cAPSLOCK]

Well, and I have to add this.

The problem may have something to do with (in fact I am sure it does) the VST-Adapter and Sonars plugin delay compensation.

I think both UA and Cakewalk have to address this.

But there are a couple important points on this issue for me.

1. Sonar is my DAW of choice. There is no reason I couldn't use Nuendo or Pro(prietary) Tools. I just like Sonar more than these. A lot. The workflow for me in Sonar is leagues better than other software. To each his own, but this is my own. If I had to let one go it would be the UA plugs (difficult as it would be).

2. Though the combination of Sonar/AMD (specifically via chipsets like the A8V) and the Windows platform seem to be an evil trifecta for the err=21 problem they have happened on other systems. I myself have seen it on an Intel machine. It has been reported (with less frequency) using Steinberg tools, and there are even threads about it on the Mac side of this forum. This leads me to believe it is not entirely a Cake/Via thing.

In the end, it seems that if something offends the UA driver by means of how quickly the data goes from host to card it pukes. Don't know if it is PCI bottleneck, overflow, or an issue with plugin delay compensation.

I understand that these things can be hard to solve, and a bunch of pissed of customers is not really gonna help. But it is the nature of the beast.

I have hoped for a long time, and still hope that UA/Cakewalk can solve this.

Until then I am happy enough with 3.9

cAPS

 

[jaydrake]

Until then I am happy enough with 3.9

Me too. As nuts as the err-21 thing made me, as soon as I resolved to go back to 3.9 with DXI's.... well,... I'm lovin' it.

 

[bulls hit]

I'm getting the err21 as well using Cakewalk GT Pro.

I've just bought the UAD-1 card, and am using the 4.1 VSTs. How do I get hold of the DXi plugs (assuming the VSTs are the problem)

 

[secretworld]

I'm getting the err21 as well using Cakewalk GT Pro.

I've just bought the UAD-1 card, and am using the 4.1 VSTs. How do I get hold of the DXi plugs (assuming the VSTs are the problem)

http://www.uaudio.com/support/software/ ... loads.html
good luck
Vincent

 

[bulls hit]

Thanks for the link Vincent.

Downloaded, installed, and while not rockin 100% yet, lookin a lot better than it did with VSTs

Cheers
KO

 

[SteveD]

I got confirmation just today that Cakewalk expects to have this fixed in the next free point release. I can only assume it may require one from UA as well if the problem is on both sides.

Until then... I skipped the $149.00 discount on the Precision Multiband because I won't upgrade from UAD-1 v3.9.

STILL HAVING ERR=21 WILL BUY NO MORE PLUGINS UNTIL THIS IS RESOLVED

 

[yaknski]

Hey all. I took a time out from my left brained activities because the err=21 messages were driving me nuts. I have resumed the madness:

1)UADv4.1.0 works well....for awhile and then err=21 issues.

2) UAD V4.0. w/ VST plugs working well, so I haven't tried V3.9 lately.

I love Sonar 5 and the UAD-1 plugins but not the headaches.

Cakewalk and UA - please fix this problem before my head explodes!!!

STILL HAVING ERR=21 WILL BUY NO MORE PLUGINS UNTIL THIS IS RESOLVED

 

[yaknski]

[quote="guitardood In the mean time, does anyone know if there a way to go back to 3.9 drivers and still use the 4.1 plugs?[/quote]

You can't use PL, , PEq, Roland chorus, Roland DimensionD, PMB with V3.9 (they areV4.0 and V4.1 releases).

 

[guitardood]

Some, maybe good, information.

Hey Folks,
I got so flustered with the error messages that I decided to go back to basics and look at what could possible be triggering the problems. Believe it or not, I was able to work an entire session this evening and not a one err=21 message over-using the 4.1 version. Here's what I did:

Went to device manager->view->resources by type, and check the IRQ usage of the 2 UAD-1 cards. They were on independent IRQ's(18,21). I was thinking that maybe a single UAD-1 driver loaded on the system was probably getting confused getting IRQ from both cards at different IRQ's and decided to play the swap game. I wound up with BOTH UAD-1 cards on a single shared IRQ(also shared with USB by the way), and now everything seems to be OK. I'm not sure if this will help, if this was the problem, or if it is really fixed, but it seems to be working great for now. Hope this helps some of you guys.


Later,

 

[yaknski]

Guitardood..

Guitardood,
Are you still having good results with V4.1after changing IRQ's to equal values?

If so, how did you change the IRQ setting? Mine are set at 23,20,21.

 

[SteveD]

Fingers crossed for a stable UAD-1 v4.2 driver with no \"err=21\" kiss of death.

Again... Sonar 5.0.1 with UAD-1 v3.9 is the most stable combination here. 99.9% error free... and very stable.

Here's hoping... but I think the problem is with Sonar's PDC implementation.

If this is fixed... UA's got my money for the Roland/DimensionD/CE-1 bundle as well as the Precision Multiband... but not until the \"err=21\" issue is resolved.

Looking forward to reports from others. :roll:

 

[guitardood]

Hey Yaknski,
The best way to check on IRQ sharing at the hardware level is to check you mobo manual to find out which slots share IRQ signals and make sure your UAD-1 are in slots that share physical IRQ. Windows in ACPI mode doesn't give realistic info about IRQs because of their rerouting tricks. I've been running with this setup since my last post on the project that was constantly giving me problems and haven't seen an err=21 yet.

BTW, it also seems that using sound forge 8 while sonar was open with the cards in non-shared irq slots seems to be the combo to hose the cards. And for whatever it's worth, this definitely seems like a UA driver problem with multiple apps and/or cards simultaneously.

L8R,