search

rncbc / qjackctl

QjackCtl - JACK Audio Connection Kit Qt GUI Interface
https://qjackctl.sourceforge.io
GNU General Public License v2.0
181 stars 40 forks source link

More specific audio connection names when using a Multi-Output Device on macOS #95

Open matthewanderson23 opened 4 years ago

matthewanderson23 commented 4 years ago

It would be extremely beneficial on macOS (I'm using Mojave) if the input ports could be named more specifically if using a Multi-Output Device, corresponding to the respective device. For example, if I have a Multi-Output Device that is my built-in output (MacBook Pro Speakers) + Soundflower, specify the input ports as such (i.e. writable client system has input ports MBP_speaker_1 MBP_speaker_2 and soundflower_1 ... soundflower_X, instead of playback_1 ... playback_X+2)

matthewanderson23 commented 4 years ago

I understand it is probably for portability's sake that by default the input ports are named playback_X, but chances are, if someone is using a Multi-Output Device as their "soundcard", they want to know which port is which.

matthewanderson23 commented 4 years ago

The same argument is likely applicable to Aggregate Devices in general on macOS

rncbc commented 4 years ago

you'll have to rename one and each port manually, on Connections or Graph.

make sure you have the most recent jackd2 and qjackctl then have this enabled: Setup > Display > Connections Windows: Enable JACK client/port pretty-names (metadata)

this applies to GNU/LInux, of course; I don't have a clue whether it works at all on any other proprietary systems.

hth. cheers

matthewanderson23 commented 4 years ago

Thanks for that tip. There’s a similar setting on Mac Enable client/port aliases editing (rename)

Unfortunately that still doesn’t help if I don’t know which channels are which with an aggregate device.

If there is a better place/repo to ask this, please let me know. Hopefully it can be considered for a later revision here or elsewhere