• Welcome to the General Discussion forum for UAD users!

    Please note that this forum is user-run, although we're thrilled to have so much contribution from Drew, Will, and other UA folks!

    Feel free to discuss both UAD and non-UAD related subjects!

    1) Please do not post technical issues here. Please use our UAD Support Forums instead.

    2) Please do not post complaints here. Use the Unrest Forum instead. They have no place in the the General Discussion forum.

    Threads posted in the wrong forum will be moved, so if you don't see your thread here anymore, please look in the correct forum.

    Lastly, please be respectful.

News of a possbile fix for err=21 at Sonar forum

fishkid

Member

fishkid

Member
Cool, let us know what results.
 

ed_mcg

Member
I works. It fixes the problem. And I have, perhaps, the worst case test rig: An AMD 4400+ x2 on a Asus A8v Deluxe w/ two cards. I can even run v4.2 now.


I as happy as a pig in slop! :D
 

bulls hit

Active Member
ed_mcg said:
I works. It fixes the problem. And I have, perhaps, the worst case test rig: An AMD 4400+ x2 on a Asus A8v Deluxe w/ two cards. I can even run v4.2 now.


I as happy as a pig in slop! :D
wow that's great. I'm going to try it tomorrow. Don't want to get my hopes up though
 

secretworld

Active Member
foreverain4 said:
what if i was getting error 21 with my uad1 wrapped to protools? this is a VST to DX adapter, right?
UA anounced the v2 wrapper for rtas in the latest webzine, will be available next quarter(3)
 

fishkid

Member
Yeah, it's a public beta version of Sonar's VST adapter but anyone with Sonar can join the beta testing. Knowing Cakewalk it'll be released as soon as their confident of the fix.

Things look real good at the moment. Anecdotal reports are showing up now in the beta forum of successes, users reporting that previous projects that had error 21 are now running error free. Looks like Cake and UA are are on the right track. It makes sense that it's the VST adapter as the error was specific to Sonar.

Isn't it great to see the two companies work this out for thier users?
 

cAPSLOCK

Active Member
Well it was a long and rough road, but I am just glad it got done.

It will be nice to not have to worry about this problem cropping up in front of my clients anymore.

This is, for me (believe it or not) the hugest audio news of 2006 so far. Hah.

Really.

cAPS
 

cAPSLOCK

Active Member
Fishkid:

Though it has most definately been an real issue with sonar I feel it is important to mention that it has occured with other platforms as well.

Nuendo:
http://www.chrismilne.com/uadforums/vie ... ght=err+21

Logic:
http://www.chrismilne.com/uadforums/vie ... ght=err+21


It even has showed up on Macintosh systems:
http://forum.cakewalk.com/tm.asp?m=3654 ... y=&#387241
http://www.chrismilne.com/uadforums/vie ... ght=err+21

I think combination that REALLY saw the most err=21 was Sonar+AMD+VIA chipset though. And I think it has been eliminated for everyone but the Sonar guys in the last several releases of the UA software.

I can't begin to say how glad I am that it may indeed be gone for us too finally.

cAPS
 

fishkid

Member
Hey cAPS,

Thanks for the clarification. Do you think it was more of a mobo/chipset issue or the Cakewalk VST adapter? I ask because I don't have a VIA chipset and I never got an error 21 until I went to UAD 4.0 and Sonar 5.

I'm with you, it is some of the best news so far.
Could be a bit of a windfall for UA because all those Sonar folks will now open their wallets, especially for the Neve stuff.
 

cAPSLOCK

Active Member
I hope Ron over at CW will shed some light on exactly what it was.

But for us it most surely had something to do with the VST adapter. For sure.

I was not meaning to imply that the VST adapter did not have a HUGE part to play in this mess. I think it has, thus the fix. I was only pointing out that it was not ONLY a sonar thing.

I have always had the hunch that what happens is the data that is going to the UA card was getting logjammed at the PCI bus somehow, and that the adapter was facilitating this problem. But I wonder if that's even close. The more I think about it the more it seems like it also had something to do with the initial connection between the Sonar audio engine and the card. Because come to think of it it happened most often when engaging the audio engine, or adding an effect.

Anyway, perhaps Ron will spill the beans?
 

prog_head

New Member
I hammered the UAD

in Sonar 5.2 and never once did I see the error. I have the ASUS A8V/X2 4400 combination and it now appears to be running great. FINALLY! What a relief.
 

fishkid

Member
More updates and fixes (from the Cakewalk VST Adapter beta thread) link here

\"Hi everyone,

We have just posted another update to the VST Adapter beta. This update fixes the UAD Err=21 problem, and also ensures that any bypassed or otherwise \"idle\" UAD plugins do not consume additional DSP resources.

One minor \"nit\" you may notice is that in some cases the DSP resources won't be reclaimed until after a full play/stop cycle after the plugin has been been taken offline.

Also, this update fixes a UAD Err=30 (buffer size mismatch error) which arose when changing audio buffer sizes.

Enjoy! \"

Ron Kuper


Looks like UA and Cakewalk are all over this one.


P.S. Is is okay I posted that quote here?

Edited to include link and source.
 

Akis

Sadly, left this world before his time.
Moderator
fishkid said:
P.S. Is is okay I posted that quote here?
Please provide the name/nickname of the original poster and a link to the original message and it'll be perfect!
 

fishkid

Member
Akis,

I have made it so.
 
UAD Bundle Month
Top