Some plugins are malfunctioning in the Immersive Plugin Hub

I’ve been testing my most common plugins in the Immersive Plugin Hub in WL13, and there are a few that seem to either not synchronise parameter changes between instances, or only do so infrequently or unpredictably. In particular, it seems to occur with some subset of the Fab Filter plugins: Pro-Q 4, Pro-C 3, and Pro-G. I’ve reported this issue privately to them in case it is on their end, but they also asked that I report it here.

I cannot provide a reproduction video here due to file size restrictions.

For this to work, the plugin must obey strictly the parameter handling of VST3. What surprises me is that I didn’t see any problem with Fab Filter on my side (still using version 3), which are good plugins.

But when you’re unsure, you can force the parameter replication by clicking on the following button.

I’ve been investigating more, and it seems that once I have forced parameters to replicate across all instances the sync then continues to happen automatically. It is only before that where I seem to have issues.

The process is as follows:

  • Insert a new multi with Pro-Q 4. I explicitly cannot replicate the issue with Pro-Q 3.
  • Create a new EQ node.
  • Swap to another instance, the changes have not been replicated.
  • Return to the original instance.
  • Click replicate to all other instances.
  • Check another instance, the changes now have been replicated.
  • Make a change on that instance and change back to the original. The additional change has now been reflected there and in all other instances.

I understand that the problem is only with Pro-Q 4, not with Pro-Q3.
Right?
Then please transmit this important information to Fab Filter.

I already have conveyed this information! Pro-Q 4 and some other plugins exhibit this behaviour.

I’ve got the latest FabFiler 4 now, and I can reproduce the issue. In fact, I can reproduce it too with the FabFilter 3.

But from my point of view, in all cases, this is only a display thing. The audio DSP is correctly set in all instances.

If I do the same experiment with the Frequency plugin of Steinberg, the visual problem does not happen.

I will talk to FabFilter about it.

1 Like