On Wed, Feb 24, 2021 at 11:33:14PM +0100, Christian Schoenebeck wrote: > On Mittwoch, 24. Februar 2021 23:04:47 CET Geoffrey McRae wrote: > > This goes against how all standard jack clients work, a new jack client > > should not auto-connect at all unless explicitly configured to as if > > there is an existing audio diagram configured (which is 99% of the time) > > it will cause unexpected/undesired behavior. > > > > Jack is not supposed to be an 'automatic' system, it's the > > responsibility of the patch bay software to route connections. > > > > The auto-connect feature exists to allow the jack audiodev to re-connect > > a broken connection when the jack device restarts/reconnects. > > Well, that was also my idea first, and I would agree with you in case of a > regular music app of course, but then I thought QEMU is probably not an > average JACK client, and it simply lowers the entry level for new users who > probably just want to output to system out anyway.
Well, I guess there is more software like that, any music player for example. I don't think this is a good reason for qemu to have non-standard behavior. If you want qemu autoconnect, you can use the connect-ports option. Beside that I'd expect the patch bay software is able to remember the routing configuration per application, so the setup would be a one-time thing you don't have to re-do on every qemu launch. Not fully sure this is actually the case though, I'm not a regular jack user. take care, Gerd
