From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D432C433E0 for ; Wed, 24 Feb 2021 22:39:47 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A2C4564F03 for ; Wed, 24 Feb 2021 22:39:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A2C4564F03 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=hostfission.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:46650 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lF2or-0000sU-Jp for qemu-devel@archiver.kernel.org; Wed, 24 Feb 2021 17:39:45 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:38854) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lF2nf-0000J9-0r for qemu-devel@nongnu.org; Wed, 24 Feb 2021 17:38:31 -0500 Received: from mail1.hostfission.com ([139.99.139.48]:55302) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lF2nb-0002Hl-O9 for qemu-devel@nongnu.org; Wed, 24 Feb 2021 17:38:30 -0500 Received: from www1.hostfission.com (www1.hostfission.com [139.99.139.52]) by mail1.hostfission.com (Postfix) with ESMTP id DE4BE4B82E; Thu, 25 Feb 2021 09:38:24 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hostfission.com; s=mail; t=1614206304; bh=ZqV5+kJyC7yKybp2e+43sLeqs220n8flV+NQMbAYmN4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=UnBNdusprIzDFdnusxDlOghzODhTbAkSuosxWwUjGP2q2tvR2oCjKJW/z5BUwYSev Mym4akQI5WQ0+Q/AL+7QQ0iSnSUE1oGBzc6oLBnbQF+2buYTWNiFApUBMOnvD3qr7w sNZCxoikI/TaEFCrQFvykJc+PVaa+IQEbdBqxunU= Received: from mail.hostfission.com (www1.hostfission.com [127.0.0.1]) by www1.hostfission.com (Postfix) with ESMTP id CB26B8C854; Thu, 25 Feb 2021 09:38:24 +1100 (AEDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 25 Feb 2021 09:38:24 +1100 From: Geoffrey McRae To: Christian Schoenebeck Cc: qemu-devel@nongnu.org, =?UTF-8?Q?Jos=C3=A9_Pekkarinen?= , kraxel@redhat.com Subject: Re: [PATCH v2] Autoconnect jack ports by default In-Reply-To: <31652865.Htn8XJslzA@silver> References: <20210224191927.19271-1-koalinux@gmail.com> <3407243.daszWApDLn@silver> <5694e258e36c6623aae5465aafeec951@hostfission.com> <31652865.Htn8XJslzA@silver> Message-ID: X-Sender: geoff@hostfission.com User-Agent: Roundcube Webmail/1.3.15 Received-SPF: pass client-ip=139.99.139.48; envelope-from=geoff@hostfission.com; helo=mail1.hostfission.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" 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. On 2021-02-25 09:33, 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. > > 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. Sorry but this is a kludge to reverse another kludge, I really don't think this is a good way to go. > > 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