Precision Multiband a greedy hog

[bulls hit]

Now that Cakewalk have released a beta VST wrapper to resolve the err=21 problem, I've availed myself of the discount and got the mastering bundle.

If I insert the multiband on a track (no other uad plugs in the project) & press play, the perf meter says 29% cpu, 41% memory, then the cpu figure drops to 0 and the project won't play. Not a flicker.

The only way I can get it to play is to disable the multiband, press play, then enable it after it's started playing. This introduces a stutter as it kicks in, which I don't get with any other uad plug.

I can add the EQ and Limiter in there as well no probs, as long as I wait until after pressing Play to enable the multiband. Withh all three going, the memory is still only showing 42%, and the cpu 46%. The Cakewalk cpu is showing 9%, so there doesn't seem to be a resource problem. I've got a 3.5GHz P4 which has been plenty fine up till now.

This is on V4.2, with a latency of 1024 samples.

Anyone else seen this? Any known workarounds?

 

[secretworld]

could be a plugin delay compensation isue, as the multiband has an enormous latency (works fine in cubase sx2)

 

[billybk1]

The only way I can get it to play is to disable the multiband, press play, then enable it after it's started playing. This introduces a stutter as it kicks in, which I don't get with any other uad plug.

I can add the EQ and Limiter in there as well no probs, as long as I wait until after pressing Play to enable the multiband. Withh all three going, the memory is still only showing 42%, and the cpu 46%. The Cakewalk cpu is showing 9%, so there doesn't seem to be a resource problem. I've got a 3.5GHz P4 which has been plenty fine up till now.

This is on V4.2, with a latency of 1024 samples.

Anyone else seen this? Any known workarounds?

I have not seen this behavior. I am using v4.2 and usually mix, in SONAR @ 1024 (23.2msec). I also use a Delta 66 with the DMA buffer size @ 64 and use the latency buffer slider to adjust latencies, on the fly, in WDM mode.
I can use the Precision Mastering EQ, Mastering Multi-Band & Limiter, as an FX chain, on the master bus, without any performance problems. You may want to re-check that the PMB, has it's "Enable Delay Compensation" box checked, in it's "VST Properties".

I have similar resource usage, using my (2) UAD-1 cards:

DSP:26-27%
Mem: 19%

With very minimal native CPU usage.
I am using SONAR 5.2 with an early v4.5.3 beta, of the VST adapter.
The last beta version caused my native CPU usage to increase a lot while using the UAD-1 plugins, so I did a system restore, to the previous version. I have never had an error=21, so I will stick with what is working right now.

 

[ByronSanto]

Sonar 5PE / Precision Multiband Bug

I have the same problem and have contacted UA about it. They are working with Sonar on it.

The Multi will work IF there is only two or less stereo tracks in your song file. If you add a third it brings Sonar to a hault.

 

[bulls hit]

Thanks for the helpful suggestions guys.

I've checked the delay compensation and it is on OK. Maybe the problem is due to a side effect with that beta wrapper. It's wierd, the multiband is the only plug this happens on

 

[billybk1]

Do you have any other host apps to try the PMB in, besides SONAR?
Then you would be able to narrow it down to the beta VST wrapper, if it works correctly. I also use my UAD-1 VST plugins in ACID Pro 6a & Sound Forge 8. Most times, when I use the Precision EQ & Multiband, it is with Sound Forge 8, when I am massaging (mastering), my final 24/44 stereo mixes.


Cheers,

Billy Buck

 

[bulls hit]

Good thinking. I just tried it in Project 5 and it does exactly the same thing. Of course P5 would use the same wrapper. It also glitches at the end of a loop in a P5 project

 

[ByronSanto]

The problem is caused by Sonar's Delay Compensation.

Inserting the PMB on tracks causes Sonar to stop. On buses it seems to works.