Kind regards, Ecki

My reason for posting here:  I'd like to know how Unify users have configured Gig Performer to make Unify patch changes.  My understanding from an initial read of Gig Performer's documentation is that the designers discourage configuring GP to send direct program changes to plug-ins and external instruments, and instead to create individual 'rack spaces' that are hardwired to the specific combination of patches one wants to make.  But considering that there are probably at least a dozen or so patches that I would consider to be 'favorites' for each hardware device as well as for Unify, the number  of combinations of patches would give rise to an unwieldy number of rack spaces to create.  What I would prefer to do - if possible - is to set up a single Gig Performer rack space that contained three 'program change selection" widgets, with each widget responsible for issuing a program change parameter to one of the three instruments.  Then I could use a device like a StreamDeck or an iPad app like TouchOSC or MIDI Designer that would allow me to set up virtual pads, with each pad being assigned a unique combination of the three program changes I might desire.  

I'm not sure if this is even possible in Gig Performer, or even if my explanation of what I'd like to do is clear.  But I'd welcome any insight into how Unify users here have configured Gig Performer setups to work in conjunction with Unify.

My current gear:

• A Korg M3 (with the built-in Radias board)
• A Korg PA5X (Korg's flagship arranger keyboard)
• A late model (2021) M1 MacBook Pro  
• A Korg NanoKontrol 2

My objective: to be able to make patch and parameter changes in real time for all three devices while minimizing or avoiding entirely  
the need to use the Mac’s mouse and keyboard.  

My intended typical use case (90%+ of the time):

• Use a real time performance hosting program like MainStage or Gig Performer to send program changes to the two hardware synths and to call up specific Unify patches
• Use Unify to host pretty much all plug-ins vis a vis loading and controlling plug-ins directly
• Use a MIDI controller like the NanoKontrol2 as a basic mixer - to control volume, pan, solo/muting - for the two Korg synths as well as one or more Unify instances.
• Possibly acquire another MIDI controller like the MIDI Fighter Twister to make real-time parameter changes to Unify's patches using rotary encoders.  I considered using either of the Korg synths as a MIDI controller but they both have limitations - the PA5X currently cannot send PC or CC messages to external devices, and neither device has any rotary encoders

Given the above,  I’d appreciate any suggestions/advice on the following:

• Which real time performance management program would you recommend I acquire, where the emphasis is on ease of learning and ease of use?
  While I recognize that MainStage is by far the least expensive option and should easily be able to handle the basic use case above,  my research on the Web has led me to believe that a program like Gig Performer or Camelot might have an easier-to-learn user interface.  Also, I have read where MainStage tends to be a resource hog, though I would think using Unify as the intermediary to handle all VSTs would obviate a lot of that risk?  In any event, I’d welcome any insights and recommendations from users experienced with these programs.
• As I mentioned,  my thought is that the NanoKontrol2 would be well suited to serve as a simple digital mixer for the three devices.
  But it lacks endless rotary encoders. Would it make sense to pair the NanoKontrol2 with a device like the MIDI Fighter Twister, where the latter
  would be dedicated to handling parameter changes in Unify patches (via Unify’s Macro knobs) and underlying plug-ins?
• When it comes to mapping Unify Macro knobs and associated real-time parameter controls,  I assume I would use Unify’s editing/mapping functions and not the parameter-mapping functions in the real-time performance hosting program (e.g. MainStage)?

Any advice on the above would be greatly appreciated!

Your help is greatly appreciated!

Someone suggested that using UNIFY could allow me to load a few different Omnisphere patches (I use 3 or 4) and that UNIFY would use the laptop processor in a way to make this whole process lighter on the processor (multithread?). Maybe I'm not explaining/understanding well?

Question: However do you have video tutorials that show precisely how to load multiple instances of Omnisphere in Unify in a way that will use the laptop resources more economically, won't be overloaded? Are there specific settings I need to address?

Second question - could I use UNIFY as standalone, without a DAW? Maybe that would free some resources for the laptop? Would that be too risky at this point, or has UNIFY been tested in this context? 

Thanks! :)