no, it works fine with out the card. it only does it when a pluggin is active.. mainly, i put a few LA2A's on, then i go for the reverb and it starts.

Is this a constant "gapping" in the audio, like a stutter, while employing UAD-1 plugs in a project? I may get a brief hesitation in the audio when initially installing or deleting plugins, but it is not persistant. What audio card are you using? What host/audio card latency are you using? You are using the DX UAD-1 plugins, right? I am using the latest UAD-1 3.2 DX versions, in my DAW, and except for the ubiquitus "CPU munching" when using (7) or more PPI's in a project, the UAD-1works and performs flawlessly.

Billy Buck

WinXP Pro (Standard PC)
PIII 1Ghz
ASUS CUSL2-C
512MB
Delta 66 (ACID40fix)
UAD-1 3.2 DX

Delta & UAD-1 on their own IRQ'S.

Sounds to me like the CPU munching problem that most of us suffer from. Open you task manager in Windows and monitor you CPU usuage while playing back the project. The UAD-1 is not supposed to use much of your CPU, but will suck a ton of it usually when UAD-1 is > 60-70% loaded (this seems worse in 3.2 than it was in 3.1). Try disabling the UAD PPI's and then enabling them when playing back and see if you CPU utilization goes down.

This is an annoying problem......it would sure be nice if UA would fix it sometime in my lifetime. I know there was a user here that claimed he didn't have the CPU munching problem, but he also stated that he used very little of the UAD-1 processing. I found that if I stayed under 60-70% UAD usage, I did not see the munching problem.

it is a constant stutter. i am using a motu 2408 mkIII. by "card latency" i assume you mean buffer settings? i have moved it to all the different settings, still nothing. it wasnt quite as bad after i adjusted my playback buffer in vegas to about .095. i keep getting a "buffer mismatch" message as well. i am using DX versions.

Ahhh, the buffer mismatch problem might be the key to your issue.
For the UAD-1 plug-ins, you cannot use them in an FX chain with other plugins that do not maintain sample constancy. Some plugins don't provide the same number of output samples as the number of input samples they receive. The UAD-1 does not like this situation and will cause the buffer mismatch problem. These types of plugins also cause issues with Vegas' realtime input monitoring.
If you read the UAD-1 notes/application read-me they state this and you have to remove the offending plug-in from the chain.
Try doing some tests with only the UAD-1 plugins as your FX and see if this helps.
Also, I've gotten the buffer mismatch problem when I have my ASIO buffer settings too low or high. If you're not using ASIO mode, try that. Are you using ASIO or Windows Classic Wave Driver? For either 0.095 is very low. For Windows Classic Wave try setting it to 0.75 or 1.0 seconds.
For ASIO try 96ms (which is where I'm at and working well).
B.

In my experience, using anything other than low latency audio drivers with the UAD-1 and a mutli-tracking app, will be problematic. When using Vegas 4 or ACID Pro, I have my Delta 66 in ASIO mode and never any higher than 1024 samples (23.2msec) I have found the "sweet spot" to be @ 256 samples (5msec). The only exception, is Sound Forge, where the higher latency MME drivers work just fine. FWIW, when using SONAR (another DX host mutli-tracking app), using the UAD-1 in either ASIO or WDM mode works best. Try using Vegas in ASIO mode @ 1024 samples or less, preferably 256. If your system is setup properly, once you set your audio card and host app to match (buffer sizes), close and re-open Vegas. You should now be able to use multiple UAD-1 plugins in Tracks, Aux buses and on the Master without mismatched buffer size error messages poping up. When they do pop-up, it is an indication that your host app, audio card and UAD-1 are not matched correctly. If all three are not matched exactly, you will encounter problems with mis-matched buffer sizes.

Billy Buck

i am using vegas 3.0, so i do not have the option of using ASIO. i noticed the uad-1 buffer setting is at 2048, and i cannot change it. does it get this number automatically from your app and hardware settings?
i will give this stuff a go tonight.

Vegas 3, oops, ......oh I just took it for granted that you were on V4. Yeah, I could never get V3 and the UAD-1 to work right together. Like I said, the MME drivers just don't cut it. Fortunately, V4 with it's ASIO capability, was released around the same time that I got my UAD-1. I have not even bothered with V3 since. V4, is so much better than V3 anyway's. With it's live input monitoring, you can even use the Nigel amp effects plugin in real-time. With my UAD-1, Delta 66 and V4 setup @ 256 samples (5msec), using ASIO mode, I can even play the Nigel with real-time response. In fact, I do not notice any difference in response(delay) when playing my Les Paul through the Nigel or through my external Line 6 POD. Great tracking either way! My advice, if you want to effectively use your UAD-1, upgrade to V4, post haste!

Billy Buck

crap, i HATE upgrading!!

hey fishtank,
just saw my first CPU munching issue last night with version 3.2 (i'm the one who hadn't seen it yet). I added dreamverb to my UAD-1 load that had several 1176s and other stuff. add me to the list of the annoyed!
bgc

how do i convert milliseconds to samples? vegas just has a little bar with milliseconds for buffer settings.

Are you talking about the "User Recording Latency Offset" in Vegas 3?
I would not even bother, I tried using that to sync with the UAD-1 in V3, with no success. Once you have solid low latency ASIO drivers & V4 installed, the automatic delay compensation (which works great in V4 with the UAD-1)
talks care of any latency issues, well.....automatically, once you you have your host app and audio card at the exact same buffer setting. There is no reason to even touch the "User Recording Latency Offset" when using the UAD-1 with V4. The Advanced Audio Configuration tab in V4, makes it real easy to setup. It has the buffer sizes in both msec & samples. Try out the demo to see what I mean. I wasted a lot of hours trying to get V3 to work right with the UAD-1, not until I got V4 and had it using my Delta 66, in ASIO mode, did Vegas & my UAD-1 become compatible with each other.


Billy Buck

The number of samples is based on the current sample rate. For ASIO drivers all work in samples, and you will be able to set this there.

For Wave Classic, Mapper, and DirectSound Mapper modes, the over all buffer size is set in milliseconds only.

For wave classic drivers you can hit the advanced button and set the default buffer sample size to a specific number of samples. However, unless you are using native Wave MME drivers (not WDM based) you should NOT set this as it will tend to degrade performance. If you are using a card from Echo and have it set to use Purewave mode - which is a native Wave MME driver mode - then you SHOULD enter the Purewave Buffer setting in the advanced dialog. Other cards that have Native Wave MME drivers are the RME series of cards and they can benifit from making this advanced adjustment.

Note, that overall buffering will still be the millisecond setting you make, but it will be broken down into the advanced setting you make. This provides a lower latency , but permits the audio engine to be smarter about how it works with buffers.

With ASIO based drivers, the ASIO driver buffer setting is what drives the entire audio engine.

Peter

well, i downloaded the demo for 4.0 and installed the motu ASIO drivers and all the problems are gone. but, the i only had (2) la2a's running, and (1) dreamverb, and the pci cpu was at 42%. is that really all this card has?