UAD 4.1 w/ Sonar 5.0.1 - It got worse: err=21

[ed_mcg]

I just tried UAD-1 4.1 w/ Sonar 5.0.1 and, for me, it's a major regression. I'm getting err=21 within a couple minutes of running, four times in a row.

I've just reverted back to 5.0.1/4.0; I get a rare err=21 with this combination; infrequent enough to deal with.

Looks like I won't be using the coupon.

 

[scottfa]

Well, I am now getting the ERR=21 message. I have to reboot my machine to get rid of it. I am using Sonar 4.04 with a Gigabyte AMD motherboard and I am not using a dual core CPU(at the moment). I am wondering if the ERR=21 is a Sonar/UAD problem or possibly a UAD/Gigabyte/Nvidia 3 problem. That is, will changing the motherboard help this situation? I do NOT experience any crackling etc.

 

[ed_mcg]

Yes, the err=21 is a Sonar w/ UAD-1 issue. It is not mother board / procesor specific issue as I've heard of it on a variety of AMD and Intel users.

And, right, it requires a full reboot. This is why is causes such frustration with users that have encountered it.

 

[scottfa]

Sure seems like this has been going on for a LONG...... time. Anybody have a clue as to what causes the problem? Mine happened the last time when I added a Pultec. Honestly, I am getting sick of dinking with the computer and not making music. All the new stuff sounds great, but fooling around with UAD and Drumkits from Hell and Sonar........etc I feel like I am back in my old job of technical support. At least I got paid to do that work.

 

[yaknski]

I had err=21 messages too with Sonar 5.0.1 and UAD-1 4.1, when I'd open a certain project. The problems occurred after I installed a 2nd UAD card and then upgraded to V 4.1.

What worked for me was deleting all UAD plug-ins on that project, then re-inserting VST wrapped versions of the UAD plug-ins back to the tracks. I think I was having buffer conflicts between my native plugins and the UAD plugins. Whatever it was, this fixed my problem. When the error would occur, 1 or both of my UAD cards would be disabled when I opened the UAD panel.

Now everything is working flawlessly.

Mother board:Asus w/865PE Chipset
CPU: Intel P4 3.2GHz/800MHz FSB
Hard Drive(s): Glyph Seagate 80GB & 200GB SATA
RAM: 2GB
Win XP home sp1
Sonar 5.0.1
x2 UAD-1 v4.1
MOTU 828 mkII

 

[Hard_At_Work]

I had to revert back to the DX versions of the UAD-1 stuff to get them work correctly in Sonar 4.04 and Uad-1 4.0. Had to desable turbo to get that far. Now with the DX versions things are working great! So now....I terrified that UA is DROPPING DX support.....WHATTTTTT?
Finally get a workiing setup with Sonar and there Dropping the line!!!

Jeeze.

 

[Blackdogstudio]

This is one of the reasons I am leary about upgrading to SONAR5. The UAD-1's are working so good with SONAR 4.0.4 that I may never upgrade. One thing I noticed was the new SONAR VST adapter caused plug-ins not to show up or function correctly so I reverted back to the 4.0.3 adapter and everything is fine now. Another thing is when I first installed the 4.0.4 patch it was the first time that I had ever seen an error 21 msg. Removing the plugs from the fx bin and then re-installing them would correct the problem but what a PITA that was. As you know, alot of time is spent getting settings just right and having to start over from scratch, well I certainly understand the frustration. What I did was go to the UAD-1 meter, check the box \"limit cpu load\", move it from 95% to 100%, then un-check the box. No more error 21 msg's after that. Weird, I know, but it worked.

 

[ranchdip]

Dangit.... This has got to stop UA & Sonar!!! WORK IT OUT! The CPU spikes are killing me and this err=21... This shouldn't be an issue by now.

 

[JasonMorris]

If this does not apply to your problem, I appologize.. but this patch from MS helped me and my dual core system out:

http://support.microsoft.com/default.as ... -us;896256

 

[daverich]

I sold my uad because of this problem.

Sorry to see it's getting worse.

C'mon UAD - Release a new better working card or go native!

Kind regards

Dave Rich

 

[yaknski]

UAD-1 V4.1 unstable with Sonar 5.0.1

UAD-1 V4.1 is now unstable for me too with Sonar PE 5.0.1 with err=21 messages, and both of my cards becoming disables until a reboot. UAD V4.0 is stable for me with Snaor 5.0.1. So no Precision multi-band for awhile for me until UAD sorts it out. My native CPU goes nuts with v4.1, then if I disable UAD during playback and then re-enable it my native cpu meter goes from 80% to 8 % , what the f????%^&$$*! I also verified this by running Win XP's system resource meter from the task manager. This is with all VST plugins and no mono versions.

V4.1 doesn't seem to get as good miles per gallon as V4.0. My hunch is that V4.1 requires more UAD system resources to run than V4.0 did.

UAD, I love your products and you guys have been great but maybe it wasn't such a good idea to release V4.1 then close customer support for the holidays. Certainly you guys deserve some time off. I bought the Precision Multiband plugin but am afraid to use V4.1 now. Maybe I should've waited?

Anyone else?

 

[scottfa]

Well, after updating to UAD 4.0 and Sonar 4.04 I get err=21 messages all the time. Often, as soon as I start a project. I reverted back to 3.9 and still get them. This problem seems to get worse on my machine as time goes by. Either I have to get rid of the UAD or Sonar. And I am not dumping Sonar. Is it worth bringing this up to UA tech support? They obviously know about the problem. Maybe the Sonar based users of the UAD card are too few in number. I can't believe that UA doesn't have some idea as to what the problem is. If not, then it is time to get rid of the card and buy URS or something.

 

[jaydrake]

It worked for me...

Check this thread of mine:

http://www.chrismilne.com/uadforums/viewtopic.php?t=3915

So far, so good.

 

[vksf01]

Re: UAD-1 V4.1 unstable with Sonar 5.0.1

hi, i fortunately didn't get the err=21 messages but i did experience the major CPU munching in sonar using v4.1. i had to drop back to v3.9 to get it to work properly

here's my rant http://www.chrismilne.com/uadforums/viewtopic.php?t=3924

UAD-1 V4.1 is now unstable for me too with Sonar PE 5.0.1 with err=21 messages, and both of my cards becoming disables until a reboot. UAD V4.0 is stable for me with Snaor 5.0.1. So no Precision multi-band for awhile for me until UAD sorts it out. My native CPU goes nuts with v4.1, then if I disable UAD during playback and then re-enable it my native cpu meter goes from 80% to 8 % , what the f????%^&$$*! I also verified this by running Win XP's system resource meter from the task manager. This is with all VST plugins and no mono versions.

V4.1 doesn't seem to get as good miles per gallon as V4.0. My hunch is that V4.1 requires more UAD system resources to run than V4.0 did.

UAD, I love your products and you guys have been great but maybe it wasn't such a good idea to release V4.1 then close customer support for the holidays. Certainly you guys deserve some time off. I bought the Precision Multiband plugin but am afraid to use V4.1 now. Maybe I should've waited?

Anyone else?

 

[yaknski]

Hey vksf01,

I believe the host CPU gone wild issue maybe this turboDMA issue from UAD-1 tech notes -

\" (TurboDMA) Most systems will experience increased or identical performance in version 4.x with the new TurboDMA mode. Some systems may encounter new performance issues with version 4.x such as higher host CPU load, dropouts, or glitches in disk rendering. In this scenario, the TurboDMA feature can be disabled with a special registry key provided by UA technical support which will revert performance back to version 3.9.0 levels under version 4.x. \"

which is located at (scroll down 1/3 page) - http://www.uaudio.com/support/software/ ... eswin.html

also check thread at -http://www.chrismilne.com/uadforums/viewtopic.php?t=3704

I've emailed UAD support re: this, they're out of the office until 1/2/06 and I'll expect that they are slammed when they get back.

During playback of a project note your host cpu level, then disable and re-enable the UAD-1 and then see if your host cpu level drops a significant amount like it does on mine.

 

[vksf01]

thanks for the info. what i noticed (at least with v4.0, was that if turbodma was disabled, when i tried to do a "fast bounce" in sonar, it took even longer than a realtime bounce!).

in the meantime, until someone reports otherwise, i'll stick with v3.9. i really don't have the energy to screw around with my computer (i've had 2 hard drive crashes recently, but that's another story)..

thanks anyway!

Hey vksf01,

I believe the host CPU gone wild issue maybe this turboDMA issue from UAD-1 tech notes -

" (TurboDMA) Most systems will experience increased or identical performance in version 4.x with the new TurboDMA mode. Some systems may encounter new performance issues with version 4.x such as higher host CPU load, dropouts, or glitches in disk rendering. In this scenario, the TurboDMA feature can be disabled with a special registry key provided by UA technical support which will revert performance back to version 3.9.0 levels under version 4.x. "

which is located at (scroll down 1/3 page) - http://www.uaudio.com/support/software/ ... eswin.html

also check thread at -http://www.chrismilne.com/uadforums/viewtopic.php?t=3704

I've emailed UAD support re: this, they're out of the office until 1/2/06 and I'll expect that they are slammed when they get back.

During playback of a project note your host cpu level, then disable and re-enable the UAD-1 and then see if your host cpu level drops a significant amount like it does on mine.

 

[SteveD]

Well I came here tonight to do my homework and hopefully use my coupon (only 2 days left) and spend my $102.00 on the 4.1 upgrade and the Precision Multiband.

I've been waiting for over a year to complete my precision mastering suite with what I knew was coming... the Precision Multiband.

It breaks my heart... but I'm not going to take the deal or even TRY version 4.1 because I love using Sonar 5.0.1... and I can tell from what others are reporting that this marriage wasn't made in heaven.

I've got 2 UAD-1 cards and my system is stable as long as I don't max out on UAD-1 plugins... then come the dreaded err=21 reboots.

Unacceptable. I won't stand for it.

Sorry UA... you would have had my money tonight... but there's no deal sweet enough if it means an unstable system.

I can't afford it.

None of us can.

I've been a faithful promoter of UAD-1 powered plugins, but I'm still on v3.9 because that's what works with my system.

Hope you guys get this sorted... 'cause that's when you'll start getting my money again... not before.

 

[Hard_At_Work]

This is exactly the same senario with us at our posting house.
UA really need to read these forums.
UA is loosing potential customers and income.
FIX THE SONAR ISSUES AND EXPAND YOUR MARKET.

 

[cAPSLOCK]

I quit buying plugins as soon as the err=21 issues started cropping up. That was with a P4 system by the way, though I use a A64 now.

Stability has been up and down between updates from UA and Cakewalk, but the problem has never really gone al the way away for me.

I still use the 2 UAD1 cards I have, but here is a list of UA plugins I have NOT bought directly because of the err=21 issue:

Precision Limiter
Precision EQ
Precision Multiband
Roland Dimension D
Roland CE-1

I will also not buy any upcoming effects UA makes if this problem is not resolved.

I dont care that UA has discontinued the DX versions. They were nice when that was all we had, but the VST versions have more recently been better since Cakewalk has actually updated the adapter while UA just let 200 year old code (a previous version of the same VST adapter) grow more and more stale.

I don't have time to be jacking with replacing my UA plugins with one version from the other (like VST to DX).

I understand that this problem is more common with SONAR than other hosts (though it not only happens with other hosts, but even has been reported happening on the Mac!). In fact the problem might be partly a problem with the way Sonar handles VST plugins.

But for me... in the end... Sonar is more important software than the UA plugins which little by little pale in the face of native competition.

The day there are a few more high quality compression options out there is the day I seriously think about pulling the UA hardware out of my machine.

I LOVE my UAD1s and I still use the LA2A and 1176 VERY frequently... But each time I use a UA plugin I have this little feeling of 'boy I hope this doesn't screw up this project' down in the side of my subconscious.

I hate that it has turned out this way for some of us.

cAPS

 

[jaydrake]

Capslock,

Not sure if you've seen my thread, but err-21 is a thing of the past on my system ever since I tried using Uad-1 DXI versions only. This is on HUGE projects with tons of plugins. I'm using 4.0 w/ Sonar 5.01.