All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Geoffrey McRae" <geoff@hostfission.com>,
	"José Pekkarinen" <koalinux@gmail.com>,
	kraxel@redhat.com
Subject: Re: [PATCH v2] Autoconnect jack ports by default
Date: Wed, 24 Feb 2021 23:33:14 +0100	[thread overview]
Message-ID: <31652865.Htn8XJslzA@silver> (raw)
In-Reply-To: <5694e258e36c6623aae5465aafeec951@hostfission.com>

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.

I mean, are you piping QEMU into Ardour or something Geoffrey?

This could still be overridden by passing a bogus pattern with argument 
"connect-ports" for people who prefer the patchbay approach in the end.

So I would vote for the "make it easy for newbies" approach in this case, but 
I leave that up to you and Gerd to decide. :)

Best regards,
Christian Schoenebeck




  reply	other threads:[~2021-02-24 22:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 19:19 [PATCH v2] Autoconnect jack ports by default José Pekkarinen
2021-02-24 19:39 ` Christian Schoenebeck
2021-02-24 22:04   ` Geoffrey McRae
2021-02-24 22:33     ` Christian Schoenebeck [this message]
2021-02-24 22:38       ` Geoffrey McRae
2021-02-25  8:31         ` José Ramón Muñoz Pekkarinen
2021-02-25  8:48       ` Gerd Hoffmann
2021-02-26 11:40         ` Christian Schoenebeck
2021-03-03  7:13           ` Gerd Hoffmann
2021-03-04 11:24             ` Christian Schoenebeck
2021-03-04 11:56               ` Daniel P. Berrangé
2021-03-04 13:12                 ` Gerd Hoffmann
2021-03-04 13:53                   ` Daniel P. Berrangé
2021-03-04 14:12                     ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=31652865.Htn8XJslzA@silver \
    --to=qemu_oss@crudebyte.com \
    --cc=geoff@hostfission.com \
    --cc=koalinux@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.