An ‘Aggregate Device’ will do exactly what you have in your screenshot. It is simply a virtual grouping of two or more devices. So although it will look like a single block in Gig Performer, you can route audio to either device, the same as in your screenshot.
2 Likes
Quite the contrary – you get the benefit of using multiple cores, giving you more capacity.
Please - what you’re asking is not a simple option underneath the covers.
Plugin hosts (whether ours or any other DAW) communicate through the OS to audio interfaces, either real or virtual.
You could also add the Black Hole virtual audio device, aggregrate that with your main audio interface and then use mechanisms like audio hijack to capture audio
1 Like
Hey guys, yesterday I could not reply anymore, cause on first day here your number of replies i limited.
Wonna say thanks, the aggregate device is the 100% simple solution for my needs, thanks so much for this info. I never made an aggregate device before, sure heard this, but reall did not know it exists, and can be so helpful. So with this my wanted option is pretty easy to build, checked that yesterday, and works perfect! 
4 Likes
Aggregate device all day.
Please ensure that both devices you are aggregating are set to the same settings. Sample rate and all that to avoid future issues and crashes.
1 Like
Yes, sure about that, thanks!
1 Like
On mac too, for sure?
Dhj is correct.
Not only multi instance lets you use more cores on either Mac or PC but also you might be able to even set different sample rates for the separate instances if I am not mistaken.
If one instance is required - the aggregate device.
Did not get it, at that point. The other post below explained that a bit, and then I understood. Did not know about aggregate device before!
1 Like
And also very important to check the drift buttons on aggregate device! Did not do that, and on a regular basis the audio of the virtual device stops at about 4 minutes plus/minus a few seconds. WTF … but found the solution!