View Single Post
Old 07-11-2020, 04:10 PM   #1
Nonlinear
Human being with feelings
 
Join Date: Apr 2018
Posts: 352
Default Techniques for "A/B" compare functionality?

Many plugins these days have an "A/B" compare function to audition two or more different sets of settings.

It seems that in order to save all of these options in the DAW we would actually need multiple sets of parameters i.e., GainA, GainB, etc., that could either be saved as discrete parameters or in chunk format data. That part is clear.

Now, how is loading of Presets handled given that the user could have either "A" or "B" option selected at the time? And what about automation data - how is that handled?

The more I dig into this the more complicated a simple "A/B" choice seems to get!

Is there a common approach for this and is it achievable with iPlug functions - or does it require custom coding?

Last edited by Nonlinear; 07-12-2020 at 05:36 PM.
Nonlinear is offline   Reply With Quote