Ok, that's what I thought.  I see it works for all macro knobs.  But for midi coming in from a keyboard controller, which I just tested, it doesn't have any affect.  That's what I was getting tripped up on.  So I will still have to use midi filter to block incoming midi data in some circumstances.  Thanks.

MIDI cc data received will go straight to the layer (regardless of that setting for the knobs), but will also update the knob position (without generating extra cc messages).

You can monitor what happens with the built in MIDI Monitor - see attached.

to disable the knobs from sending out CC values

Could you explain this setting more?  I believe you're referring to the setting "Generate MIDI-CC linked events on Macro knobs mouse control".

I keep running into synths that have their own assignment to CC1.  For instance, vibrato is somewhat common.  However I use Macro25 set for CC1 and I assign it to the synths vst filter cutoff parameter.  But then I find that the Layer is also letting CC1 get thru to the synth, and so then CC1 triggers both vibrato and cutoff.  So then I add midi filter blocking CC1 to layer 1 to stop the vibrato, which solves this dilemma. 

If you have this setting checked off, is it supposed to stop CC1 from getting thru on the Layer?  Or what does the setting do?  Manual didn't help me understand it either.

In short.. there is no good answer :) ... tweak your macro knob and modwheel.. if the filter sound changes, then it's mapped as expected and if you want all patches to work as John intended, set macro 1 to cc1 (and make sure sending MIDI cc output on macro knob moves is enabled in the MIDI settings tab).

One work around for the moment.. save a patch in your user library with an easy to remember/type name.. e.g. 000 (it will be at the top of the list).. then before you close your session simply save the patch to 000 (click save as and enter 000 (overwrite it) - that is easy to remember and short to type).. and close the session.. with update on quit it should reload 000 on start (with all the patch settings).

(This applies for standalone mode obviously, in a DAW the current state is grabbed when closing a project if you have any project auto-save settings enabled - or you should just save your DAW session before closing it.)

If you want all the connected MIDI devices to auto-connect then enable the MIDI device polling option.

Audio interface settings should be retained by default automatically on close - so don't un-power your audio interface before quitting Unify2 - seems like this would be good practice anyway.. just leave the audio interface powered up whilst the computer is running.

In settings page you can also set your preferred option for the default trigger mode, and whether the metronome state should be saved (also should apply in the case of auto-saves/update on quit in future - but again, not with the current system unless you manually save a quick restore patch).

I am aware of the existing GUI option to load a preferred default patch on startup. While that gets close to what I am requesting, it still requires extra steps and ongoing patch file management. Many of my other plugins do this by default (e.g., Arturia, AAS, Scaler immediately come to mind).

*Regarding Audio/MIDI settings (this was raised before, and may be specific to my setup):

• Audio: Typically, my audio interface selection is retained. However, if I happen to power the interface down before quitting Unify, Unify reverts to the Mac's default audio interface the next time I open the app.

• MIDI: Consistently, all connected MIDI controller ports are re-checked/enabled every time I launch Unify, regardless of what was previously disabled.

I appreciate your consideration!

I need precise volume control of each layer as a song plays out - do independent layer fade outs, etc.  I don't think Notemate is going to solve that where as "layer MIDI input enable/disable switching automation" does.