• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Control link problem with UAD plugins

Marcost

New member
Hi all,

I use control-link and my Mackie MCU Pro to control plugin parameters. Everything works fine since S1 5 until now.

I've just bought some UAD plugins and having mapped them to the Mackie as usual, I've now hit a problem... regardless of the actual parameter settings on the plugin, control-link reads the parameters as their default values when I return to that plugin. E.g. I set gain to 10. When I return later to that plugin, the plugin shows gain at 10 but the Mackie reads 0 (or whatever default value is).

Both S1 and UAD plugins are at latest revision, running on W10.

If it's not a recognised issue with S1, I'll try asking UAD.

Thanks in advance,

Martin
 
Which plugins are we talking about? I have some UAD plugins but no Mackie protocol controller, but with both my ATOM. SQ and the Nektar it looks as you would expect, on the controllers as well as on the Control Link in the upper left corner in S1 the values match what the plugin shows. I tried the 1176 and the Pultec and both seem to give accurate results.
 
Hi Dave,

Thanks for taking the time to check and respond. Attached are a couple of examples where the plugin setting does not match the control link value in S1 top left. I bought the signature edition, so have 56 UAD plugins. I've noticed this problem on all the ones I've mapped so far (at least 5).

If I move the plugin knob, the control link snaps to the correct value. However, if I first move the corresponding hardware knob on the Mackie then the plugin snaps to the control link value so I lose my previous setting - not helpful.

Thanks again,

Martin
 

Attachments

  • EQP.JPG
    EQP.JPG
    93,7 KB · Views: 3
  • LA2A.JPG
    LA2A.JPG
    117,1 KB · Views: 3
I understand that that is not helpful. However, I'm not seeing that behavior here, sorry. So maybe it is more related to the controller?

EDIT: I think I now understand what is going on. And no, I don't think you can prevent that. Of course the value of the controller knob is applied to the plugin. You should do you mapping on an instance that is not doing something in your mix. I have a special song file for exactly this. Assigning things creating snapshots of the plugins and whatever I can think of. This is assuming that the Mackie controls are not continuous controllers, therefore having fixed values for each knob position. That is where the problem probably is.
 
I understand that that is not helpful. However, I'm not seeing that behavior here, sorry. So maybe it is more related to the controller?

EDIT: I think I now understand what is going on. And no, I don't think you can prevent that. Of course the value of the controller knob is applied to the plugin. You should do you mapping on an instance that is not doing something in your mix. I have a special song file for exactly this. Assigning things creating snapshots of the plugins and whatever I can think of. This is assuming that the Mackie controls are not continuous controllers, therefore having fixed values for each knob position. That is where the problem probably is.
Thanks. On all other plugin manufacturers I have mapped, the Mackie controls snap to the current values when the plugin is opened. That is the behaviour I am used to regardless of the state of the plugin when I mapped it.

The controls on the Mackie are vpot rotary encoders and the led ring display on them should change to reflect the plugin setting when the plugun is opened.

All the UAD plugins were mapped a few days ago in my project template.

Cheers
 
Ok, that is not what I would expect to happen. But if all other plugins do what you want and the UAD ones don't, then it is clear that it' s the plugins behaving differently, not the DAW. Not because it's Studio One, I would tell you this regardless of what DAW you use. Look at what is different, and in this case it's the plugin developer, then start there.
 
Back
Top