Correct the problem in using UAD plugins!

[V.G.]

MIXBUS32C permanently disconnects UAD plug-ins at intervals, reporting a buffer size mismatch.
Plug-ins start working again after switching on, but it takes a lot of time to turn them on and the workflow is interrupted. It is also very likely that any plug-in can be forgotten to be turned back on.
I think that the solution to this problem is not so difficult for you, because plugins, when enabled, work.

[LoganHanna]

I am also having this issue as well.


Sent from my iPhone using Tapatalk

[Dingo]

I could be mis-reading it, but the error message seems to imply that there is a buffer size issue between multiple instances of UAD within your UA setup.
Did you send the 'transmit issue report to UA' ?
Perhaps you should also write to UA and Mixbus support.

[V.G.]

I could be mis-reading it, but the error message seems to imply that there is a buffer size issue between multiple instances of UAD within your UA setup.
Did you send the 'transmit issue report to UA' ?
Perhaps you should also write to UA and Mixbus support.

I wrote both in UA support, and in MB support.
Ben knows about this problem and knows the reason for its occurrence. He wrote about it to me.
But whether it will be solved is a big question for me, because knowing about it and not eliminating it, Mixbus discredit itself.
UA plupins are an essential element of professional mixing.

[madmaxmiller]

UA plupins are an essential element of professional mixing.

You forgot to type *imho*.
MMM

[Ben@Harrison]

I think this problem is caused when you add a mono UA plugin to a stereo track. Mixbus creates 2 mono instances, and for some reason the second UAD plugin doesn't accept the buffersize. Try adding the "stereo" version of the plugin to the track, and see if you still get the error.

-Ben

[V.G.]

I think this problem is caused when you add a mono UA plugin to a stereo track. Mixbus creates 2 mono instances, and for some reason the second UAD plugin doesn't accept the buffersize. Try adding the "stereo" version of the plugin to the track, and see if you still get the error.

-Ben

When you add an AU version of a plugin, you cannot choose mono or stereo, because there is no mono version or stereo version, there is just a plugin and it becomes mono or stereo depending on the track to which it is added.
This problem occurs even in an empty session if there is only one MANALEY MASSIVE PASSIVE EQ on the Master Bus.
I cannot use the VST version because MIXBUS doesn't let me do that.
I wrote about this 4 months ago: http://mixbus.harrisonconsoles.com/forum...-7071.html
I contacted support, but the only thing I was advised to check the location of plug-ins on the disk. Of course they are located where it should be.
I contacted the UA support service and after providing all the information, they admitted that they did not see any problems for the plugins to work.
MIXBUS problem! otherwise, there would be no people with the same problem.

---

UA plupins are an essential element of professional mixing.

You forgot to type *imho*.
MMM

All my statements I do on my own behalf, and not from the public.
And I see no reason to confirm this additionally.

[doncolga]

I think this problem is caused when you add a mono UA plugin to a stereo track. Mixbus creates 2 mono instances, and for some reason the second UAD plugin doesn't accept the buffersize. Try adding the "stereo" version of the plugin to the track, and see if you still get the error.

-Ben

When you add an AU version of a plugin, you cannot choose mono or stereo, because there is no mono version or stereo version, there is just a plugin and it becomes mono or stereo depending on the track to which it is added.
This problem occurs even in an empty session if there is only one MANALEY MASSIVE PASSIVE EQ on the Master Bus.
I cannot use the VST version because MIXBUS doesn't let me do that.
I wrote about this 4 months ago: http://mixbus.harrisonconsoles.com/forum...-7071.html
I contacted support, but the only thing I was advised to check the location of plug-ins on the disk. Of course they are located where it should be.
I contacted the UA support service and after providing all the information, they admitted that they did not see any problems for the plugins to work.
MIXBUS problem! otherwise, there would be no people with the same problem.

---

UA plupins are an essential element of professional mixing.

You forgot to type *imho*.
MMM

All my statements I do on my own behalf, and not from the public.
And I see no reason to confirm this additionally.

Have you had a look at what's happening with or experimented with the pin connections? Also, a quick Google search shows this happens in other programs, not just MixBus. I found references for this error in Cubase, WaveLab, Logic, ProTools, Sony Acid Pro, Fruity Loops and Adobe Audition.

[V.G.]

I think this problem is caused when you add a mono UA plugin to a stereo track. Mixbus creates 2 mono instances, and for some reason the second UAD plugin doesn't accept the buffersize. Try adding the "stereo" version of the plugin to the track, and see if you still get the error.

-Ben

When you add an AU version of a plugin, you cannot choose mono or stereo, because there is no mono version or stereo version, there is just a plugin and it becomes mono or stereo depending on the track to which it is added.
This problem occurs even in an empty session if there is only one MANALEY MASSIVE PASSIVE EQ on the Master Bus.
I cannot use the VST version because MIXBUS doesn't let me do that.
I wrote about this 4 months ago: http://mixbus.harrisonconsoles.com/forum...-7071.html
I contacted support, but the only thing I was advised to check the location of plug-ins on the disk. Of course they are located where it should be.
I contacted the UA support service and after providing all the information, they admitted that they did not see any problems for the plugins to work.
MIXBUS problem! otherwise, there would be no people with the same problem.

---

UA plupins are an essential element of professional mixing.

You forgot to type *imho*.
MMM

All my statements I do on my own behalf, and not from the public.
And I see no reason to confirm this additionally.

Have you had a look at what's happening with or experimented with the pin connections? Also, a quick Google search shows this happens in other programs, not just MixBus. I found references for this error in Cubase, WaveLab, Logic, ProTools, Sony Acid Pro, Fruity Loops and Adobe Audition.

Have you watched the forums from 2012? Yes it was. But now in Cubase, Samplitude, Logic Pro there are no these problems. I use LPX, Protools, Cubase.
Do you see a problem in my pin connections?
And also: Do you use UAD plugins in MIXBUS without any problems?

[Dingo]

One thing to bear in mind is that Protools uses a proprietary format of AAX not AU nor VST, so to compare performance in Protools versus other platforms is a misnomer.