From: Takashi Iwai Subject: Re: [PATCH 0/6] snd-usb endpoint rework, version 7 Date: Fri, 13 Apr 2012 09:51:23 +0200 Message-ID: References: <1334231475-20980-1-git-send-email-zonque@gmail.com> <4F87C587.9000101@gmail.com> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mx2.suse.de (cantor2.suse.de [195.135.220.15]) by alsa0.perex.cz (Postfix) with ESMTP id B65922434C for ; Fri, 13 Apr 2012 09:51:23 +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: Felix Homann Cc: blablack@gmail.com, Grant Diffey , clemens@ladisch.de, alsa-devel@alsa-project.org, Daniel Mack List-Id: alsa-devel@alsa-project.org At Fri, 13 Apr 2012 09:32:17 +0200, Felix Homann wrote: > > Hi, > > >> if all volumes are max on module insert. the ftu is essentially unusable > >> untill they're corrected > > Yes, the current defaults for the FTUs are horrible. > > But I don't know if I really like the "diagonal" state that you > proposed as a default state. At least for my setup it's not more > usable than the "all-volumes-maxed" state. I probably would prefer a > "everything-muted" default. Then you only have to deal with the > controls you actually need and don't have to bother with tons of other > controls. (And, it's more in line with non-USB devices). > > If there aren't any objections to the "everything-muted-by-default" > approach, I will prepare a patch this weekend. It's basically good -- excpet for that it may let people see as a regression sometimes. Let's check first whether "alsactl init" or whatever distro initialization works properly with the muted USB-audio device. > > What about alsactl? Set the mixers once, then call "alsactl store". Does > > that help? > > Yes, for sure. That's what I have been using for a long time. It would > be desirable though if the state was stored on diconnect/shutdown of > the device. Is this possible with a udev rule? Not really. When udev is notified at disconnection, it is already disconnected, thus you can't access to the device :) Takashi