Well I thought let's see if upsampling makes one of my songs sound better.
 I have found on my win7 32 bit machine that if there are any UAD-1 plugins in the file, enabling upsampling on any vst whether or not it is associated with a track that contains a UAD plug or not, will result in an out of storage space error upon export. This condition will persist until Sonar is closed and restarted. Removing the 3 UAD plugs (2 instances of LA-2A on tracks and one Pultec on the 2 bus). If I open the file and remove those UAD plugs then I can upsample and export ok.
 
My asio buffers were 128 and I jacked them to 1024 but that didn't help.

UAD plugins don't like different buffer sizes so it definitely wont work with them. i.e. they have a limitation that *all* UAD plugins have exactly the same buffer sizes. Of course if you want to upsample one of them this won't work.
So don't do that :)
Edit: Wait you said you aren't even upsampling the UAD plugins? Thats weird that they would complain since their buffer sizes aren't being changed. One thing is possible however - if the UAD plugins in the same bin downstream from an upsampled plugin its possible that it might get a a buffer thats smaller than the configured buffer size. Check if moving the UAD plug to a different bus solves it.

You're up late.
 
Tomorrow I will do some testing with a plain file and a few plug ins to get a better picture for ya.
 
 

Anderton

mudgel

Anderton
This is pretty much explained in the eZine. I would recommend reading it to people who want to know more.

Feel free to come and read it to me any time. Though a little notice before you visit would be nice. Thanks.

Ha! Yes, I just noticed the ambiguous phrasing and changed it. Although I suppose we could have a group Skype meeting and someone could read it to everyone else 

I'm glad I captured the truth for posterity. Or as they would say in the Coffee House; for posterior.

Well I spent the better part of the day monkeying around with upsampling.
If I used a small file than none of the problems I had initially with the uad were not there anymore except if I tried to enable upsampling on the uad plug I got a buffer mismatch error.
 
As for my song with lots of tracks and plugs I was able to upsample most all the vsts just not the uad plugs (or suffer the buffer change error, but all in all upsampling seems like a hit. The mix is less cloudy and much more defined and open sounding compared to the 44.1 k version from before.
 
 
 
 

Thanks for the update. I'm curious what happens if you upsample *all* the uad plugins in the project. Or move then to a sep bus that has no other resampled plugs in it.

I'll try that sometime today.

Ok as you suspected, enabling upsampling on all the uad plugs works without error.
Disabling upsampling on the pultec on the 2 bus while leaving the La2a's upsampled on bass and vox result in the buffer size mismatch error.
 
So I guess testing the uad plugs on their own track would be unnecessary?
 
 

Yeah UAD plugins require all the active plugins to have the same buffer size. Its a limitation of the UAD hardware.
This is contradictory to upsampling that requires the upsampled plugin to run at a higher buffer size.
Putting *all* the UAD plugins in a single bin and upsampling the first one would also work.
I would also expect that if the UAD plugins were in an independent bin and none of them were upsampled it would work irrespective of other upsampled plugins in the project.

Noel Borthwick [Cakewalk]
 
I would also expect that if the UAD plugins were in an independent bin and none of them were upsampled it would work irrespective of other upsampled plugins in the project.

And you suspect correctly as that's how it was getting exported last night, most, if not all VSTs upsampled and no uads upsampled.