MAC only: Aggregate Device instead Virtual Audio Channels

This might help some Mac users. In Gig Performer, it bothers me when interfaces are not connected because the dialog boxes with questions or virtual ports keep popping up.

I have therefore defined an aggregate device on my Mac and added Blackhole 16 at the end (see screenshot). The advantage of this is that if an interface is currently not connected, and the number of linked inputs is sufficient, Gig Performer starts without asking, as long as the Blackhole channels are enough. Later, if I connect an interface, it is automatically recognized and integrated. Similarly, if an interface crashes, I can turn it off and on again during operation.

3 Likes

Do you also use this when performing live?

A Google search gave me: “Aggregate devices add complexity and can introduce latency or dropouts compared to a single, high-performance interface”

Did you ever encouter any performance issues?

@marbles: I have been using it for years on both Intel and Silicon, and have never experienced any issues.

2 Likes

I’ve had trouble in the past (Intel-era Macs) but it was usually with complex aggregate configurations where I needed a particular device to be dragged up from 44.1kHz to 48kHz to match multiple audio devices without flexible sample rates. These days, all devices have been upgraded and are natively 48kHz. On the M-series Macs, audio device aggregation works seamlessly, and in some cases, it actually helps keep variable-sample-rate devices locked at a particular sample rate when an application might try to change it.

2 Likes

This is a great idea! Thank you

2 Likes