From: Tanu Kaskinen Subject: Re: How to redefine "default" to be equivalent to "sysdefault"? Date: Mon, 18 Jun 2012 17:17:34 +0300 Message-ID: <1340029054.2892.5.camel@laptop> References: <1339574254.2909.15.camel@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by alsa0.perex.cz (Postfix) with ESMTP id 9C23024365 for ; Mon, 18 Jun 2012 16:17:37 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel List-Id: alsa-devel@alsa-project.org On Mon, 2012-06-18 at 15:45 +0200, Takashi Iwai wrote: > At Wed, 13 Jun 2012 10:57:34 +0300, > Tanu Kaskinen wrote: > > > > Hi, > > > > I have a file with the following contents: > > > > > > > > # This file an alsa configuration file, used by pasuspender to make the > > # "default" Alsa device work while PulseAudio is in suspended state. > > > > # Include the system configuration first. Is there any easier way to do this? > > # 14 lines for including one file is a bit much... > > @hooks [ > > { > > func load > > files [ > > { > > @func concat > > strings [ > > { @func datadir } > > "/alsa.conf" > > ] > > } > > ] > > } > > ] > > > > # Redefine "default" to be the same as "sysdefault". On most systems > > # "sysdefault" is configured to use dmix. > > pcm.!default sysdefault > > > > > > > > That doesn't do what I want it to do. When I run > > > > ALSA_CONFIG_PATH=/path/to/file.conf aplay -Ddefault ~/test.wav > > Doesn't ALSA_CONFIG_PATH=/path/to/file.conf:/usr/share/alsa/alsa.conf > work? I didn't know that I can give multiple files, so I haven't tried. One minor problem with this approach is that the alsa.conf path would be hardcoded, instead of using $(datadir)/alsa.conf. > $ALSA_CONFIG_PATH overrides the whole default paths, so it > doesn't include even sysdefault definition unless you specify multiple > paths. Yes, but did you miss the part entirely where I load alsa.conf in the beginning of the custom configuration file? That should work too, right? I know that alsa.conf is being loaded, because if I comment out the part that loads alsa.conf, I indeed get an error saying that "sysdefault" is not defined. -- Tanu