While I get where you're coming from, those using QEMU with Jack are
already advanced users that are used to reading technical documentation.
Having our one client do something that is unexpected/different would
not only confuse existing Jack users but also anyone following any
guides/documentation on how to use a generic jack client. IMO the better
solution here is simply better documentation, perhaps even a known
working sample setup.
This is an interesting point, but hey, things be told in advance, whether
the patch is accepted or not is up to you, I'll respect any decision in the
upstreaming, I'm just curious, how can a default behaviour that multiple
other applications and libraries adopt is going to confuse jack community?
For instance, I tend to work with firefox, and mumble that natively support
jack, and they perform automatic connection no patchbay extra config
required, the basics just work out of the box, while you still can do more
complex stuff if you want to use the full set of features of jack.
On the other hand, I took some time to read to automatically configure
the connection over qjackctl patchbay, so thanks for pointing out that via.
José.