-
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.
Sonar 5.0.1 and Uad 4.0 Error 30 back again
- Thread starter Briguy
- Start date
Well... it IS annoying. And the err=30 tends to happen after you change the cards buffer size.
For me the error happens once and then everything works fine again.
However, I have also seen the err=21 rear its amazingly ugly head a couple times too since the recent upgrades.
It it happened more frequently I would either ditch the UA card or Sonar, I am not sure which since I love them both.
cAPS
For me the error happens once and then everything works fine again.
However, I have also seen the err=21 rear its amazingly ugly head a couple times too since the recent upgrades.
It it happened more frequently I would either ditch the UA card or Sonar, I am not sure which since I love them both.
cAPS
Right I get the err=30 on changes to latency/buffer size, as far as I can tell it has no ill effects. Click the "Ok, so what?" button and continue.cAPSLOCK said:Well... it IS annoying. And the err=30 tends to happen after you change the cards buffer size.
...
However, I have also seen the err=21 rear its amazingly ugly head a couple times too since the recent upgrades.
...
cAPS
The real bugger is the err=21 that causes the UAD card to get lost. I started getting those with Sonar 5.0.0 and UAD 4.0 after I loaded the Java JRE, I then unloaded that and have not seen them since. Sonar 5.0.1 w/ UAD 4.0 has been reasonably stable, just an occasional err=30; I'm happy.
(Please don't ask why I was loading Java onto my DAW
Hard_At_Work
Member
Err=21 here as well
This was true for me as well even after MANY conversations with both cake and UA. I think the larger problem is Basic Code issues between Sonar and UA products. Even after all the recent revisions of both products.
After extensive searches, it seems there are VERY FEW sonar users that have satisfactory results with the UAD-1. There do seem to be some users that were lucky enough to have bought the 'right' combination of MOBO and Memory and have had fewer issues but, without question, there are consistant and basic issues between UAD-1 and Sonar.
After 2 years of experimentation between Sonar and UAD-1 on 4 different motherboards and extensive calls to both tech departments, still no 'consistant' working system that does not involve MAJOR workflow compromises. This is really unfortunate.
Our other tracking room just added Nuendo to their AMD 64 system ( same system as ours ) and after exporting all the tracks in OMF to their system, the UAD-1 stuff works flawlessly. No errors of any kind even when the card is fully loaded and mixed with many other plugs.
I would pay dearly to just have the UA guys and the Sonar guys sit down in one room and hash it out once and for all!!! Jeeeze.
Nuendo is a great tool and for surround is the real deal but Sonar is much more practical from a workflow/creativity point of view.
I beleive that soon Sonar will become a viable professional tool and the UA guys are really missing some market share here by not addressing the obvious compatibility issues between the two.
Just my .02 cents :|
This was true for me as well even after MANY conversations with both cake and UA. I think the larger problem is Basic Code issues between Sonar and UA products. Even after all the recent revisions of both products.
After extensive searches, it seems there are VERY FEW sonar users that have satisfactory results with the UAD-1. There do seem to be some users that were lucky enough to have bought the 'right' combination of MOBO and Memory and have had fewer issues but, without question, there are consistant and basic issues between UAD-1 and Sonar.
After 2 years of experimentation between Sonar and UAD-1 on 4 different motherboards and extensive calls to both tech departments, still no 'consistant' working system that does not involve MAJOR workflow compromises. This is really unfortunate.
Our other tracking room just added Nuendo to their AMD 64 system ( same system as ours ) and after exporting all the tracks in OMF to their system, the UAD-1 stuff works flawlessly. No errors of any kind even when the card is fully loaded and mixed with many other plugs.
I would pay dearly to just have the UA guys and the Sonar guys sit down in one room and hash it out once and for all!!! Jeeeze.
Nuendo is a great tool and for surround is the real deal but Sonar is much more practical from a workflow/creativity point of view.
I beleive that soon Sonar will become a viable professional tool and the UA guys are really missing some market share here by not addressing the obvious compatibility issues between the two.
Just my .02 cents :|
It surprises even me that the product I would be likely to give up first between Sonar and the UAD1 is the UAD1.
I mean I would hate to part with it for many reasons, but there are more and more viable choices coming around for good sounding compression, and that is the one area that native has really lagged behind in comparison to the UA plugins.
Still. I have few enough problems to be fairly satisfied with keepiong the UA stuff running with the occasional Err=21.
Sonar's workflow and flexibility are unequalled in my opinion.
I have a pretty firm feeling the the way Cakewalk has chosen to handle VST support (kinda badly really) is the main reason for the problem combined with the latency/PCI bussing issues of the UA hardware.
We may never see a solution...
cAPS
I mean I would hate to part with it for many reasons, but there are more and more viable choices coming around for good sounding compression, and that is the one area that native has really lagged behind in comparison to the UA plugins.
Still. I have few enough problems to be fairly satisfied with keepiong the UA stuff running with the occasional Err=21.
Sonar's workflow and flexibility are unequalled in my opinion.
I have a pretty firm feeling the the way Cakewalk has chosen to handle VST support (kinda badly really) is the main reason for the problem combined with the latency/PCI bussing issues of the UA hardware.
We may never see a solution...
cAPS
Thanx for your input, I mostly see the error 30 when I have to reset Sonars engine. I don't recall changing buffer sizes when this has happened or even on a previous session. I really wouldn't like to get rid of my due to this small issue, As long as the plugins are still working after that message pops up I can deal that. Again I do agree that Uad and cake should seriously sit down and finalize that issue(s). Thanks again
New here to forum.
I was running Sonar 3 PE(lastest version, whatever that was) and 1 UAD-1 card v4.0.0 on a Sweetwater Creation Station Pro (stock except upgraded from 1GB to 2GB RAM) without any problems (except running UAD-1 to 91-95% on some projects.)
As such, I added a second UAD-1 to system then started getting err=21 and err=30 messages. Sweetwater support suggested I upgrade to Sonar 5 or at least Sonar 4 (which I had but didn't load).
Got a clean install of Sonar 4 PE and updated to latest version. System seems to work fine and then all of a sudden err=21 messages which go away after reboot.
I guess I was dreaming that my system would be stable as I did my research before buying each piece. What I'm reading here is conflicts and instability between UAD-1 and Sonar. What's weird is my initial and less powerful set-up worked w/o instability.
I was running Sonar 3 PE(lastest version, whatever that was) and 1 UAD-1 card v4.0.0 on a Sweetwater Creation Station Pro (stock except upgraded from 1GB to 2GB RAM) without any problems (except running UAD-1 to 91-95% on some projects.)
As such, I added a second UAD-1 to system then started getting err=21 and err=30 messages. Sweetwater support suggested I upgrade to Sonar 5 or at least Sonar 4 (which I had but didn't load).
Got a clean install of Sonar 4 PE and updated to latest version. System seems to work fine and then all of a sudden err=21 messages which go away after reboot.
I guess I was dreaming that my system would be stable as I did my research before buying each piece. What I'm reading here is conflicts and instability between UAD-1 and Sonar. What's weird is my initial and less powerful set-up worked w/o instability.