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=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham 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 959FBC4CEC9 for ; Tue, 17 Sep 2019 13:19:00 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (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 166A92171F for ; Tue, 17 Sep 2019 13:19:00 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="p5rFTmu3" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 166A92171F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 66F1415F8; Tue, 17 Sep 2019 15:18:08 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 66F1415F8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1568726338; bh=qR/hAi0WykOqNGU94dsDuoF4YRi9/9W/SKPdPFUAS7c=; h=Date:From:To:In-Reply-To:References:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=p5rFTmu36AeY+7dfqCg1rg6qA56qRgoIpKELYwfrVQy8tUf9vFX4khBqn4ixkVpK9 i+mo8kFl/CDWRHQ2iZIb1+Cczi3ZDN79fKNQbbi5EuwKJpUN7/3ZcqFUlYB2KLBNEs DFHOuX1eCaAcbk/Q0/+XSAm8gnfa2d5FRY8L4bYw= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id C6FE8F802BD; Tue, 17 Sep 2019 15:18:07 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 02A4FF80361; Tue, 17 Sep 2019 15:18:07 +0200 (CEST) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 526AAF801DA for ; Tue, 17 Sep 2019 15:17:50 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 526AAF801DA X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 9BC68AF11; Tue, 17 Sep 2019 13:17:49 +0000 (UTC) Date: Tue, 17 Sep 2019 15:17:49 +0200 Message-ID: From: Takashi Iwai To: Tanu Kaskinen In-Reply-To: References: <20190904164706.gwjbcywbj7emnwvr@localhost> <20190910173345.63bv2xa4vlkxicxj@localhost> <365e4bcc033c151076140471225db51c80808b7f.camel@iki.fi> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Cc: alsa-devel@alsa-project.org, frederik Subject: Re: [alsa-devel] parameter for pulse device? X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Tue, 17 Sep 2019 15:14:53 +0200, Tanu Kaskinen wrote: > > On Tue, 2019-09-17 at 14:55 +0200, Takashi Iwai wrote: > > On Tue, 17 Sep 2019 14:51:01 +0200, > > Tanu Kaskinen wrote: > > > On Tue, 2019-09-10 at 10:33 -0700, frederik@ofb.net wrote: > > > > On Mon, Sep 09, 2019 at 07:52:24PM +0200, Takashi Iwai wrote: > > > > > It depends on how pcm.pulse is defined. If it's defined to take an > > > > > argument, it can work like that. (Or sometimes you may need to pass > > > > > the argument explicitly like "pulse:{device=mointor}".) > > > > > > > > > > The standard pcm.pulse definition provided in alsa-plugins repo > > > > > doesn't take the argument, and that can be the reason. > > > > > > > > Thank you Takashi. Would it be easy to change alsa-plugins so that it > > > > takes an argument? Is there a chance that this change would be > > > > accepted? > > > > > > > > If you can point me to the section of code in e.g. "plughw" where > > > > argument parsing is done, then I would probably end up modifying > > > > alsa-plugins myself, just to simplify what I am doing. > > > > > > This commit might be instructive: > > > https://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=3c199a0d199f0fae78c9c1b19c11878a6134b3a8 > > > > Yes, thanks for pointing an example. > > > > Now I took a quick look at the current code, and one remaining problem > > is that there is no device parameter value corresponding to the > > default (=NULL). Maybe we should accept the string "default" to be > > treated as NULL, for example. > > > > Ditto for the server parameter. > > Maybe "", i.e. the empty string, would be a good choice for the special > string representing NULL? It's not a valid device name or server > address, unlike "default", so there can't be any conflicts. Not that > "default" is very likely to cause conflicts either. Yeah, that sounds feasible. Then the rest is just coding ;) thanks, Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/alsa-devel