Vegas 4 + UAD-1 = Crashes

fishtank wrote on 7/27/2003, 11:49 AM
I just recently installed my new UAD-1 and love the sound of the plug-ins and added DSP power I now have. The problem is that V4 is now unstable and crashes fairly easily. Is anyone else having these problems?

V4 currently has a great deal of issues that need to be resolved, but the one problem I didn't have was crashes - until I added the UAD-1. Is this a V4 issue or a UAD driver issue?

Comments

bgc wrote on 7/27/2003, 1:30 PM
Do a search on UAD here in the Vegas forum. Several people have tried using the UAD-1 with limited success. My impression is that there may be issues with the Direct-X wrapper UAD provides.
PipelineAudio wrote on 7/27/2003, 4:19 PM
UAD-1 has a LOT of issues. Dealing with their tech support will make you realize just how lucky we are to have Peter, Dave and the rest of the Sonic Foundry staff to deal with!
stakeoutstudios wrote on 7/28/2003, 3:58 AM
are any of you getting total freezes and lockups with the UAD1?

I replaced my power supply to see if it was that... now I have a hefty 400W Zalman power supply and I'm still getting lockups...

Quite infrequent, but irritating nonetheless.

Jason
billybk wrote on 7/28/2003, 6:45 AM
No, I can't say that I have ever had a total freeze or lockup(BSOD) while actively using the UAD-1 with Vegas. But, I do have two re-occurring known issues since the 3.1 update:

1) Excessive native CPU usage when using the DX PPI's in a project. The disable/enable trick from the PM, during playback is a temporary workaround, to reclaim the native CPU back.

2) Audio gapping on exports: It seems that when using PPI's(particularly the Pultec & LA2A) on the master main during an export will result in clearly defined gaps( 1 or more gaps of 1000-4200 samples in length in a typical 3 minute long render), easily seen using a stereo editor, like SF6, zoomed in to the 1024 sample level. It sounds like an audio click on playback. It appears that to avoid this gapping on renders, that you need to export @ 128 samples(2.9msec). Unfortunately, neither Vegas nor ACID Pro can export @ that latency. My workaround for this is to avoid using the PPI's on the master main when exporting and then use SF6(audio chainer) to apply any final PPI touches.

UA is aware of these problems/bugs and hopefully is working to get a fix in time for the next 3.2 update.


Billy Buck




fishtank wrote on 7/28/2003, 11:56 AM
I have not had any freezes or lockups, but usually get an error message and that annoying looped *buzz* from my audio card. I close down the apps and reboot at that point. This has happened when I was soloing a track etc. I just installed the UAD-1 Friday evening and had very little time to try it out - not sure how useable it will be if I keep having these crashes, though. I also get these errors about buffer size changing from time to time, but usually can keep going. I have not noticed the reported CPU munching problem as of yet.

System:

Tyan Tiger S2466 with 2 x MP1900's
512 M Corsair ECC Reg. DDR
Frontier Dakota\Montana
Matrox G550
Win 2K SP4
2 - WD800JB's
UAD-1 (in 66 MHz PCI slot)
billybk wrote on 7/28/2003, 1:38 PM
"I have not noticed the reported CPU munching problem as of yet."

fishtank,
Try loading up (7) or more DX PPI's in a project(so that the DSP usage is over 60%). Open both the UAD-1s Performance Meter and the Windows Task Manager(to monitor native CPU usage) to your desktop. During playback of your project, disable and then enable the PPI's globally from the Performance Meter and watch the Windows Task Manager's CPU monitor. If you see the native CPU usage drop, then you have experienced the native CPU munching. It's there, you just haven't been looking for it.
Also, try rendering a project, with a Pultec EQ & LA2A on the main out, to a stereo wave file. Do a couple of renders of the same project. Odds are, if you take and open that file in a stereo wave file editor, like Sound Forge 6, and zoom into the 1024 sample level and scan through the entire length, you will invaribly find at least one of your renders will have (1) or more audio gaps in them. It only seems to happen if you have PPI's(in particular the Pultec & LA2A) on the main out during export.


Billy Buck
fishtank wrote on 7/28/2003, 11:51 PM
You are correct....I do have the CPU munching!

Was working on a project with PPI DSP usage just barely over 60% as well as a number of Waves native plug-ins running and noticed crackling in the audio. I disabled the PPI's and then enabled them and the crackling went away (wasn't looking at the Task Manager, but it was pretty obvious). I repeated this several times.

This damn crashing is what is killing me. The funny thing is that the crashes seemed to go away if I worked much slower - waiting a bit before switching soloed tracks in/out, starting and stoping playback etc. I really hope they get these problems worked out soon as I would like to buy another UAD-1.
stakeoutstudios wrote on 7/29/2003, 3:27 AM
having said all this, I'm able to work around the problems just about...

I have three UAD1's with the Cambridge now... incredible amount of power!!
whr wrote on 8/1/2003, 11:21 AM
I've been having trouble with crashes recently since I had to reload Vegas. My biggest problem is that after I save a multi-track audio file that is using strings of DX FX I crash when I try to open a new file. Once in a while it will even crash while trying to play a file of tracks that have been rendered with the DX strings. I have never related this specifically to UAD1 but it is very possible that it is the culprit.