Presets for Macro settings

https://pluginguru.net/unify/manual/doku.php?id=realtime-params#macro-definitions_and_cc-assignments_presets

Maybe I'm wrong, Shane, but I'm not sure that was what the OP was asking for. I think he was interested in an implementation similar to what Ableton just added in Live 11. It allows you to capture snapshots of the current values of all assigned macros and jump or morph between them. Maschine also has this feature. 

But this got me thinking it if would be possible to have a macro parameter path that includes another macro (for example: unify/macro/2). This could get messy, but it could also be very powerful. It would allow you to create a super-macro knob which controls multiple macro knobs. By setting the response curve of the super-macro to a stairstep, you could have one macro knob jump between predefined values of all the sub-macros it controls. By setting the response curve to a smooth curve, you could morph between the values of the sub-macros, which is what the original poster was asking for.

Of course, this would really work well if combined with my earlier request to change macro knob behavior from 'jump" to "pick" or "scale". 😉 

Also, this could be a cool implementation for dealing with the macros within an embedded Unify layer. You could have a "base layer" set of super-macros that control all the corresponding macros of any additional Unify layers you add in (like this: inst/3/macro/1).

just tossing ideas...

@karlfranz

Yes, the concept of taking snapshots and morphing between them is an interesting one.

You can link macro knobs to macro parameter paths of embedded Unify instances, but not within the same instance (as that could lead to feedback loops).

Posted by: @getdunne

but not within the same instance (as that could lead to feedback loops)

That's why I said it could get messy.

The easiest way I see to circumvent that pitfall is to establish some rules for the super-macro object class:

1) A super-macro can control many macros;

2) A macro cannot control a super-macro; 

3) One super-macro cannot control another;

4) Multiple super-macros can control the same macro.

These rules would essentially limit macro control down one level and no more. I think that would prevent any feedback loop from happening. 

Also, using this approach could provide up to 128 snapshots from one super-macro along with the ability to morph. In VST mode, this would allow the DAW to change many parameters using only one automation lane.

@karlfranz

The easiest way to circumvent the pitfall is the way I already did it: super-macros are at nesting depth N, the macros they control are at N+1. All four of your rules are satisfied, no feedback is possible, no need for a new "super-macro object class".